| /linux/Documentation/devicetree/bindings/net/bluetooth/ |
| H A D | nokia,h4p-bluetooth.txt | 2 --------------------- 5 vendors and modified device API. Those devices speak a protocol named H4+ 6 (also known as h4p) by Nokia, which is similar to the H4 protocol from the 7 Bluetooth standard. In addition to the H4 protocol it specifies two more 13 - compatible: should contain "nokia,h4p-bluetooth" as well as one of the following: 14 * "brcm,bcm2048-nokia" 15 * "ti,wl1271-bluetooth-nokia" 16 - reset-gpios: GPIO specifier, used to reset the BT module (active low) 17 - bluetooth-wakeup-gpios: GPIO specifier, used to wakeup the BT module (active high) 18 - host-wakeup-gpios: GPIO specifier, used to wakeup the host processor (active high) [all …]
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | nvidia,tegra30-mc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra30-mc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Dmitry Osipenko <digetx@gmail.com> 11 - Jon Hunter <jonathanh@nvidia.com> 12 - Thierry Reding <thierry.reding@gmail.com> 22 Protocol Arbiter, which manage a related pool of memory devices. A system 23 may have a single Protocol Arbiter or multiple Protocol Arbiters. 26 Domains and Protocol Arbiters. In the simplest version of the system, the [all …]
|
| H A D | snps,dw-umctl2-ddrc.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/snps,dw-umctl2-ddrc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Synopsys DesignWare Universal Multi-Protocol Memory Controller 10 - Krzysztof Kozlowski <krzk@kernel.org> 11 - Michal Simek <michal.simek@amd.com> 15 working with the memory devices supporting up to (LP)DDR4 protocol. It can 17 16-bits or 32-bits or 64-bits wide. 20 controller. It has an optional SEC/DEC ECC support in 64- and 32-bits [all …]
|
| /linux/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-facebook-greatlakes.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later 4 /dts-v1/; 5 #include "aspeed-g6.dtsi" 6 #include <dt-bindings/gpio/aspeed-gpio.h> 7 #include <dt-bindings/leds/leds-pca955x.h> 8 #include <dt-bindings/i2c/i2c.h> 12 compatible = "facebook,greatlakes-bmc", "aspeed,ast2600"; 23 iio-hwmon { 24 compatible = "iio-hwmon"; 25 io-channels = <&adc0 0>, <&adc0 1>, <&adc0 2>, <&adc0 3>, [all …]
|
| /linux/Documentation/i2c/ |
| H A D | smbus-protocol.rst | 2 The SMBus Protocol 5 The following is a summary of the SMBus protocol. It applies to 6 all revisions of the protocol (1.0, 1.1, and 2.0). 7 Certain protocol features which are not supported by 10 Some adapters understand only the SMBus (System Management Bus) protocol, 11 which is a subset from the I2C protocol. Fortunately, many devices use 16 I2C protocol). This makes it possible to use the device driver on both 21 Below is a list of SMBus protocol operations, and the functions executing 22 them. Note that the names used in the SMBus protocol specifications usually 23 don't match these function names. For some of the operations which pass a [all …]
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | arm,scpi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: System Control and Power Interface (SCPI) Message Protocol 11 - Sudeep Holla <sudeep.holla@arm.com> 33 - const: arm,scpi # SCPI v1.0 and above 34 - const: arm,scpi-pre-1.0 # Unversioned SCPI before v1.0 35 - items: 36 - enum: 37 - amlogic,meson-gxbb-scpi [all …]
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | phy-cadence-torrent.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/phy/phy-cadence-torrent.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 16 - Swapnil Jakhade <sjakhade@cadence.com> 17 - Yuti Amonkar <yamonkar@cadence.com> 22 - cdns,torrent-phy 23 - ti,j7200-serdes-10g 24 - ti,j721e-serdes-10g 26 '#address-cells': [all …]
|
| /linux/drivers/staging/axis-fifo/ |
| H A D | axis-fifo.txt | 1 Xilinx AXI-Stream FIFO v4.1 IP core 3 This IP core has read and write AXI-Stream FIFOs, the contents of which can 4 be accessed from the AXI4 memory-mapped interface. This is useful for 11 Currently supports only store-forward mode with a 32-bit 12 AXI4-Lite interface. DOES NOT support: 13 - cut-through mode 14 - AXI4 (non-lite) 17 - compatible: Should be one of: 18 "xlnx,axi-fifo-mm-s-4.1" 19 "xlnx,axi-fifo-mm-s-4.2" [all …]
|
| /linux/sound/firewire/fireface/ |
| H A D | ff.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * ff.c - a part of driver for RME Fireface series 5 * Copyright (c) 2015-2017 Takashi Sakamoto 13 MODULE_AUTHOR("Takashi Sakamoto <o-takashi@sakamocchi.jp>"); 18 struct fw_device *fw_dev = fw_parent_device(ff->unit); in name_card() 19 static const char *const names[] = { in name_card() local 28 name = names[ff->unit_version]; in name_card() 30 strscpy(ff->card->driver, "Fireface"); in name_card() 31 strscpy(ff->card->shortname, name); in name_card() 32 strscpy(ff->card->mixername, name); in name_card() [all …]
|
| /linux/arch/arm64/boot/dts/arm/ |
| H A D | juno-scmi.dtsi | 3 power-domains = <&scmi_devpd 8>; 7 power-domains = <&scmi_devpd 8>; 11 power-domains = <&scmi_devpd 8>; 15 power-domains = <&scmi_devpd 8>; 19 power-domains = <&scmi_devpd 8>; 23 power-domains = <&scmi_devpd 8>; 27 power-domains = <&scmi_devpd 8>; 31 power-domains = <&scmi_devpd 8>; 42 /delete-node/ scpi; 47 mbox-names = "tx", "rx"; [all …]
|
| /linux/fs/smb/client/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 28 protocol. CIFS was the successor to the original network filesystem 29 protocol, Server Message Block (SMB ie SMB1), the native file sharing 32 The SMB3.1.1 protocol is supported by most modern operating systems 35 Linux kernel server, ksmbd. Support for the older CIFS protocol was 43 for DFS (hierarchical name space), secure per-user session 45 security features, per-share encryption, packet-signing, snapshots, 63 value of /proc/fs/cifs/cifsFYI). See Documentation/admin-guide/cifs/usage.rst 76 man-in-the-middle attacks and stronger crypto hashes, so the use 101 servers without the user namespace prefix, but their names are [all …]
|
| /linux/arch/arm64/boot/dts/freescale/ |
| H A D | imx95.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0-only OR MIT) 6 #include <dt-bindings/clock/nxp,imx95-clock.h> 7 #include <dt-bindings/dma/fsl-edma.h> 8 #include <dt-bindings/gpio/gpio.h> 9 #include <dt-bindings/input/input.h> 10 #include <dt-bindings/interrupt-controller/arm-gic.h> 11 #include <dt-bindings/thermal/thermal.h> 13 #include "imx95-clock.h" 14 #include "imx95-pinfunc.h" 15 #include "imx95-power.h" [all …]
|
| H A D | fsl-ls1028a-kontron-sl28.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 3 * Device Tree file for the Kontron SMARC-sAL28 board. 9 /dts-v1/; 10 #include "fsl-ls1028a.dtsi" 11 #include <dt-bindings/interrupt-controller/irq.h> 12 #include <dt-bindings/gpio/gpio.h> 13 #include <dt-bindings/input/input.h> 16 model = "Kontron SMARC-sAL28"; 33 compatible = "gpio-keys"; 35 power-button { [all …]
|
| /linux/drivers/hsi/clients/ |
| H A D | nokia-modem.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * nokia-modem.c 45 dev_info(modem->device, "CMT rst line change detected\n"); in do_nokia_modem_rst_ind_tasklet() 47 if (modem->ssi_protocol) in do_nokia_modem_rst_ind_tasklet() 48 ssip_reset_event(modem->ssi_protocol); in do_nokia_modem_rst_ind_tasklet() 55 tasklet_schedule(&modem->nokia_modem_rst_ind_tasklet); in nokia_modem_rst_ind_isr() 65 for (i = 0; i < modem->gpio_amount; i++) { in nokia_modem_gpio_unexport() 66 sysfs_remove_link(&dev->kobj, modem->gpios[i].name); in nokia_modem_gpio_unexport() 67 gpiod_unexport(modem->gpios[i].gpio); in nokia_modem_gpio_unexport() 73 struct device_node *np = dev->of_node; in nokia_modem_gpio_probe() [all …]
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | baikal,bt1-apb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/bus/baikal,bt1-apb.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Baikal-T1 APB-bus 11 - Serge Semin <fancer.lancer@gmail.com> 14 Baikal-T1 CPU or DMAC MMIO requests are handled by the AMBA 3 AXI Interconnect 15 which routes them to the AXI-APB bridge. This interface is a single master 17 addressed APB slave devices. In case of any APB protocol collisions, slave 22 - $ref: /schemas/simple-bus.yaml# [all …]
|
| H A D | baikal,bt1-axi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/bus/baikal,bt1-axi.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Baikal-T1 AXI-bus 11 - Serge Semin <fancer.lancer@gmail.com> 14 AXI3-bus is the main communication bus of Baikal-T1 SoC connecting all 15 high-speed peripheral IP-cores with RAM controller and with MIPS P5600 20 some peripherals). In case of any protocol error, device not responding 23 accessible by means of the Baikal-T1 System Controller. [all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | qcom,bam-dmux.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/qcom,bam-dmux.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Stephan Gerhold <stephan@gerhold.net> 15 or MSM8974. It is built using a simple protocol layer on top of a DMA engine 25 const: qcom,bam-dmux 32 - description: Power control 33 - description: Power control acknowledgment 35 interrupt-names: [all …]
|
| H A D | loongson,ls1b-gmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/loongson,ls1b-gmac.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Loongson-1B Gigabit Ethernet MAC Controller 10 - Keguang Zhang <keguang.zhang@gmail.com> 13 Loongson-1B Gigabit Ethernet MAC Controller is based on 17 - Dual 10/100/1000Mbps GMAC controllers 18 - Full-duplex operation (IEEE 802.3x flow control automatic transmission) 19 - Half-duplex operation (CSMA/CD Protocol and back-pressure support) [all …]
|
| H A D | loongson,ls1c-emac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/loongson,ls1c-emac.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Loongson-1C Ethernet MAC Controller 10 - Keguang Zhang <keguang.zhang@gmail.com> 13 Loongson-1C Ethernet MAC Controller is based on 17 - 10/100Mbps 18 - Full-duplex operation (IEEE 802.3x flow control automatic transmission) 19 - Half-duplex operation (CSMA/CD Protocol and back-pressure support) [all …]
|
| H A D | renesas,ethertsn.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: Renesas Ethernet TSN End-station 10 - Niklas Söderlund <niklas.soderlund@ragnatech.se> 14 Gbps full-duplex link via MII/GMII/RMII/RGMII. Depending on the connected PHY. 17 - $ref: ethernet-controller.yaml# 22 - enum: 23 - renesas,r8a779g0-ethertsn # R-Car V4H 24 - const: renesas,rcar-gen4-ethertsn [all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-ocfs2 | 3 Contact: ocfs2-devel@lists.linux.dev 6 ocfs2-tools to interact with the filesystem. 10 Contact: ocfs2-devel@lists.linux.dev 17 The protocol version has a major and minor number. Two 19 major number and an overlapping minor number - thus, 21 sporting version 1.8, as long as both use the 1.8 protocol. 26 This file is read-only. The value is compiled into the 31 Contact: ocfs2-devel@lists.linux.dev 38 * 'o2cb' - The classic o2cb cluster stack that ocfs2 has 40 * 'user' - A plugin supporting userspace cluster software [all …]
|
| H A D | sysfs-class-mei | 6 The mei/ class sub-directory belongs to mei device class 36 Description: Display the negotiated HBM protocol version. 38 The HBM protocol version negotiated 45 Description: Display the driver HBM protocol version. 47 The HBM protocol version supported by the driver. 102 names. 104 - mei: generic mei device. 105 - itouch: itouch (ipts) mei device.
|
| /linux/security/apparmor/ |
| H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0 4 obj-$(CONFIG_SECURITY_APPARMOR) += apparmor.o 6 apparmor-y := apparmorfs.o audit.o capability.o task.o ipc.o lib.o match.o \ 10 apparmor-$(CONFIG_SECURITY_APPARMOR_HASH) += crypto.o 12 obj-$(CONFIG_SECURITY_APPARMOR_KUNIT_TEST) += apparmor_policy_unpack_test.o 13 apparmor_policy_unpack_test-objs += policy_unpack_test.o 15 clean-files := capability_names.h rlim_names.h net_names.h 17 # Build a lower case string table of address family names 20 # #define AF_INET 2 /* Internet IP Protocol */ 27 # #define AF_INET 2 /* Internet IP Protocol */ [all …]
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | st-rc.txt | 1 Device-Tree bindings for ST IRB IP 4 - compatible: Should contain "st,comms-irb". 5 - reg: Base physical address of the controller and length of memory 7 - interrupts: interrupt-specifier for the sole interrupt generated by 10 - rx-mode: can be "infrared" or "uhf". This property specifies the L1 11 protocol used for receiving remote control signals. rx-mode should 13 - tx-mode: should be "infrared". This property specifies the L1 14 protocol used for transmitting remote control signals. tx-mode should 18 - pinctrl-names, pinctrl-0: the pincontrol settings to configure muxing 20 - clocks : phandle with clock-specifier pair for IRB. [all …]
|
| /linux/Documentation/devicetree/bindings/serial/ |
| H A D | nvidia,tegra194-tcu.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/serial/nvidia,tegra194-tcu.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Thierry Reding <thierry.reding@gmail.com> 11 - Jonathan Hunter <jonathanh@nvidia.com> 15 systems within the Tegra SoC. It is implemented through a mailbox- 16 based protocol where each "virtual UART" has a pair of mailboxes, one 26 - const: nvidia,tegra194-tcu 27 - items: [all …]
|