| /Documentation/driver-api/phy/ |
| D | phy.rst | 8 and how-to-use.
15 such as serialization, de-serialization, encoding, decoding and is responsible
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
32 For the simple case where the PHY provider implements only a single instance of
36 dt boot case.
49 arguments. For the dt boot case, all PHY providers should use one of the above
54 nodes within extra levels for context and extensibility, in which case the low
[all …]
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 5 Given that I2C is a low-speed bus, over which the majority of messages
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
22 -------
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
40 -------
42 Bus master drivers wishing to implement safe DMA can use helper functions from
43 the I2C core. One gives you a DMA-safe buffer for a given i2c_msg as long as a
[all …]
|
| /Documentation/usb/ |
| D | mtouchusb.rst | 8 - 0.3 - Created based off of scanner & INSTALL from the original touchscreen
10 - Amended for linux-2.4.18, then 2.4.19
12 - 0.5 - Complete rewrite using Linux Input in 2.6.3
15 - 1.4 - Multiple changes to support the EXII 5000UC and house cleaning
19 Performed multiple successful tests with an EXII-5010UC
30 ------------------------------------------------------
32 USB Capacitive - Pearl Case 14-205 (Discontinued)
33 USB Capacitive - Black Case 14-124 (Discontinued)
34 USB Capacitive - No Case 14-206 (Discontinued)
36 USB Capacitive - Pearl Case EXII-5010UC
[all …]
|
| D | usbdevfs-drop-permissions.c | 38 printf("ERROR: reset failed! (%d - %s)\n", in reset_device()
39 -res, strerror(-res)); in reset_device()
51 printf("ERROR claiming if %d (%d - %s)\n", in claim_some_intf()
52 i, -res, strerror(-res)); in claim_some_intf()
81 drop_privileges(fd, -1U); in main()
85 "[1] Reset device. Should fail if device is in use\n" in main()
86 "[2] Claim 4 interfaces. Should succeed where not in use\n" in main()
92 case 0: in main()
94 case 1: in main()
97 case 2: in main()
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nand-chip.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/nand-chip.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
13 - $ref: mtd.yaml#
18 SPI-NAND devices are concerned by this description.
23 Contains the chip-select IDs.
25 nand-ecc-engine:
30 case the phandle should reference the parent node.
[all …]
|
| /Documentation/RCU/ |
| D | lockdep.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 aware of when each task enters and leaves any flavor of RCU read-side
10 that this is not the case in 2.6.32 and earlier). This allows lockdep's
18 rcu_read_lock_bh_held() for RCU-bh.
19 rcu_read_lock_sched_held() for RCU-sched.
20 rcu_read_lock_any_held() for any of normal RCU, RCU-bh, and RCU-sched.
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
[all …]
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 15 depending on the use case. Interconnect providers can also be interconnect
16 consumers, such as in the case where two network-on-chip fabrics interface
20 - compatible : contains the interconnect provider compatible string
21 - #interconnect-cells : number of cells in a interconnect specifier needed to
28 compatible = "qcom,msm8916-snoc";
29 #interconnect-cells = <1>;
31 clock-names = "bus_clk", "bus_a_clk";
42 multiple paths from different providers depending on use case and the
54 interconnect-names : List of interconnect path name strings sorted in the same
55 order as the interconnects property. Consumers drivers will use
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,cdce706.txt | 1 Bindings for Texas Instruments CDCE706 programmable 3-PLL clock
7 - compatible: shall be "ti,cdce706".
8 - reg: i2c device address, shall be in range [0x68...0x6b].
9 - #clock-cells: from common clock binding; shall be set to 1.
10 - clocks: from common clock binding; list of parent clock
13 - clock-names: shall be clk_in0 and/or clk_in1. Use clk_in0
14 in case of crystal oscillator or differential signal input
15 configuration. Use clk_in0 and clk_in1 in case of independent
16 single-ended LVCMOS inputs configuration.
22 #clock-cells = <0>;
[all …]
|
| /Documentation/process/ |
| D | coding-style.rst | 19 --------------
31 Now, some people will claim that having 8-character indentations makes
33 80-character terminal screen. The answer to that is that if you need
37 In short, 8-char indents make things easier to read, and have the added
42 to align the ``switch`` and its subordinate ``case`` labels in the same column
43 instead of ``double-indenting`` the ``case`` labels. E.g.:
45 .. code-block:: c
48 case 'G':
49 case 'g':
52 case 'M':
[all …]
|
| /Documentation/admin-guide/ |
| D | bug-bisect.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
8 This document describes how to use a ``git bisect`` to find the source code
9 change that broke something -- for example when some functionality stopped
13 kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
17 care about the result -- for example, because the problem happens after the
28 use as pristine base at each bisection step; ideally, you have also worked out
29 a fully reliable and straight-forward way to reproduce the regression, too.*
38 Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
64 minutes more on testing in case your reproducer is unreliable.
68 test after this (roughly 10 steps)'. In that case go back to step 1.
[all …]
|
| D | serial-console.rst | 6 To use a serial port as console you need to compile the support into your
7 kernel - by default it is not compiled in. For PC style serial ports
10 :menuselection:`Character devices --> Serial drivers --> 8250/16550 and compatible serial support -…
16 use for console output.
38 In this case, the output will appear on all requested consoles. And
49 times. In this case, there are the following two rules:
74 The kernel command line is used also by systemd. It would use the last
83 You will need to create a new device to use ``/dev/console``. The official
86 (You can also use a network device as a console. See
89 Here's an example that will use ``/dev/ttyS1`` (COM2) as the console.
[all …]
|
| D | ext4.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
44 converted to use 256 byte for greater efficiency via:
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
[all …]
|
| /Documentation/leds/ |
| D | leds-class.rst | 8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
48 - devicename:
57 - color:
59 include/dt-bindings/leds/common.h.
61 - function:
63 include/dt-bindings/leds/common.h.
66 to linux-leds@vger.kernel.org.
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 3 This node is intended to allow SoC reset in case of software reset
14 - compatible: ti,keystone-reset
16 - ti,syscon-pll: phandle/offset pair. The phandle to syscon used to
17 access pll controller registers and the offset to use
20 - ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
22 in order to use mux block registers for all watchdogs.
26 - ti,soft-reset: Boolean option indicating soft reset.
29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related
37 Setup keystone reset so that in case software reset or
40 pllctrl: pll-controller@2310000 {
[all …]
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 11 The implementation introduces a global, in-kernel hashtable that
30 meta-data and shadow-data:
32 - meta-data
34 - obj - pointer to parent object
35 - id - data identifier
37 - data[] - storage for shadow data
41 They also allow to call a custom constructor function when a non-zero
48 * klp_shadow_get() - retrieve a shadow variable data pointer
49 - search hashtable for <obj, id> pair
51 * klp_shadow_alloc() - allocate and add a new shadow variable
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The ARM Versatile boards are two variants of ARM926EJ-S evaluation boards
30 - description: The ARM Versatile Application Baseboard (HBI-0118) is an
31 evaluation board specifically for the ARM926EJ-S. It can be connected
32 to an IB1 interface board for a touchscreen-type use case or an IB2
33 for a candybar phone-type use case. See ARM DUI 0225D.
35 - const: arm,versatile-ab
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | chipidea,usb2-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Xu Yang <xu.yang_2@nxp.com>
25 clock-names:
31 power-domains:
37 reset-names:
40 "#reset-cells":
45 itc-setting:
[all …]
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason we need a mechanism to separate controller-local
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
61 - irq_resolve_mapping() returns a pointer to the irq_desc structure
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
66 - irq_linear_revmap() is now identical to irq_find_mapping(), and is
68 - generic_handle_domain_irq() handles an interrupt described by a
72 compatible with a RCU read-side critical section.
80 callbacks) then it can be directly obtained from irq_data->hwirq.
87 Which reverse map type should be used depends on the use case. Each
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | architecture.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - `In-Kernel Testing Framework`_
10 - `kunit_tool (Command-line Test Harness)`_
12 In-Kernel Testing Framework
19 - Organizes tests
20 - Reports test results
21 - Provides test utilities
24 ----------
26 The test case is the fundamental unit in KUnit. KUnit test cases are organised
27 into suites. A KUnit test case is a function with type signature
[all …]
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 21 modes causes the PM core to skip some platform-related callbacks which on ACPI
45 ----------------------------
47 To find out why hibernation fails on your system, you can use a special testing
53 - test the freezing of processes
56 - test the freezing of processes and suspending of devices
59 - test the freezing of processes, suspending of devices and platform
63 - test the freezing of processes, suspending of devices, platform
67 - test the freezing of processes, suspending of devices, platform global
76 To use one of them it is necessary to write the corresponding string to
79 to use the "devices" test mode along with the "platform" mode of hibernation,
[all …]
|
| /Documentation/networking/ |
| D | radiotap-headers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 How to use radiotap headers
8 ------------------------------------
10 Radiotap headers are variable-length and extensible, you can get most of the
19 -----------------------
29 < 8-byte ieee80211_radiotap_header >
33 At the moment there are only 13 possible argument indexes defined, but in case
44 --------------------------
50 - the arguments are all stored little-endian!
52 - the argument payload for a given argument index has a fixed size. So
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
7 mapping is made use of in conjunction with the mmap() system call, the shmat()
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
17 and it's also much more restricted in the latter case:
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
31 the no-MMU case doesn't support these, behaviour is identical to
36 In the MMU case: VM regions backed by pages read from file; changes to
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | capture.c.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 .. code-block:: c
24 #include <fcntl.h> /* low-level i/o */
50 static int fd = -1;
69 } while (-1 == r && EINTR == errno);
90 case IO_METHOD_READ:
91 if (-1 == read(fd, buffers[0].start, buffers[0].length)) {
93 case EAGAIN:
96 case EIO:
109 case IO_METHOD_MMAP:
[all …]
|
| /Documentation/arch/mips/ |
| D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------
11 Similar to the arch/arm case (b), a DT-aware bootloader is expected to
20 512MB of the physical address space (0x00000000 - 0x1fffffff),
23 Legacy bootloaders do not use this convention, and they do not pass in a
24 DT block. In this case, Linux will look for a builtin DTB, selected via
27 This convention is defined for 32-bit systems only, as there are not
28 currently any 64-bit BMIPS implementations.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 8 1-1. What is RDMA controller?
9 1-2. Why RDMA controller needed?
10 1-3. How is RDMA controller implemented?
16 1-1. What is RDMA controller?
17 -----------------------------
20 set of processes can use. These processes are grouped using RDMA controller.
25 1-2. Why RDMA controller needed?
26 --------------------------------
37 1-3. How is RDMA controller implemented?
38 ----------------------------------------
[all …]
|