Searched +full:alternative +full:- +full:a (Results 1 – 25 of 158) sorted by relevance
1234567
| /Documentation/networking/pse-pd/ |
| D | pse-pi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 The Power Sourcing Equipment Power Interface (PSE PI) plays a pivotal role in
7 the architecture of Power over Ethernet (PoE) systems. It is essentially a
9 eight-pin modular jack, commonly known as the Ethernet RJ45 port. This
14 ---------------------------
19 - Section "33.2.3 PI pin assignments" covers the pin assignments for PoE
21 - Section "145.2.4 PSE PI" addresses the configuration for PoE systems that
25 -------------------------------
27 Single Pair Ethernet (SPE) represents a different approach to Ethernet
31 two pairs of wires, SPE operates on a simpler model due to its single-pair
[all …]
|
| /Documentation/devicetree/bindings/net/pse-pd/ |
| D | pse-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/pse-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 power over twisted pair/ethernet cable. The ethernet-pse nodes should be
12 used to describe PSE controller and referenced by the ethernet-phy node.
15 - Oleksij Rempel <o.rempel@pengutronix.de>
16 - Kory Maincent <kory.maincent@bootlin.com>
20 pattern: "^ethernet-pse(@.*|-([0-9]|[1-9][0-9]+))?$"
22 "#pse-cells":
[all …]
|
| D | ti,tps23881.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/ti,tps23881.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kory Maincent <kory.maincent@bootlin.com>
13 - $ref: pse-controller.yaml#
18 - ti,tps23881
23 '#pse-cells':
26 reset-gpios:
38 "#address-cells":
[all …]
|
| D | microchip,pd692x0.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/microchip,pd692x0.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kory Maincent <kory.maincent@bootlin.com>
13 - $ref: pse-controller.yaml#
18 - microchip,pd69200
19 - microchip,pd69210
20 - microchip,pd69220
36 physical ports available on a manager have to be described in the
[all …]
|
| /Documentation/ABI/removed/ |
| D | video1394 | 1 What: video1394 (a.k.a. "OHCI-1394 Video support" for FireWire)
3 Contact: linux1394-devel@lists.sourceforge.net
7 alternative to raw1394's isochronous I/O functionality which had
12 Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
13 firewire-core.
16 libdc1394 (works with firewire-cdev too, transparent to library ABI
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-dma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/stm32/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
14 channel: a phandle to the DMA controller plus the following four integer cells:
17 3. A 32bit mask specifying the DMA channel configuration which are device
19 -bit 9: Peripheral Increment Address
22 -bit 10: Memory Increment Address
[all …]
|
| /Documentation/arch/x86/ |
| D | topology.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 The architecture-agnostic topology definitions are in
12 Documentation/admin-guide/cputopology.rst. This file holds x86-specific
17 Needless to say, code should use the generic functions - this file is *only*
26 The kernel does not care about the concept of physical sockets because a
28 the past a socket always contained a single package (see below), but with the
29 advent of Multi Chip Modules (MCM) a socket can hold more than one package. So
33 The topology of a system is described in the units of:
35 - packages
36 - cores
[all …]
|
| D | zero-page.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 The additional fields in struct boot_params as a part of 32-bit boot
7 protocol of kernel. These should be filled by bootloader or 16-bit
8 real-mode setup code of the kernel. References/settings to it mainly
34 1E0/004 ALL alt_mem_k Alternative mem check, in KB
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 2 zram: Compressed RAM-based block devices
8 The zram module creates RAM-based block devices named /dev/zram<id>
20 There are several ways to configure and manage zram device(-s):
22 a) using zram and zram_control sysfs attributes
23 b) using zramctl utility, provided by util-linux (util-linux@vger.kernel.org).
28 In order to get a better idea about zramctl please consult util-linux
29 documentation, zramctl man-page or `zramctl --help`. Please be informed
30 that zram maintainers do not develop/maintain util-linux or zramctl, should
31 you have any questions please contact util-linux@vger.kernel.org
33 Following shows a typical sequence of steps for using zram.
[all …]
|
| /Documentation/devicetree/bindings/cache/ |
| D | starfive,jh8100-starlink-cache.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cache/starfive,jh8100-starlink-cache.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Joshua Yeong <joshua.yeong@starfivetech.com>
14 clusters of CPU cores. The cache driver enables RISC-V non-standard cache
15 management as an alternative to instructions in the RISC-V Zicbom extension.
18 - $ref: /schemas/cache-controller.yaml#
20 # We need a select here so we don't match all nodes with 'cache'
26 - starfive,jh8100-starlink-cache
[all …]
|
| /Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
13 A USB connector node represents a physical USB connector. It should be a child
14 of a USB interface controller or a separate node when it is attached to both
20 - enum:
21 - usb-a-connector
22 - usb-b-connector
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | toshiba,et8ek8.txt | 6 Documentation/devicetree/bindings/media/video-interfaces.txt .
10 --------------------
12 - compatible: "toshiba,et8ek8"
13 - reg: I2C address (0x3e, or an alternative address)
14 - vana-supply: Analogue voltage supply (VANA), 2.8 volts
15 - clocks: External clock to the sensor
16 - clock-frequency: Frequency of the external clock to the sensor. Camera
18 a pre-determined frequency known to be suitable to the board.
19 - reset-gpios: XSHUTDOWN GPIO. The XSHUTDOWN signal is active low. The sensor
24 -------------------
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm6345-l1-intc.txt | 1 Broadcom BCM6345-style Level 1 interrupt controller
3 This block is a first level interrupt controller that is typically connected
8 - 32, 64 or 128 incoming level IRQ lines
10 - Most onchip peripherals are wired directly to an L1 input
12 - A separate instance of the register set for each CPU, allowing individual
15 - Contains one or more enable/status word pairs per CPU
17 - No atomic set/clear operations
19 - No polarity/level/edge settings
21 - No FIFO or priority encoder logic; software is expected to read all
22 2-4 status words to determine which IRQs are pending
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 19 Storage vendors, so this network filesystem client can mount to a
27 POSIX compliance, secure per-user session establishment, encryption,
32 the combination can provide a reasonable alternative to other network and
36 This filesystem has a mount utility (mount.cifs) and various user space
39 https://git.samba.org/?p=cifs-utils.git
43 git://git.samba.org/cifs-utils.git
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
11 # drivers if they share a common core requirement and use disjoint semantics to
13 # use "select". For instance it means if a driver A and driver B share the same
15 # annotate this, all features that driver A selects cannot now be negated by
18 # A perhaps not so obvious implication of this is that, if semantics on these
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
24 # describes a simple driver core layout of example features a kernel might
25 # have. Let's assume we have some CORE functionality, then the kernel has a
29 # CORE_BELL_A then CORE_BELL_A ends up becoming a common BELL feature which
34 # under 'select' for a symbol, when such symbols are selected kconfig them
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | richtek,rt1719.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1719 sink-only Type-C PD controller
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT1719 is a sink-only USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
17 support for alternative interfaces of the Type-C specification.
22 - richtek,rt1719
30 wakeup-source:
[all …]
|
| D | richtek,rt1711h.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT1711H Type-C Port Switch and Power Delivery controller
10 - Gene Chen <gene_chen@richtek.com>
13 The RT1711H is a USB Type-C controller that complies with the latest
14 USB Type-C and PD standards. It does the USB Type-C detection including attach
17 support for alternative interfaces of the Type-C specification.
22 - richtek,rt1711h
23 - richtek,rt1715
[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
23 "#address-cells":
26 "#size-cells":
29 read-only:
34 wp-gpios:
36 GPIO to which the write-protect pin of the chip is connected.
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wolfram Sang <wsa@kernel.org>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
24 from <dt-bindings/gpio/gpio.h> since the signal is by definition
28 scl-gpios:
[all …]
|
| /Documentation/hwmon/ |
| D | nzxt-smart2.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver nzxt-smart2
8 - NZXT RGB & Fan controller
9 - NZXT Smart Device v2
12 -----------
21 Also, the device has a noise sensor, but the sensor seems to be completely
25 -----------
32 device has a dedicated "detect fans" command, and currently, it is executed only
34 reload. As an alternative to reloading the module, a userspace tool (like
43 -------------
[all …]
|
| /Documentation/admin-guide/media/ |
| D | lmedm04.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 -------------------------------------------
19 .. code-block:: none
23 will produce dvb-usb-lme2510c-s7395.fw
25 An alternative but older firmware can be found on the driver
26 disk DVB-S_EN_3.5A in BDADriver/driver
32 .. code-block:: none
36 will produce dvb-usb-lme2510c-s7395.fw
39 disk DM04+_5.1A[LG] in BDADriver/driver
42 ---------------------------
[all …]
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | gpu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Rob Clark <robdclark@gmail.com>
14 # as a work-around:
20 - qcom,adreno
21 - amd,imageon
23 - compatible
28 - description: |
30 figure out the chip-id.
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | xlnx,versal-clk.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/xlnx,versal-clk.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michal Simek <michal.simek@amd.com>
13 The clock controller is a hardware block of Xilinx versal clock tree. It
20 - enum:
21 - xlnx,versal-clk
22 - xlnx,zynqmp-clk
23 - items:
[all …]
|
| /Documentation/filesystems/ |
| D | automount-support.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 fs/nfs/). This facility includes allowing in-kernel mounts to be
15 In-Kernel Automounting
22 [root@andromeda root]# mount -t afs \#root.afs. /afs
28 ChangeLog html LICENSE pdf RELNOTES-1.2.2
50 (2) When a new mountpoint is created in the ->d_automount method, add
56 with a pointer to this list. This will process the list, marking every
59 If a vfsmount was already flagged for expiry, and if its usage count is 1
70 If a mountpoint is moved, it gets removed from the expiration list. If a bind
74 If a namespace is copied, all mountpoints contained therein will be copied,
[all …]
|
| /Documentation/virt/hyperv/ |
| D | clocks.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----
8 On arm64, Hyper-V virtualizes the ARMv8 architectural system counter
12 architectural system counter is functional in guest VMs on Hyper-V.
13 While Hyper-V also provides a synthetic system clock and four synthetic
14 per-CPU timers as described in the TLFS, they are not used by the
15 Linux kernel in a Hyper-V guest on arm64. However, older versions
16 of Hyper-V for arm64 only partially virtualize the ARMv8
19 Linux kernel versions on these older Hyper-V versions requires an
20 out-of-tree patch to use the Hyper-V synthetic clocks/timers instead.
[all …]
|
1234567