| /Documentation/devicetree/bindings/net/ |
| D | macb.txt | 5 Use "cdns,at91rm9200-emac" Atmel at91rm9200 SoC.
6 Use "cdns,at91sam9260-macb" for Atmel at91sam9 SoCs.
7 Use "cdns,sam9x60-macb" for Microchip sam9x60 SoC.
8 Use "cdns,np4-macb" for NP4 SoC devices.
9 Use "cdns,at32ap7000-macb" for other 10/100 usage or use the generic form: "cdns,macb".
10 Use "cdns,pc302-gem" for Picochip picoXcell pc302 and later devices based on
12 Use "atmel,sama5d2-gem" for the GEM IP (10/100) available on Atmel sama5d2 SoCs.
13 Use "atmel,sama5d3-macb" for the 10/100Mbit IP available on Atmel sama5d3 SoCs.
14 Use "atmel,sama5d3-gem" for the Gigabit IP available on Atmel sama5d3 SoCs.
15 Use "atmel,sama5d4-gem" for the GEM IP (10/100) available on Atmel sama5d4 SoCs.
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | colorspaces-defs.rst | 34 two basic ways to do it: Divide the angular value by 2 (0-179), or use the
95 - Use the default transfer function as defined by the colorspace.
97 - Use the Rec. 709 transfer function.
99 - Use the sRGB transfer function.
101 - Use the opRGB transfer function.
103 - Use the SMPTE 240M transfer function.
105 - Do not use a transfer function (i.e. use linear RGB values).
107 - Use the DCI-P3 transfer function.
109 - Use the SMPTE 2084 transfer function. See :ref:`xf-smpte-2084`.
124 - Use the default Y'CbCr encoding as defined by the colorspace.
[all …]
|
| /Documentation/x86/x86_64/ |
| D | boot-options.rst | 39 Do not opt-in to Local MCE delivery. Use legacy method
80 Use IO-APIC. Default
83 Don't use the IO-APIC.
86 Don't use the local APIC
89 Don't use the local APIC (alias for i386 compatibility)
109 Deprecated, use tsc=unstable instead.
112 Don't use the HPET timer.
131 Use the CPU reboot vector for warm reset
139 Use the keyboard controller. cold reset (default)
141 Use the ACPI RESET_REG in the FADT. If ACPI is not configured or
[all …]
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 11 `alloc_pages`. It is also possible to use more specialized allocators,
14 Most of the memory allocation APIs use GFP flags to express how that
20 answer, although very likely you should use
41 many other allocations types can use ``GFP_KERNEL``. Note, that
46 handler, use ``GFP_NOWAIT``. This flag prevents direct reclaim and
51 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
56 * Userspace allocations should use either of the ``GFP_USER``,
77 use new scope APIs described in
84 And even with hardware with restrictions it is preferable to use
90 The most straightforward way to allocate memory is to use a function
[all …]
|
| D | idr.rst | 38 these users have been content with a ``UINT_MAX`` limit, and they use
42 If you need to allocate IDs sequentially, you can use
47 either use the callback-based :c:func:`idr_for_each` or the
48 iterator-style :c:func:`idr_for_each_entry`. You may need to use
50 also use :c:func:`idr_get_next` if the iterator doesn't fit your needs.
54 pointed to from the IDR; if you want to do that, use one of the iterators
57 You can use :c:func:`idr_is_empty` to find out whether there are any
|
| D | symbol-namespaces.rst | 5 The following document describes how to use Symbol Namespaces to structure the
15 === 3 How to use Symbols exported in Namespaces
16 === 4 Loading Modules that use namespaced Symbols
26 limiting the availability of a set of symbols for use in other parts of the
27 kernel. As of today, modules that make use of symbols exported into namespaces,
47 namespace `USB_STORAGE`, use::
54 and kernel/module.c make use the namespace at build time or module load time,
66 subsystem and the maintainer's preference, which one to use. The first option
87 3. How to use Symbols exported in Namespaces
90 In order to use symbols that are exported into namespaces, kernel modules need
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | atmel-usart.txt | 7 For the dbgu UART, use "atmel,<chip>-dbgu", "atmel,<chip>-usart"
33 - atmel,use-dma-rx: use of PDC or DMA for receiving data
34 - atmel,use-dma-tx: use of PDC or DMA for transmitting data
36 It will use specified PIO instead of the peripheral function pin for the USART feature.
47 - use PDC:
54 atmel,use-dma-rx;
55 atmel,use-dma-tx;
64 - use DMA:
71 atmel,use-dma-rx;
72 atmel,use-dma-tx;
|
| /Documentation/vm/ |
| D | swap_numa.rst | 8 information, we can make use of this information to decide which swap
9 device to use in get_swap_pages() to get better performance.
12 How to use this feature
16 use of automatically binding, there is no need to manipulate priority settings
24 Then node 0 will use the two swap devices in the order of swapA then swapB and
25 node 1 will use the two swap devices in the order of swapB then swapA. Note
40 Then node 0 will use them in the order of::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
[all …]
|
| D | split_page_table_lock.rst | 13 access to the table. At the moment we use split lock for PTE and PMD
43 Hugetlb can support several page sizes. We use split lock only for PMD
61 Make sure the architecture doesn't use slab allocator for page table
87 To avoid increasing size of struct page and have best performance, we use a
90 - if spinlock_t fits into long, we use page->ptr as spinlock, so we
92 - if size of spinlock_t is bigger then size of long, we use page->ptl as
93 pointer to spinlock_t and allocate it dynamically. This allows to use
100 Please, never access page->ptl directly -- use appropriate helper.
|
| /Documentation/networking/device_drivers/ti/ |
| D | tlan.txt | 57 the adapter to use the AUI interface instead of the 10 Base T
58 interface. This is also what to do if you want to use the BNC
71 5. You have to use speed=X duplex=Y together now. If you just
76 6. If the driver is built into the kernel, you can use the 3rd
88 0x02 = use half duplex
89 0x04 = use full duplex
90 0x08 = use 10BaseT
91 0x10 = use 100BaseTx
98 use the above options on a per adapter basis. To force a 100Mbit/HD
99 link with your eth1 adapter use:
[all …]
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 23 The second issue is that to make use of existing interfaces in Linux,
38 * Client - A driver which makes use of a resource by setting up a
51 to be used directly (client) and it can also make use of the CMB as
62 then the NVMe Target could use the RNIC's memory instead of the CMB
63 in cases where the NVMe cards in use do not have CMB support.
75 any orchestrator drivers to find and use the memory. When marked in
87 routine to use the mapping function :c:func:`pci_p2pdma_map_sg()` instead
91 The client may also, optionally, make use of
92 :c:func:`is_pci_p2pdma_page()` to determine when to use the P2P mapping
93 functions and when to use the regular mapping functions. In some
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.txt | 19 - DO use node names matching the class of the device. Many standard names are
29 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon'
36 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
37 strings. DO use fallback compatibles when devices are the same as or a subset
41 - DO use a vendor prefix on device specific property names. Consider if
48 - DO use common property unit suffixes for properties with scientific units.
59 - DO use non-empty 'ranges' to limit the size of child buses/devices. 64-bit
|
| /Documentation/devicetree/bindings/extcon/ |
| D | extcon-arizona.txt | 17 - wlf,use-jd2 : Use the additional JD input along with JD1 for dual pin jack
19 - wlf,use-jd2-nopull : Internal pull on JD2 is disabled when used for
23 - wlf,micd-software-compare : Use a software comparison to determine mic
44 The first cell defines the accessory detection pin, zero will use MICDET1
45 and all other values will use MICDET2.
59 wlf,use-jd2;
60 wlf,use-jd2-nopull;
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 13 rarely used. However, it is recommended to use a DMA-safe buffer if your
17 note that other subsystems you use might add requirements. E.g., if your
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
27 updated to use this flag will work like before. And like before, they risk
34 of i2c_master_send() and i2c_master_recv() functions can now use DMA safe
42 Bus master drivers wishing to implement safe DMA can use helper functions from
49 bounce buffer. But you don't need to care about that detail, just use the
67 driver can be used as a reference example how to use the above helpers.
69 Final note: If you plan to use DMA with I2C (or with anything else, actually)
|
| /Documentation/fb/ |
| D | sisfb.rst | 38 Well, it depends: If compiled statically into the kernel, use lilo's append
52 A common mistake is that folks use a wrong parameter format when using the
55 (or whatever mode you want to use, alternatively using any other format
58 want to use). Using a "=" for a ":" (and vice versa) is a huge difference!
65 How do I use it?
81 - or simply use the VESA mode number in hexadecimal or decimal.
90 use either "mode" or "vesa" but not both.
95 resolution is used. If you want to switch to a different mode, use the fbset
100 you want to switch to another mode, use the stty shell command.
106 You should *not* compile-in vesafb. And please do not use the "vga=" keyword
[all …]
|
| D | uvesafb.rst | 11 Unlike other drivers, uvesafb makes use of a userspace helper called
25 order for uvesafb to work properly. If you want to use uvesafb during
27 either compile it into the kernel or use it as an initrd.
40 video mode you want to use. This can be especially painful with
80 vgapal Use the standard VGA registers for palette changes.
82 pmipal Use the protected mode interface for palette changes.
95 nomtrr Do not use memory type range registers.
102 amount of video RAM, use this option to override the BIOS (in MiB).
109 vbemode:x Force the use of VBE mode x. The mode will only be set if it's
113 HINT: If you use this option because normal <mode> parameter does
[all …]
|
| D | tridentfb.rst | 31 How to use it?
47 fp use flat panel related stuff
51 image, otherwise use
54 memsize integer value in KB, use if your card's memory size is misdetected.
60 Only use if your video memory is taken from main memory hence of
61 configurable size. Otherwise use memsize.
67 800 or 1280) and it is not what the driver seems to detect use it.
|
| /Documentation/process/ |
| D | email-clients.rst | 9 These days most developers use ``git send-email`` instead of regular
11 end, maintainers use ``git am`` to apply the patches.
51 Don't use PGP/GPG signatures in mail that contains patches.
90 Works. Some people use this successfully for patches.
92 To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
103 Some people use this successfully for patches.
109 Then use:
119 Some people use Kmail successfully for patches.
158 :menuselection:`save as`. You can use the whole email unmodified as a patch
176 Plenty of Linux developers use ``mutt``, so it must work pretty well.
[all …]
|
| /Documentation/arm64/ |
| D | acpi_object_usage.rst | 47 Optional, not currently supported, with no real use-case for an
178 ARM-specific error sources have been defined; please use those or the
180 Bridge), or use type 9 (Generic Hardware Error Source). Firmware first
221 descriptions and power states on ARM platforms should use the DSDT
273 use. Since these are not meant to be of general use but are limited
274 to very specific end users, they are not recommended for use and are
281 Recommend for use on arm64; use of PCC is recommended when using CPPC
357 for use with devices that can be added to a running system, but can
392 Optional, not currently supported. No known use case for arm64,
457 _CID 6.1.2 Use as needed, see also _HID.
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 21 You must use the `*delay` family of functions. These
22 functions use the jiffie estimation of clock speed
35 In general, use of mdelay is discouraged and code should
36 be refactored to allow for the use of msleep.
39 You should use the `*sleep[_range]` family of functions.
64 * Use udelay
74 * Use usleep_range
104 * Use msleep or possibly msleep_interruptible
111 early by a signal. In general, just use msleep unless
|
| /Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 12 In order to use a diskless system, such as an X-terminal or printer server
16 filesystem mounted via NFS. The following text describes on how to use NFS
26 In order to use nfsroot, NFS client support needs to be selected as
41 told what root fs device to use. And in the case of nfsroot, where to find
49 real device but just a synonym to tell the kernel to use NFS instead of
60 (see below). This parameter allows the use of different
99 autoconfiguration will take place. The most common way to use this
140 <device> Name of network device to use.
148 <autoconf> Method to use for autoconfiguration. In the case of options
157 off or none: don't use autoconfiguration
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 13 several pins, if we use one pcm per per_pin, there will be many PCMs.
15 per_pin. Driver uses spec->dyn_pcm_assign flag to indicate whether to use
69 Will not use hda_jack but use snd_jack in spec->pcm_rec[pcm_idx].jack directly.
73 Use hda_jack and assign spec->pcm_rec[pcm_idx].jack = jack->jack statically.
88 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for
96 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for dyn_pcm_assign.
97 Use hda_jack mechanism to handle jack events.
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5640.txt | 38 1: Use GPIO1 for jack-detect
39 2: Use JD1_IN4P for jack-detect
40 3: Use JD2_IN4N for jack-detect
41 4: Use GPIO2 for jack-detect
42 5: Use GPIO3 for jack-detect
43 6: Use GPIO4 for jack-detect
|
| /Documentation/devicetree/bindings/mmc/ |
| D | brcm,sdhci-iproc.txt | 13 Use brcm2835-sdhci for the eMMC controller on the BCM2835 (Raspberry Pi) and
16 Use sdhci-iproc-cygnus for Broadcom SDHCI Controllers
19 Use sdhci-iproc for Broadcom SDHCI Controllers that allow standard
25 - sdhci,auto-cmd12: specifies that controller should use auto CMD12.
|
| /Documentation/driver-api/phy/ |
| D | phy.rst | 8 and how-to-use.
17 controllers have PHY functionality embedded into it and others use an external
18 PHY. Other peripherals that use PHY include Wireless LAN, Ethernet,
22 all over the Linux kernel to drivers/phy to increase code re-use and for
25 This framework will be of use only to devices that use external PHY (PHY
49 arguments. For the dt boot case, all PHY providers should use one of the above
78 to make use of it. The PHY framework provides 2 APIs to create the PHY.
88 The PHY drivers can use one of the above 2 APIs to create the PHY by passing
94 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in
99 Before the controller can make use of the PHY, it has to get a reference to
[all …]
|