Searched +full:0 +full:- +full:9 +full:a +full:- +full:f (Results 1 – 25 of 134) sorted by relevance
123456
| /Documentation/devicetree/bindings/soundwire/ |
| D | soundwire-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soundwire/soundwire-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
11 - Vinod Koul <vkoul@kernel.org>
14 SoundWire busses can be described with a node for the SoundWire controller
15 device and a set of child nodes for each SoundWire slave on the bus.
21 "#address-cells":
24 "#size-cells":
[all …]
|
| /Documentation/trace/postprocess/ |
| D | decode_msr.py | 3 # decode_msr msr-index.h < trace
9 with open(sys.argv[1] if len(sys.argv) > 1 else "msr-index.h", "r") as f:
10 for j in f:
11 m = re.match(r'#define (MSR_\w+)\s+(0x[0-9a-fA-F]+)', j)
16 ( "MSR_LASTBRANCH_%d_FROM_IP", 0x680, 0x69F ),
17 ( "MSR_LASTBRANCH_%d_TO_IP", 0x6C0, 0x6DF ),
18 ( "LBR_INFO_%d", 0xdc0, 0xddf ),
22 m = re.search(r'(read|write)_msr:\s+([0-9a-f]+)', j)
31 r = er[0] % (num - er[1],)
|
| D | trace-vmscan-postprocess.pl | 2 # This is a POC for reading the text representation of trace output related to
3 # page reclaim. It makes an attempt to extract some high-level information on
6 # Example usage: trace-vmscan-postprocess.pl < /sys/kernel/debug/tracing/trace_pipe
8 # --read-procstat If the trace lacks process info, get it from /proc
9 # --ignore-pid Aggregate processes of the same name together
25 use constant MM_VMSCAN_WRITEPAGE_ANON_SYNC => 9;
31 # Per-order events
43 # High-level events extrapolated from tracepoints
77 my $sigint_report = 0;
78 my $sigint_exit = 0;
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 4 Contact: tpmdd-devel@lists.sf.net
5 Description: The device/ directory under a specific TPM instance exposes
12 Contact: tpmdd-devel@lists.sf.net
13 Description: The "active" property prints a '1' if the TPM chip is accepting
16 visible to the OS, but will only accept a restricted set of
24 Contact: tpmdd-devel@lists.sf.net
32 Contact: tpmdd-devel@lists.sf.net
37 Manufacturer: 0x53544d20
41 Manufacturer is a hex dump of the 4 byte manufacturer info
42 space in a TPM. TCG version shows the TCG TPM spec level that
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | allwinner,sun50i-a64-de2.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/bus/allwinner,sun50i-a64-de2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <maxime.ripard@bootlin.com>
15 pattern: "^bus(@[0-9a-f]+)?$"
17 "#address-cells":
20 "#size-cells":
25 - const: allwinner,sun50i-a64-de2
[all …]
|
| D | allwinner,sun8i-a23-rsb.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/bus/allwinner,sun8i-a23-rsb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <maxime.ripard@bootlin.com>
14 "#address-cells":
17 "#size-cells":
18 const: 0
22 - const: allwinner,sun8i-a23-rsb
[all …]
|
| /Documentation/ioctl/ |
| D | ioctl-number.rst | 21 system calls 'write' and 'read'. For example, a SET_FOO ioctl would
23 a GET_FOO ioctl would be _IOR, although the kernel would actually write
28 many drivers share a partial letter with other drivers.
30 If you are writing a driver for a new device and need a letter, pick an
33 patch to Linus Torvalds. Or you can e-mail me at <mec@shout.net> and
36 The second argument to _IO, _IOW, _IOR, or _IOWR is a sequence number
50 if a program calls an ioctl on the wrong device, it will get an
67 no attempt to list non-X86 architectures or ioctls from drivers/staging/.
73 0x00 00-1F linux/fs.h conflict!
74 0x00 00-1F scsi/scsi_ioctl.h conflict!
[all …]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
16 On a significant proportion of boards, the manufacturer has stored
24 pattern: "^(eeprom|efuse|nvram)(@.*|-[0-9a-f])*$"
26 "#address-cells":
29 "#size-cells":
32 read-only:
38 "^.*@[0-9a-f]+$":
[all …]
|
| /Documentation/vm/ |
| D | zsmalloc.rst | 11 (0-order) pages, it would suffer from very high fragmentation --
15 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
17 pages act as a single higher-order page i.e. an object can span 0-order
18 page boundaries. The code refers to these linked pages as a single entity
23 worst case, page is incompressible and is thus stored "as-is" i.e. in
27 Additionally, zs_malloc() does not return a dereferenceable pointer.
31 issues on 32-bit systems where the VA region for kernel space mappings
33 be mapped using zs_map_object() to get a usable pointer and subsequently
40 ``/sys/kernel/debug/zsmalloc/<user name>``. Here is a sample of stat output::
47 9 176 0 1 186 129 8 4
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
16 MDIO bus must have a list of child nodes, one per device on the
17 bus. These should follow the generic ethernet-phy.yaml document, or
18 a device specific binding document.
24 "#address-cells":
[all …]
|
| D | fsl-fec.txt | 4 - compatible : Should be "fsl,<soc>-fec"
5 - reg : Address and length of the register set for the device
6 - interrupts : Should contain fec interrupt
7 - phy-mode : See ethernet.txt file in the same directory
10 - phy-supply : regulator that powers the Ethernet PHY.
11 - phy-handle : phandle to the PHY device connected to this device.
12 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
13 Use instead of phy-handle.
14 - fsl,num-tx-queues : The property is valid for enet-avb IP, which supports
17 - fsl,num-rx-queues : The property is valid for enet-avb IP, which supports
[all …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | watchdog.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Guenter Roeck <linux@roeck-us.net>
11 - Wim Van Sebroeck <wim@linux-watchdog.org>
15 describe watchdog devices in a device tree.
19 pattern: "^watchdog(@.*|-[0-9a-f])?$"
21 timeout-sec:
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | pincfg.txt | 4 - pio-map : array of pin configurations. Each pin is defined by 6
7 - port : port number of the pin; 0-6 represent port A-G in UM.
8 - pin : pin number in the port.
9 - dir : direction of the pin, should encode as follows:
11 0 = The pin is disabled
16 - open_drain : indicates the pin is normal or wired-OR:
18 0 = The pin is actively driven as an output
19 1 = The pin is an open-drain driver. As an output, the pin is
20 driven active-low, otherwise it is three-stated.
22 - assignment : function number of the pin according to the Pin Assignment
[all …]
|
| /Documentation/scsi/ |
| D | sym53c8xx_2.txt | 1 The Linux SYM-2 driver documentation file
5 95170 DEUIL LA BARRE - FRANCE
9 2004-10-09
28 8.7 Reset all logical units of a target
29 8.8 Abort all tasks of all logical units of a target
30 9. Configuration parameters
40 10.2.7 Suggest a default SCSI id for hosts
42 10.2.9 Debug mode
45 10.2.12 Exclude a host from being attached
60 This driver supports the whole SYM53C8XX family of PCI-SCSI controllers.
[all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/spi/spi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mark Brown <broonie@kernel.org>
13 SPI busses can be described with a node for the SPI controller device
14 and a set of child nodes for each SPI slave on the bus. The system SPI
20 pattern: "^spi(@.*|-[0-9a-f])*$"
22 "#address-cells":
25 "#size-cells":
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-piix4.rst | 2 Kernel driver i2c-piix4
9 * ServerWorks OSB4, CSB5, CSB6, HT-1000 and HT-1100 southbridges
18 * AMD Hudson-2, ML, CZ
26 - Frodo Looijaard <frodol@dds.nl>
27 - Philip Edelbrock <phil@netroedge.com>
31 -----------------
40 -----------
42 The PIIX4 (properly known as the 82371AB) is an Intel chip with a lot of
44 minor functions is implementing a System Management Bus. This is a true
45 SMBus - you can not access it on I2C levels. The good news is that it
[all …]
|
| /Documentation/admin-guide/ |
| D | tainted-kernels.rst | 2 ---------------
6 most of the time it's not a problem to run a tainted kernel; the information is
13 (i.e. unload a proprietary kernel module), to indicate the kernel remains not
15 notices an internal problem (a 'kernel bug'), a recoverable error
16 ('kernel oops') or a non-recoverable error ('kernel panic') and writes debug
18 check the tainted state at runtime through a file in ``/proc/``.
24 You find the tainted state near the top in a line starting with 'CPU:'; if or
25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened
30 CPU: 0 PID: 4424 Comm: insmod Tainted: P W O 4.20.0-0.rc6.fc30 #1
32 RIP: 0010:my_oops_init+0x13/0x1000 [kpanic]
[all …]
|
| /Documentation/input/devices/ |
| D | sentelic.rst | 8 :Copyright: |copy| 2002-2011 Sentelic Corporation.
10 :Last update: Dec-07-2011
15 A) MSID 4: Scrolling wheel mode plus Forward page(4th button) and Backward
21 4. Issuing the "Get device ID" command (0xF2) and waits for the response;
22 5. FSP will respond 0x04.
27 Bit 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
28 BYTE |---------------|BYTE |---------------|BYTE|---------------|BYTE|---------------|
29 1 |Y|X|y|x|1|M|R|L| 2 |X|X|X|X|X|X|X|X| 3 |Y|Y|Y|Y|Y|Y|Y|Y| 4 | | |B|F|W|W|W|W|
30 |---------------| |---------------| |---------------| |---------------|
37 Bit2 => Middle Button, 1 is pressed, 0 is not pressed.
[all …]
|
| /Documentation/networking/device_drivers/smsc/ |
| D | smc9.txt | 2 SMC 9xxxx Driver
14 (A kernel patch is supplied for 1.3.71 )
20 3. To compile as a module, run 'make' .
23 4. Loading the driver as a module :
29 ifport=x : 0 for whatever is default
36 ftp://fenris.campus.vt.edu/smc9/smc9-12.tar.gz
37 ftp://sfbox.vt.edu/filebox/F/fenris/smc9/smc9-12.tar.gz
|
| /Documentation/devicetree/bindings/gpio/ |
| D | pl061-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/pl061-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Rob Herring <robh@kernel.org>
13 # We need a select here so we don't match all nodes with 'arm,primecell'
20 - compatible
24 pattern: "^gpio@[0-9a-f]+$"
28 - const: arm,pl061
[all …]
|
| D | nxp,lpc1850-gpio.txt | 2 -----------------------------------------------------
5 - compatible : Should be "nxp,lpc1850-gpio"
6 - reg : List of addresses and lengths of the GPIO controller
8 - reg-names : Should be "gpio", "gpio-pin-ic", "gpio-group0-ic" and
9 "gpio-gpoup1-ic"
10 - clocks : Phandle and clock specifier pair for GPIO controller
11 - resets : Phandle and reset specifier pair for GPIO controller
12 - gpio-controller : Marks the device node as a GPIO controller
13 - #gpio-cells : Should be two:
14 - The first cell is the GPIO line number
[all …]
|
| /Documentation/fault-injection/ |
| D | nvme-fault-injection.rst | 3 Linux's fault injection framework provides a systematic way to support
17 ---------------------------------------------------
24 cp a.file /mnt
28 cp: cannot stat ‘/mnt/a.file’: Input/output error
32 FAULT_INJECTION: forcing a failure.
33 name fault_inject, interval 1, probability 100, space 0, times 1
34 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc8+ #2
39 dump_stack+0x5c/0x7d
40 should_fail+0x148/0x170
41 nvme_should_fail+0x2f/0x50 [nvme_core]
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | armada3700-periph-clock.txt | 12 The following is a list of provided IDs for Armada 370 North bridge clocks:
14 -----------------------------------
15 0 mmc MMC controller
24 9 i2c_2 I2C 2
27 12 ddr_fclk DDR F clock
33 The following is a list of provided IDs for Armada 370 South bridge clocks:
35 -----------------------------------
36 0 gbe-50 50 MHz parent clock for Gigabit Ethernet
37 1 gbe-core parent clock for Gigabit Ethernet core
38 2 gbe-125 125 MHz parent clock for Gigabit Ethernet
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | bttv-cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 .. flat-table::
9 :header-rows: 1
11 :stub-columns: 0
13 * - Card number
14 - Card name
15 - PCI IDs
17 * - 0
18 - *** UNKNOWN/GENERIC ***
19 -
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,gic-v3.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic-v3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <marc.zyngier@arm.com>
13 AArch64 SMP cores are often associated with a GICv3, providing Private
15 Software Generated Interrupts (SGI), and Locality-specific Peripheral
19 - $ref: /schemas/interrupt-controller.yaml#
24 - items:
25 - enum:
[all …]
|
123456