Searched +full:back +full:- +full:to +full:- +full:back (Results 1 – 25 of 628) sorted by relevance
12345678910>>...26
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS 17 MAJOR:MINOR-fuseblk 23 The default backing dev, used for non-block device backed 30 Size of the read-ahead window in kilobytes 32 (read-write) 38 total write-back cache that relates to its current average 39 writeout speed in relation to the other devices. 42 percentage of the write-back cache to a particular device. 45 (read-write) 52 total write-back cache that relates to its current average [all …]
|
| D | sysfs-bus-surface_aggregator-tabletsw | 6 This attribute returns a string with the current type-cover 10 - "disconnected": The type-cover has been disconnected. 12 - "closed": The type-cover has been folded closed and lies on 15 - "laptop": The type-cover is open and in laptop-mode, i.e., 18 - "folded-canvas": The type-cover has been folded back 19 part-ways, but does not lie flush with the back side of the 20 device. In general, this means that the kick-stand is used 23 - "folded-back": The type cover has been fully folded back and 24 lies flush with the back side of the device. 26 - "<unknown>": The current state is unknown to the driver, for [all …]
|
| D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured 11 Each write to the entry causes one command request to be built 12 and sent while the replies are read back one message at time 22 in little-endian binary format to have it sent to the configured 29 Each write to the entry causes one command request to be built 30 and sent while the replies are read back one message at time 38 Description: SCMI Raw message errors facility; any kind of timed-out or 41 Each read gives back one message at time (receiving an EOF at 52 Each read gives back one message at time (receiving an EOF at 60 Description: SCMI Raw stack reset facility; writing a value to this entry [all …]
|
| D | sysfs-platform-hidma-mgmt | 1 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority 10 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/weight 19 What: /sys/devices/platform/hidma-mgmt*/chreset_timeout_cycles 25 Contains the platform specific cycle value to wait after a 31 What: /sys/devices/platform/hidma-mgmt*/dma_channels 38 of HIDMA hardware. The value may change from chip to chip. 40 What: /sys/devices/platform/hidma-mgmt*/hw_version_major 48 What: /sys/devices/platform/hidma-mgmt*/hw_version_minor 56 What: /sys/devices/platform/hidma-mgmt*/max_rd_xactions 63 read transactions that can be issued back to back. [all …]
|
| D | sysfs-bus-most | 8 might return <1-1.1:1.0> 25 directory is created that allows applications to read and 34 This is used to set an arbitrary DCI register address an 35 application wants to read from or write to. 43 This is used to read and write the DCI register whose address 52 This is used to check and configure the MAC address. 60 This is used to check and configure the MAC address. 68 This is used to check and configure the MAC address. 76 This is used to check and configure the MEP filter address. 84 This is used to check and configure the MEP hash table. [all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 7 caches data to the RAID disks. The cache can be in write-through (supported 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since 9 3.4) has a new option '--write-journal' to create array with cache. Please 10 refer to mdadm manual for details. By default (RAID array starts), the cache is 11 in write-through mode. A user can switch it to write-back mode by:: 13 echo "write-back" > /sys/block/md0/md/journal_mode 15 And switch it back to write-through mode by:: 17 echo "write-through" > /sys/block/md0/md/journal_mode 19 In both modes, all writes to the array will hit cache disk first. This means 22 write-through mode [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 .. _v4l2-meta-fmt-rpi-be-cfg: 9 Raspberry Pi PiSP Back End configuration format 12 The Raspberry Pi PiSP Back End memory-to-memory image signal processor is 14 to the `pispbe-config` output video device node using the 17 The PiSP Back End processes images in tiles, and its configuration requires 22 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_ 23 provide detailed description of the ISP back end configuration and programming 27 ------------------------- 30 to be processed and is therefore shared across all the tiles of the image. So [all …]
|
| /Documentation/scsi/ |
| D | sd-parameters.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 --------------- 16 write back 1 0 on on 17 write back, no read (daft) 1 1 on off 20 To set cache type to "write back" and save this setting to the drive:: 22 # echo "write back" > cache_type 24 To modify the caching mode without making the change persistent, prepend 25 "temporary " to the cache type string. E.g.:: 27 # echo "temporary write back" > cache_type
|
| /Documentation/admin-guide/media/ |
| D | raspberrypi-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be) 7 The PiSP Back End 10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads 13 pixel data back to memory through two distinct output channels. 18 The PiSP Back End ISP processes images in tiles. The handling of image 19 tessellation and the computation of low-level configuration parameters is 24 an image sensor through a MIPI CSI-2 compatible capture interface, storing them 25 in DRAM memory and processing them in the PiSP Back End to obtain images usable 29 The pisp-be driver [all …]
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 15 It does not cover the support needed from applications to enable the BIOS to 16 update itself with the image downloaded in to the memory. 25 Please go to http://support.dell.com register and you can find info on 28 Libsmbios can also be used to update BIOS on Dell systems go to 34 using the driver breaks the image in to packets of fixed sizes and the driver 36 maintains a link list of packets for reading them back. 40 The rbu driver needs to have an application (as mentioned above) which will 41 inform the BIOS to enable the update in the next system reboot. 57 copied to a single contiguous block of physical memory. 63 changed to packets during the driver load time by specifying the load [all …]
|
| D | kernel-per-CPU-kthreads.rst | 2 Reducing OS jitter due to per-cpu kthreads 5 This document lists per-CPU kthreads in the Linux kernel and presents 6 options to control their OS jitter. Note that non-per-CPU kthreads are 7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind 8 them to a "housekeeping" CPU dedicated to such work. 13 - Documentation/core-api/irq/irq-affinity.rst: Binding interrupts to sets of CPUs. 15 - Documentation/admin-guide/cgroup-v1: Using cgroups to bind tasks to sets of CPUs. 17 - man taskset: Using the taskset command to bind tasks to sets 20 - man sched_setaffinity: Using the sched_setaffinity() system 21 call to bind tasks to sets of CPUs. [all …]
|
| D | quickly-build-trimmed-linux.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 5 How to quickly build a trimmed Linux kernel 8 This guide explains how to swiftly build Linux kernels that are ideal for 9 testing purposes, but perfectly fine for day-to-day use, too. 14 *[If you are new to compiling Linux, ignore this TLDR and head over to the next 15 section below: it contains a step-by-step guide, which is more detailed, but 16 still brief and easy to follow; that guide and its accompanying reference 20 If your system uses techniques like Secure Boot, prepare it to permit starting 21 self-compiled Linux kernels; install compilers and everything else needed for 22 building Linux; make sure to have 12 Gigabyte free space in your home directory. [all …]
|
| /Documentation/sphinx/ |
| D | parallel-wrapper.sh | 2 # SPDX-License-Identifier: GPL-2.0+ 5 # environment (as exported by scripts/jobserver-exec), or fall back to 6 # the "auto" parallelism when "-jN" is not specified at the top-level 13 if [ -z "$parallel" ] ; then 14 # If no parallelism is specified at the top-level make, then 15 # fall back to the expected "-jauto" mode that the "htmldocs" 17 auto=$(perl -e 'open IN,"'"$sphinx"' --version 2>&1 |"; 24 if [ -n "$auto" ] ; then 28 # Only if some parallelism has been determined do we add the -jN option. 29 if [ -n "$parallel" ] ; then [all …]
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 Git source-code management system. Git is a powerful tool with a lot of 10 ways to use those features. This document looks in particular at the use 15 One thing to be aware of in general is that, unlike many other projects, 19 maintainers result from a desire to avoid merges, while others come from 27 referred to as rebasing since both are done with the ``git rebase`` 30 - Changing the parent (starting) commit upon which a series of patches is 36 - Changing the history of a set of patches by fixing (or deleting) broken 37 commits, adding patches, adding tags to commit changelogs, or changing 39 type of operation will be referred to as "history modification" [all …]
|
| /Documentation/block/ |
| D | deadline-iosched.rst | 5 This little file attempts to document how the deadline io scheduler works. 7 of interest to power users. 10 ----------------------- 11 Refer to Documentation/block/switching-sched.rst for information on 12 selecting an io scheduler on a per-device basis. 14 ------------------------------------------------------------------------------ 17 ----------------------- 19 The goal of the deadline io scheduler is to attempt to guarantee a start 27 ----------------------- 29 Similar to read_expire mentioned above, but for writes. [all …]
|
| /Documentation/userspace-api/ |
| D | tee.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 include/uapi/linux/tee.h defines the generic interface to a TEE. 10 User space (the client) connects to the driver by opening /dev/tee[0-9]* or 11 /dev/teepriv[0-9]*. 13 - TEE_IOC_SHM_ALLOC allocates shared memory and returns a file descriptor 16 any longer it should be unmapped with munmap() to allow the reuse of 19 - TEE_IOC_VERSION lets user space know which TEE this driver handles and 22 - TEE_IOC_OPEN_SESSION opens a new session to a Trusted Application. 24 - TEE_IOC_INVOKE invokes a function in a Trusted Application. 26 - TEE_IOC_CANCEL may cancel an ongoing TEE_IOC_OPEN_SESSION or TEE_IOC_INVOKE. [all …]
|
| /Documentation/arch/powerpc/ |
| D | transactional_memory.rst | 5 POWER kernel support for this feature is currently limited to supporting 8 This file aims to sum up how it is supported by Linux and what behaviour you 17 instructions are presented to delimit transactions; transactions are 18 guaranteed to either complete atomically or roll back and undo any partial 49 transactional or non-transactional accesses within the system. In this 50 example, the transaction completes as though it were normal straight-line code 52 atomic move of money from the current account to the savings account has been 59 state will roll back to that at the 'tbegin', and control will continue from 60 'tbegin+4'. The branch to abort_handler will be taken this second time; the 69 - Conflicts with cache lines used by other processors [all …]
|
| D | dawr-power9.rst | 6 cause a checkstop if it points to cache inhibited (CI) memory. Currently Linux 7 has no way to distinguish CI memory when configuring the DAWR, so on affected 13 This issue is only present on processors prior to v2.3. The revision can be 34 PPC_PTRACE_GETHWDBGINFO call. This results in GDB falling back to 37 h_set_mode(DAWR) and h_set_dabr() will now return an error to the 43 migration from POWER8 to POWER9, at the cost of silently losing the 57 host. The watchpoint will fail and GDB will fall back to software 61 and configure the hardware to use the DAWR. This will run at full 63 guest is migrated to a POWER9 host, the watchpoint will be lost on the 64 POWER9. Loads and stores to the watchpoint locations will not be [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | goodix,gt7375p.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Douglas Anderson <dianders@chromium.org> 14 This touchscreen uses the i2c-hid protocol but has some non-standard 18 - $ref: /schemas/input/touchscreen/touchscreen.yaml# 23 - const: goodix,gt7375p 24 - items: 25 - const: goodix,gt7986u 26 - const: goodix,gt7375p [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,imx-asrc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/fsl,imx-asrc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 13 with other Back Ends Audio controller such as ESAI, SSI and SAI. It has 14 three pairs to support three substreams within totally 10 channels. 17 - Shawn Guo <shawnguo@kernel.org> 18 - Sascha Hauer <s.hauer@pengutronix.de> 23 - enum: 24 - fsl,imx35-asrc [all …]
|
| /Documentation/i2c/ |
| D | i2c-address-translators.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 ----------- 15 forwards transactions from upstream to the appropriate downstream port 21 An ATR looks similar to an i2c-mux except: 22 - the address on the parent and child busses can be different 23 - there is normally no need to select the child port; the alias used on the 27 The kernel i2c-atr provides a helper to implement an ATR within a driver. 30 devices on the child bus ends up in invoking the driver code to select 32 and picking one for each new device is up to the driver implementer. The 33 ATR maintains a table of currently assigned alias and uses it to modify [all …]
|
| /Documentation/admin-guide/mm/ |
| D | zswap.rst | 9 in the process of being swapped out and attempts to compress them into a 10 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles 11 for potentially reduced swap I/O. This trade-off can also result in a 21 throttling by the hypervisor. This allows more work to get done with less 22 impact to the guest workload and guests sharing the I/O subsystem 24 drastically reducing life-shortening writes. 26 Zswap evicts pages from compressed cache on an LRU basis to the backing swap 35 An example command to enable zswap at runtime, assuming sysfs is mounted 42 back into memory all of the pages stored in the compressed pool. The 44 either invalidated or faulted back into memory. In order to force all [all …]
|
| D | transhuge.rst | 16 But in the future it can expand to other filesystems. 26 requiring larger clear-page copy-page in page faults which is a 32 factor will affect all subsequent accesses to the memory for the whole 46 going to run faster. 48 Modern kernels support "multi-size THP" (mTHP), which introduces the 49 ability to allocate memory in blocks that are bigger than a base page 50 but smaller than traditional PMD-size (as described above), in 51 increments of a power-of-2 number of pages. mTHP can back anonymous 52 memory (for example 16K, 32K, 64K, etc). These THPs continue to be 53 PTE-mapped, but in many cases can still provide similar benefits to [all …]
|
| /Documentation/devicetree/bindings/iommu/ |
| D | ti,omap-iommu.txt | 4 - compatible : Should be one of, 5 "ti,omap2-iommu" for OMAP2/OMAP3 IOMMU instances 6 "ti,omap4-iommu" for OMAP4/OMAP5 IOMMU instances 7 "ti,dra7-dsp-iommu" for DRA7xx DSP IOMMU instances 8 "ti,dra7-iommu" for DRA7xx IOMMU instances 9 - ti,hwmods : Name of the hwmod associated with the IOMMU instance 10 - reg : Address space for the configuration registers 11 - interrupts : Interrupt specifier for the IOMMU instance 12 - #iommu-cells : Should be 0. OMAP IOMMUs are all "single-master" devices, 14 also refer to the generic bindings document for more info [all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | era.rst | 2 dm-era 8 dm-era is a target that behaves similar to the linear target. In 11 maintains the current era as a monotonically increasing 32-bit 15 partially invalidating the contents of a cache to restore cache 16 coherency after rolling back a vendor snapshot. 36 ---------- 38 Possibly move to a new era. You shouldn't assume the era has 43 ------------------ 45 Create a clone of the metadata, to allow a userland process to read it. 48 ------------------ [all …]
|
12345678910>>...26