Searched +full:master +full:- +full:kernel (Results 1 – 25 of 222) sorted by relevance
123456789
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 6 --------------- 16 ------------------ 28 update <old_keyid> <new_keyid> - enable or update passphrase. 29 disable <keyid> - disable enabled security and remove key. 30 freeze - freeze changing of security states. 31 erase <keyid> - delete existing user encryption key. 32 overwrite <keyid> - wipe the entire nvdimm. 33 master_update <keyid> <new_keyid> - enable or update master passphrase. 34 master_erase <keyid> - delete existing user encryption key. 37 ----------------- [all …]
|
| /Documentation/scsi/ |
| D | advansys.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 RISC-based, Bus-Mastering, Fast (10 Mhz) and Ultra (20 Mhz) Narrow 9 (8-bit transfer) SCSI Host Adapters for the ISA, EISA, VL, and PCI 10 buses and RISC-based, Bus-Mastering, Ultra (20 Mhz) Wide (16-bit 21 - ABP-480 - Bus-Master CardBus (16 CDB) 24 - ABP510/5150 - Bus-Master ISA (240 CDB) 25 - ABP5140 - Bus-Master ISA PnP (16 CDB) 26 - ABP5142 - Bus-Master ISA PnP with floppy (16 CDB) 27 - ABP902/3902 - Bus-Master PCI (16 CDB) 28 - ABP3905 - Bus-Master PCI (16 CDB) [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-soundwire-master | 1 What: /sys/bus/soundwire/devices/sdw-master-<N>/revision 2 /sys/bus/soundwire/devices/sdw-master-<N>/clk_stop_modes 3 /sys/bus/soundwire/devices/sdw-master-<N>/clk_freq 4 /sys/bus/soundwire/devices/sdw-master-<N>/clk_gears 5 /sys/bus/soundwire/devices/sdw-master-<N>/default_col 6 /sys/bus/soundwire/devices/sdw-master-<N>/default_frame_rate 7 /sys/bus/soundwire/devices/sdw-master-<N>/default_row 8 /sys/bus/soundwire/devices/sdw-master-<N>/dynamic_shape 9 /sys/bus/soundwire/devices/sdw-master-<N>/err_threshold 10 /sys/bus/soundwire/devices/sdw-master-<N>/max_clk_freq [all …]
|
| D | sysfs-bus-i3c | 1 What: /sys/bus/i3c/devices/i3c-<bus-id> 3 Contact: linux-i3c@vger.kernel.org 5 An I3C bus. This directory will contain one sub-directory per 8 What: /sys/bus/i3c/devices/i3c-<bus-id>/current_master 10 Contact: linux-i3c@vger.kernel.org 12 Expose the master that owns the bus (<bus-id>-<master-pid>) at 17 What: /sys/bus/i3c/devices/i3c-<bus-id>/mode 19 Contact: linux-i3c@vger.kernel.org 21 I3C bus mode. Can be "pure", "mixed-fast" or "mixed-slow". See 25 What: /sys/bus/i3c/devices/i3c-<bus-id>/i3c_scl_frequency [all …]
|
| /Documentation/driver-api/i3c/ |
| D | master-driver-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 I3C master controller driver API 7 .. kernel-doc:: drivers/i3c/master.c 9 .. kernel-doc:: include/linux/i3c/master.h
|
| /Documentation/networking/ |
| D | vrf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 routing and forwarding domains (aka VRFs, VRF-lite to be specific) in the 12 Linux network stack. One use case is the multi-tenancy problem where each 30 ------ 34 +-----------------------------+ 35 | vrf-blue | ===> route table 10 36 +-----------------------------+ 38 +------+ +------+ +-------------+ 40 +------+ +------+ +-------------+ 42 +------+ +------+ [all …]
|
| /Documentation/w1/ |
| D | w1-netlink.rst | 10 1. Events. They are generated each time a new master or slave device 21 [struct cn_msg] - connector header. 23 [struct w1_netlink_msg] - w1 netlink header. 24 __u8 type - message type. 30 master add/remove events 32 userspace command for bus master 37 __u8 status - error indication from kernel 38 __u16 len - size of data attached to this header data 40 __u8 id[8]; - slave unique device id 42 __u32 id; - master's id [all …]
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 5 The GPIO based I2C bus master driver can be configured to provide fault 7 which is driven by the I2C bus master driver under test. The GPIO fault 9 master driver should handle gracefully. 12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually 13 mounted at /sys/kernel/debug. There will be a separate subdirectory per GPIO 15 injection. They will be described now along with their intended use-cases. 21 ----- 26 because the bus master under test will not be able to clock. It should detect 31 ----- 36 master under test should detect this condition and trigger a bus recovery (see [all …]
|
| D | dma-considerations.rst | 5 Given that I2C is a low-speed bus, over which the majority of messages 7 time of writing, only 10% of I2C bus master drivers have DMA support 13 rarely used. However, it is recommended to use a DMA-safe buffer if your 18 I2C bus master driver is using USB as a bridge, then you need to have DMA 22 ------- 30 that setting this flag makes only sense in kernel space. User space data is 31 copied into kernel space anyhow. The I2C core makes sure the destination 32 buffers in kernel space are always DMA capable. Also, when the core emulates 40 ------- 42 Bus master drivers wishing to implement safe DMA can use helper functions from [all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm-master-stats.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/qcom/qcom,rpm-master-stats.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm Technologies, Inc. (QTI) RPM Master Stats 10 - Konrad Dybcio <konradybcio@kernel.org> 16 (particularly around entering hardware-driven low power modes: XO shutdown 17 and total system-wide power collapse) are first made at Master-level, and 20 The Master Stats provide a few useful bits that can be used to assess whether 21 our device has entered the desired low-power mode, how long it took to do so, [all …]
|
| D | qcom,smp2p.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Andy Gross <agross@kernel.org> 11 - Bjorn Andersson <bjorn.andersson@linaro.org> 12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 16 of a single 32-bit value between two processors. Each value has a single 35 $ref: /schemas/types.yaml#/definitions/phandle-array 37 - items: 38 - description: phandle to a syscon node representing the APCS registers [all …]
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 .. _dsa-config-showcases: 13 ----------------------- 30 at https://www.kernel.org/pub/linux/utils/net/iproute2/ 38 to send or receive traffic. Prior to kernel v5.12, the state of the conduit 39 interface had to be managed explicitly by the user. Starting with kernel v5.12, 42 - when a DSA user interface is brought up, the conduit interface is 44 - when the conduit interface is brought down, all DSA user interfaces are 71 * lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3) 72 * lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7) [all …]
|
| /Documentation/trace/ |
| D | stm.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 which is assigned a unique pair of master and channel. While some of 14 master/channel combination from this pool. 17 sources can only be identified by master/channel combination, so in 20 master/channel pairs to the trace sources that it understands. 23 master 7 channel 15, while arbitrary user applications can use masters 34 associated with it, located in "stp-policy" subsystem directory in 40 $ ls /config/stp-policy/dummy_stm.my-policy/user 42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters 44 $ cat /config/stp-policy/dummy_stm.my-policy/user/channels [all …]
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e17.rst | 2 Kernel driver w1_ds28e17 7 * Maxim DS28E17 1-Wire-to-I2C Master Bridge 19 ----------- 20 The DS28E17 is a Onewire slave device which acts as an I2C bus master. 24 a DS28E17 can be accessed by the kernel or userspace tools as if they were 25 connected to a "native" I2C bus master. 30 SUBSYSTEM=="i2c-dev", KERNEL=="i2c-[0-9]*", ATTRS{name}=="w1-19-*", \ 31 SYMLINK+="i2c-$attr{name}" 33 may be used to create stable /dev/i2c- entries based on the unique id of the 41 it is connected. The power-on default of the DS28E17 is 400kBaud, but [all …]
|
| /Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data 8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full 12 additional chipselect line is usually active-low (nCS); four signals are 18 only "master" side interfaces are supported, where Linux talks to SPI 29 <spi_controller>`. SPI devices are children of that master, 33 board-specific initialization code. A :c:type:`struct spi_driver 46 .. kernel-doc:: include/linux/spi/spi.h 49 .. kernel-doc:: drivers/spi/spi.c 52 .. kernel-doc:: drivers/spi/spi.c
|
| D | w1.rst | 2 W1: Dallas' 1-wire bus 7 W1 API internal to the kernel 13 W1 kernel API functions. 15 .. kernel-doc:: include/linux/w1.h 23 .. kernel-doc:: drivers/w1/w1.c 31 .. kernel-doc:: drivers/w1/w1_family.c 37 W1 internal initialization for master devices. 39 .. kernel-doc:: drivers/w1/w1_internal.h 45 W1 internal initialization for master devices. 47 .. kernel-doc:: drivers/w1/w1_int.c [all …]
|
| D | i2c.rst | 5 the "Inter-IC" bus, a simple bus protocol which is widely used where low 7 some vendors use another name (such as "Two-Wire Interface", TWI) for 12 I2C is a multi-master bus; open drain signaling is used to arbitrate 16 The Linux I2C programming interfaces support the master side of bus 38 .. kernel-doc:: include/linux/i2c.h 41 .. kernel-doc:: drivers/i2c/i2c-boardinfo.c 44 .. kernel-doc:: drivers/i2c/i2c-core-base.c 47 .. kernel-doc:: drivers/i2c/i2c-core-smbus.c
|
| /Documentation/devicetree/bindings/i3c/ |
| D | cdns,i3c-master.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/i3c/cdns,i3c-master.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Cadence I3C master block 10 - Boris Brezillon <bbrezillon@kernel.org> 13 - $ref: i3c.yaml# 17 const: cdns,i3c-master 25 clock-names: 27 - const: pclk [all …]
|
| /Documentation/translations/it_IT/i2c/ |
| D | summary.rst | 6 kernel) è un protocollo sviluppato da Philips. É un protocollo lento a 2 fili 14 L'ultima specifica ufficiale I2C è la `"Specifica I2C-bus e manuale utente" 20 https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_. 40 uno o più circuiti integrati *master* e uno o più circuiti integrati *slave*. 42 .. kernel-figure:: ../../../i2c/i2c_bus.svg 43 :alt: Un semplice bus I2C con un master e 3 slave 47 Un circuito integrato **master** è un nodo che inizia le comunicazioni con gli 48 slave. Nell'implementazione del kernel Linux è chiamato **adattatore** o bus. I 57 quando indirizzato dal master. In Linux è chiamato **client** (dispositivo). I
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 9 either in kernel space or in user space with a daemon called 'ecryptfsd'. In 10 the former case the operation is performed directly by the kernel CryptoAPI 18 kernel key of the 'user' type, inserted in the user's session specific keyring 20 'ecryptfs-utils'. 26 kernel and protected by the parent master key. 28 In order to avoid known-plaintext attacks, the datablob obtained through 38 kernel level. 42 keyctl add encrypted name "new ecryptfs key-type:master-key-name keylen" ring 44 keyctl update keyid "update key-type:master-key-name" 49 key-type:= 'trusted' | 'user' [all …]
|
| /Documentation/mm/damon/ |
| D | maintainer-profile.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 linux-mm@kvack.org. Patches should be made against the `mm-unstable tree 11 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ whenever possible and posted 15 --------- 19 <https://git.kernel.org/sj/h/damon/next>`_ by the DAMON maintainer. 20 Sufficiently reviewed patches will be queued in `mm-unstable 21 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ by the memory management 23 in `mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_, and finally 24 pull-requested to the mainline by the memory management subsystem maintainer. 26 Note again the patches for `mm-unstable tree [all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for 8 is publicly available for download from the RTA web-site [1]. 17 into the kernel similarly to other buses by defining RapidIO-specific device and 21 architecture-specific interfaces that provide support for common RapidIO 32 2.1 Master Port 33 --------------- 35 A master port (or mport) is a RapidIO interface controller that is local to the 36 processor executing the Linux code. A master port generates and receives RapidIO 37 packets (transactions). In the RapidIO subsystem each master port is represented 38 by a rio_mport data structure. This structure contains master port specific [all …]
|
| /Documentation/filesystems/ |
| D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt) 11 Note: "fscrypt" in this document refers to the kernel-level portion, 14 covers the kernel-level portion. For command-line examples of how to 20 <https://source.android.com/security/encryption/file-based>`_, over 21 using the kernel's API directly. Using existing tools reduces the 23 completeness this documentation covers the kernel's API anyway.) 25 Unlike dm-crypt, fscrypt operates at the filesystem level rather than 28 filesystem. This is useful for multi-user systems where each user's 29 data-at-rest needs to be cryptographically isolated from the others. 34 directly into supported filesystems --- currently ext4, F2FS, UBIFS, [all …]
|
| /Documentation/w1/masters/ |
| D | omap-hdq.rst | 2 Kernel driver for omap HDQ/1-wire module 7 HDQ/1-wire controller on the TI OMAP 2430/3430 platforms. 15 The HDQ/1-Wire module of TI OMAP2430/3430 platforms implement the hardware 16 protocol of the master functions of the Benchmark HDQ and the Dallas 17 Semiconductor 1-Wire protocols. These protocols use a single wire for 18 communication between the master (HDQ/1-Wire controller) and the slave 19 (HDQ/1-Wire external compliant device). 21 A typical application of the HDQ/1-Wire module is the communication with battery 24 The controller supports operation in both HDQ and 1-wire mode. The essential 25 difference between the HDQ and 1-wire mode is how the slave device responds to [all …]
|
| D | w1-gpio.rst | 2 Kernel driver w1-gpio 9 ----------- 11 GPIO 1-wire bus master driver. The driver uses the GPIO API to control the 13 It is also possible to define the master using device tree, see 14 Documentation/devicetree/bindings/w1/w1-gpio.yaml 17 Example (mach-at91) 18 ------------------- 23 #include <linux/w1-gpio.h> 26 .dev_id = "w1-gpio", 28 GPIO_LOOKUP_IDX("at91-gpio", AT91_PIN_PB20, NULL, 0, [all …]
|
123456789