Searched full:mostly (Results 1 – 25 of 183) sorted by relevance
12345678
| /Documentation/ABI/testing/ |
| D | sysfs-ata | 111 Mostly used by PATA devices.
113 xfer_mode: (RO) Current transfer mode. Mostly used by
117 Mostly used by PATA devices.
|
| /Documentation/i2c/ |
| D | summary.rst | 18 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
25 Because the SMBus is mostly a subset of the generalized I2C bus, we can
|
| D | dma-considerations.rst | 15 around 8 bytes (as of today, this is mostly an educated guess, however). For
|
| /Documentation/sound/soc/ |
| D | codec-to-codec.rst | 5 Mostly the flow of audio is always from CPU to codec so your system
114 mostly useful for communication with simple fixed-function codecs, such
|
| /Documentation/devicetree/bindings/serial/ |
| D | qcom,msm-uart.yaml | 15 dma-engine isn't needed. From a software perspective it's mostly compatible
|
| D | qcom,msm-uartdm.yaml | 17 software perspective it's mostly compatible with the MSM serial UART except
|
| /Documentation/hwmon/ |
| D | lm92.rst | 47 mostly compatible but do not have a vendor ID register and therefore must be
|
| D | asus_ec_sensors.rst | 65 the path is mostly identical for them). If ASUS changes this path
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ssbi.yaml | 11 communicate with a limited range of devices (mostly power management
|
| D | ti-sysc.yaml | 16 is mostly used for interaction between module and Power, Reset and Clock
18 than that it is mostly independent of the interconnect.
|
| D | baikal,bt1-axi.yaml | 19 (mostly between peripheral devices and RAM, but also between DMA and
|
| /Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 9 exceeds the page size. However, for a filesystem of mostly huge files,
|
| /Documentation/devicetree/bindings/clock/ |
| D | brcm,bcm2835-cprman.txt | 9 few PLLs, and a level of mostly-generic clock generators sourcing from
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-backlight | 56 backlight state. Platform interfaces are mostly a
|
| /Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | imx8m-ddrc.yaml | 21 for the sake of "describing hardware"), it mostly just exposes firmware
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | apll.txt | 8 modes (locked, low power stop etc.) APLL mostly behaves like
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.yaml | 10 The Calxeda SATA controller mostly conforms to the AHCI interface
|
| D | imx-sata.yaml | 13 The Freescale i.MX SATA controller mostly conforms to the AHCI interface
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | tpo,tpg110.yaml | 19 can be discovered and the hardware is therefore mostly
|
| /Documentation/devicetree/bindings/mips/lantiq/ |
| D | rcu.txt | 7 The RCU register range is used for multiple purposes. Mostly one device
|
| /Documentation/devicetree/bindings/sound/ |
| D | microchip,sama7g5-i2smcc.yaml | 45 - description: Generic Clock (Optional). Should be set mostly when Master
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-rf-tuner.rst | 18 without a metal box "silicon tuners". These controls are mostly
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 52 MMIO traps back to VMM where the virtual devices are mostly emulated.
|
| /Documentation/RCU/ |
| D | listRCU.rst | 3 Using RCU to Protect Read-Mostly Linked Lists
6 One of the most common uses of RCU is protecting read-mostly linked lists
21 Example 1: Read-mostly list: Deferred Destruction
487 Read-mostly list-based data structures that can tolerate stale data are
|
| /Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | sysctrl.yaml | 17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the
|
12345678