Searched full:shown (Results 1 – 25 of 184) sorted by relevance
12345678
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-ceva.txt | 10 The fields for the above parameter must be as shown below:
18 The fields for the above parameter must be as shown below:
26 The fields for the above parameter must be as shown below:
34 The fields for the above parameter must be as shown below:
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti,da850-mstpri.txt | 15 Example for da850-lcdk is shown below.
|
| D | mvebu-mbus.txt | 139 In the shown example, the translation entry in the 'ranges' property is what
193 of 0xf0000000, or 0xd0000000 for the NOR device shown above, if such region is
214 See the example below, where a more complete device tree is shown:
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-da8xx-ddrctl.txt | 15 Example for da850 shown below.
|
| /Documentation/pcmcia/ |
| D | driver.rst | 9 runtime as shown below::
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 168 shown below, which is one of several functions that enforce ordering of
251 portion of RCU's grace period guarantee is shown in the following
261 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
264 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
318 counter, as shown below:
346 to the newly advanced value from the ``rcu_state`` structure, as shown
386 non-idle CPUs report their own quiescent states, as shown in the
401 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
438 traverses up the ``rcu_node`` tree as shown at the bottom of the
462 effects are as shown below:
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-intro.rst | 20 and the cropping target is a part of an image to be shown on a display.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 28 Enabled protocols are shown in [] brackets.
89 The enabled wakeup protocol is shown in [] brackets.
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 110 shown also when the invalid H/W pointer is detected at the
197 ports. The connection status and the running status are shown
224 - set-up of PCM, shown in hw_parms, sw_params, and status in the PCM
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 26 has been developed, the sample output of the utility is shown below::
|
| /Documentation/security/ |
| D | IMA-templates.rst | 45 clearly shown: the latter function will not contain specific code to handle
70 prefix is shown only if the hash algorithm is not SHA1 or MD5);
|
| /Documentation/admin-guide/media/ |
| D | pci-cardlist.rst | 53 .. [#] some of the drivers have sub-drivers, not shown at this table
96 Some of those drivers support multiple devices, as shown at the card
|
| D | usb-cardlist.rst | 35 some of the drivers have sub-drivers, not shown at this table.
38 as shown at :doc:`gspca card list <gspca-cardlist>`.
|
| /Documentation/leds/ |
| D | ledtrig-oneshot.rst | 20 The trigger can be activated from user space on led class devices as shown
|
| D | ledtrig-usbport.rst | 32 This trigger can be activated from user space on led class devices as shown
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 41 Enabled protocols are shown in [] brackets.
102 The enabled wakeup protocol is shown in [] brackets.
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5663.txt | 32 R channel accordingly. Example is shown as following.
|
| /Documentation/devicetree/bindings/dma/ |
| D | arm-pl330.txt | 37 as shown below.
|
| /Documentation/userspace-api/media/ |
| D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
|
| /Documentation/filesystems/ |
| D | hfsplus.rst | 18 Specifies the creator/type values as shown by the MacOS finder
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,drif.txt | 5 representation of DRIF interfacing with a master device is shown below.
87 When interfacing with a third party tuner device with two data pins as shown
135 When interfacing with a third party tuner device with one data pin as shown
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mpc.txt | 9 "fsl,mpc5121-i2c-ctrl" is required as shown in the example below.
|
| /Documentation/admin-guide/ |
| D | svga.rst | 84 case your chipset has been detected, some chipset-specific modes are shown as
104 modes are not listed at all and the modes revealed by ``scan`` are shown before
113 by entering its mode directly if you know it even if it isn't shown on the menu.
125 0x0100. All VESA modes should be autodetected and shown on the menu.
|
| /Documentation/hwmon/ |
| D | nsa320.rst | 52 provided kernel. Testing has shown that if the delay between chip select and
|
| /Documentation/devicetree/bindings/usb/ |
| D | dwc3-st.txt | 32 The dwc3 core should be added as subnode to ST DWC3 glue as shown in the
|
12345678