data_type
large_stringclasses
3 values
source
large_stringclasses
29 values
code
large_stringlengths
98
49.4M
filepath
large_stringlengths
5
161
message
large_stringclasses
234 values
commit
large_stringclasses
234 values
subject
large_stringclasses
418 values
critique
large_stringlengths
101
1.26M
metadata
dict
source
linux
Binding for NVIDIA Tegra20 CPUFreq ================================== Required properties: - clocks: Must contain an entry for the CPU clock. See ../clocks/clock-bindings.txt for details. - operating-points-v2: See ../bindings/opp/opp-v2.yaml for details. - #cooling-cells: Should be 2. See ../thermal/thermal-cooling...
Documentation/devicetree/bindings/cpufreq/nvidia,tegra20-cpufreq.txt
null
null
null
null
null
source
linux
================== C-SKY CPU Bindings ================== The device tree allows to describe the layout of CPUs in a system through the "cpus" node, which in turn contains a number of subnodes (ie "cpu") defining properties for every cpu. Only SMP system need to care about the cpus node and single processor needn't de...
Documentation/devicetree/bindings/csky/cpus.txt
null
null
null
null
null
source
linux
=============================== C-SKY Performance Monitor Units =============================== C-SKY Performance Monitor is designed for ck807/ck810/ck860 SMP soc and it could count cpu's events for helping analysis performance issues. ============================ PMU node bindings definition =======================...
Documentation/devicetree/bindings/csky/pmu.txt
null
null
null
null
null
source
linux
* Cirrus Logic CLPS711X Framebuffer Required properties: - compatible: Shall contain "cirrus,ep7209-fb". - reg : Physical base address and length of the controller's registers + location and size of the framebuffer memory. - clocks : phandle + clock specifier pair of the FB reference clock. - di...
Documentation/devicetree/bindings/display/cirrus,clps711x-fb.txt
null
null
null
null
null
source
linux
Ilitek ILI9225 display panels This binding is for display panels using an Ilitek ILI9225 controller in SPI mode. Required properties: - compatible: "vot,v220hf01a-t", "ilitek,ili9225" - rs-gpios: Register select signal - reset-gpios: Reset pin The node for this driver must be a child node of a SPI controller, hence ...
Documentation/devicetree/bindings/display/ilitek,ili9225.txt
null
null
null
null
null
source
linux
PXA LCD Controller ------------------ Required properties: - compatible : one of these "marvell,pxa2xx-lcdc", "marvell,pxa270-lcdc", "marvell,pxa300-lcdc" - reg : should contain 1 register range (address and length). - interrupts : framebuffer controller interrupt. - clocks: phandle to input clocks Optional pr...
Documentation/devicetree/bindings/display/marvell,pxa2xx-lcdc.txt
null
null
null
null
null
source
linux
PXA3xx GCU Controller --------------------- Required properties: - compatible : "marvell,pxa300-gcu" - reg : should contain the register range (address and length). - interrupts : Controller interrupt. - clocks: phandle to the PXA specific input clock. Example for PXA300: display-controller@54000000 { compati...
Documentation/devicetree/bindings/display/marvell,pxa300-gcu.txt
null
null
null
null
null
source
linux
MIPI DSI (Display Serial Interface) busses ========================================== The MIPI Display Serial Interface specifies a serial bus and a protocol for communication between a host and up to four peripherals. This document will define the syntax used to represent a DSI bus in a device tree. This document de...
Documentation/devicetree/bindings/display/mipi-dsi-bus.txt
null
null
null
null
null
source
linux
Multi-Inno MI0283QT display panel Required properties: - compatible: "multi-inno,mi0283qt". The node for this driver must be a child node of a SPI controller, hence all mandatory properties described in ../spi/spi-bus.txt must be specified. Optional properties: - dc-gpios: D/C pin. The presence/absence of this GPIO ...
Documentation/devicetree/bindings/display/multi-inno,mi0283qt.txt
null
null
null
null
null
source
linux
Pervasive Displays RePaper branded e-ink displays Required properties: - compatible: "pervasive,e1144cs021" for 1.44" display "pervasive,e1190cs021" for 1.9" display "pervasive,e2200cs021" for 2.0" display "pervasive,e2271cs021" for 2.7" display - panel-on-gpios: Timing controller power control - discharge-...
Documentation/devicetree/bindings/display/repaper.txt
null
null
null
null
null
source
linux
* SM SM501 The SM SM501 is a LCD controller, with proper hardware, it can also drive DVI monitors. Required properties: - compatible : should be "smi,sm501". - reg : contain two entries: - First entry: System Configuration register - Second entry: IO space (Display Controller register) - interrupts : SMI inte...
Documentation/devicetree/bindings/display/sm501fb.txt
null
null
null
null
null
source
linux
ARC PGU This is a display controller found on several development boards produced by Synopsys. The ARC PGU is an RGB streamer that reads the data from a framebuffer and sends it to a single digital encoder (usually HDMI). Required properties: - compatible: "snps,arcpgu" - reg: Physical base address and length of ...
Documentation/devicetree/bindings/display/snps,arcpgu.txt
null
null
null
null
null
source
linux
* Solomon SSD1289 Framebuffer Driver Required properties: - compatible: Should be "solomon,ssd1289fb". The only supported bus for now is lbc. - reg: Should contain address of the controller on the LBC bus. The detail was described in Documentation/devicetree/bindings/powerpc/fsl/lbc.txt Examples: display@...
Documentation/devicetree/bindings/display/ssd1289fb.txt
null
null
null
null
null
source
linux
STMicroelectronics stih4xx platforms - sti-vtg: video timing generator Required properties: - compatible: "st,vtg" - reg: Physical base address of the IP registers and length of memory mapped region. Optional properties: - interrupts : VTG interrupt number to the CPU. - st,slave: phandle on a slave vtg - ...
Documentation/devicetree/bindings/display/st,stih4xx.txt
null
null
null
null
null
source
linux
VIA VT8500 Framebuffer ----------------------------------------------------- Required properties: - compatible : "via,vt8500-fb" - reg : Should contain 1 register ranges(address and length) - interrupts : framebuffer controller interrupt - bits-per-pixel : bit depth of framebuffer (16 or 32) Required subnodes: - disp...
Documentation/devicetree/bindings/display/via,vt8500-fb.txt
null
null
null
null
null
source
linux
VIA/Wondermedia Graphics Engine Controller ----------------------------------------------------- Required properties: - compatible : "wm,prizm-ge-rops" - reg : Should contain 1 register ranges(address and length) Example: ge_rops@d8050400 { compatible = "wm,prizm-ge-rops"; reg = <0xd8050400 0x100>; };
Documentation/devicetree/bindings/display/wm,prizm-ge-rops.txt
null
null
null
null
null
source
linux
Wondermedia WM8505 Framebuffer ----------------------------------------------------- Required properties: - compatible : "wm,wm8505-fb" - reg : Should contain 1 register ranges(address and length) - bits-per-pixel : bit depth of framebuffer (16 or 32) Required subnodes: - display-timings: see display-timing.txt for i...
Documentation/devicetree/bindings/display/wm,wm8505-fb.txt
null
null
null
null
null
source
linux
Device Tree bindings for Armada DRM CRTC driver Required properties: - compatible: value should be "marvell,dove-lcd". - reg: base address and size of the LCD controller - interrupts: single interrupt number for the LCD controller - port: video output port with endpoints, as described by graph.txt Optional proper...
Documentation/devicetree/bindings/display/armada/marvell,dove-lcd.txt
null
null
null
null
null
source
linux
Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver A DSI Host Controller resides in the middle of display controller and external HDMI converter or panel. Required properties: - compatible: value should be "hisilicon,hi6220-dsi". - reg: physical base address and length of dsi controller's registers...
Documentation/devicetree/bindings/display/hisilicon/dw-dsi.txt
null
null
null
null
null
source
linux
Device-Tree bindings for hisilicon ADE display controller driver ADE (Advanced Display Engine) is the display controller which grab image data from memory, do composition, do post image processing, generate RGB timing stream and transfer to DSI. Required properties: - compatible: value should be "hisilicon,hi6220-ade...
Documentation/devicetree/bindings/display/hisilicon/hisi-ade.txt
null
null
null
null
null
source
linux
Texas Instruments DRA7x Display Subsystem ========================================= See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic description about OMAP Display Subsystem bindings. DSS Core -------- Required properties: - compatible: "ti,dra7-dss" - reg: address and length of the regis...
Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt
null
null
null
null
null
source
linux
Texas Instruments OMAP Display Subsystem ======================================== Generic Description ------------------- This document is a generic description of the OMAP Display Subsystem bindings. Binding details for each OMAP SoC version are described in respective binding documentation. The OMAP Display Subsys...
Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt
null
null
null
null
null
source
linux
Texas Instruments OMAP2 Display Subsystem ========================================= See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic description about OMAP Display Subsystem bindings. DSS Core -------- Required properties: - compatible: "ti,omap2-dss" - reg: address and length of the regi...
Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt
null
null
null
null
null
source
linux
Texas Instruments OMAP3 Display Subsystem ========================================= See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic description about OMAP Display Subsystem bindings. DSS Core -------- Required properties: - compatible: "ti,omap3-dss" - reg: address and length of the regi...
Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt
null
null
null
null
null
source
linux
Texas Instruments OMAP4 Display Subsystem ========================================= See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic description about OMAP Display Subsystem bindings. DSS Core -------- Required properties: - compatible: "ti,omap4-dss" - reg: address and length of the regi...
Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt
null
null
null
null
null
source
linux
Texas Instruments OMAP5 Display Subsystem ========================================= See Documentation/devicetree/bindings/display/ti/ti,omap-dss.txt for generic description about OMAP Display Subsystem bindings. DSS Core -------- Required properties: - compatible: "ti,omap5-dss" - reg: address and length of the regi...
Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt
null
null
null
null
null
source
linux
TPD12S015 HDMI level shifter and ESD protection chip ==================================================== Required properties: - compatible: "ti,tpd12s015" Optional properties: - gpios: CT CP HPD, LS OE and HPD gpios Required nodes: - Video port 0 for HDMI input - Video port 1 for HDMI output Example ------- tpd12...
Documentation/devicetree/bindings/display/ti/ti,tpd12s015.txt
null
null
null
null
null
source
linux
Device-Tree bindings for tilcdc DRM generic panel output driver Required properties: - compatible: value should be "ti,tilcdc,panel". - panel-info: configuration info to configure LCDC correctly for the panel - ac-bias: AC Bias Pin Frequency - ac-bias-intrpt: AC Bias Pin Transitions per Interrupt - dma-burs...
Documentation/devicetree/bindings/display/tilcdc/panel.txt
null
null
null
null
null
source
linux
Device-Tree bindings for tilcdc DRM driver Required properties: - compatible: value should be one of the following: - "ti,am33xx-tilcdc" for AM335x based boards - "ti,da850-tilcdc" for DA850/AM18x/OMAP-L138 based boards - interrupts: the interrupt number - reg: base address and size of the LCDC device Reco...
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt
null
null
null
null
null
source
linux
* IMG Multi-threaded DMA Controller (MDC) Required properties: - compatible: Must be "img,pistachio-mdc-dma". - reg: Must contain the base address and length of the MDC registers. - interrupts: Must contain all the per-channel DMA interrupts. - clocks: Must contain an entry for each entry in clock-names. See ../cloc...
Documentation/devicetree/bindings/dma/img-mdc-dma.txt
null
null
null
null
null
source
linux
* Hisilicon K3 DMA controller See dma.txt first Required properties: - compatible: Must be one of - "hisilicon,k3-dma-1.0" - "hisilicon,hisi-pcm-asp-dma-1.0" - reg: Should contain DMA registers location and length. - interrupts: Should contain one interrupt shared by all channel - #dma-cells...
Documentation/devicetree/bindings/dma/k3dma.txt
null
null
null
null
null
source
linux
* Milbeaut AHB DMA Controller Milbeaut AHB DMA controller has transfer capability below. - device to memory transfer - memory to device transfer Required property: - compatible: Should be "socionext,milbeaut-m10v-hdmac" - reg: Should contain DMA registers location and length. - interrupts: ...
Documentation/devicetree/bindings/dma/milbeaut-m10v-hdmac.txt
null
null
null
null
null
source
linux
* Milbeaut AXI DMA Controller Milbeaut AXI DMA controller has only memory to memory transfer capability. * DMA controller Required property: - compatible: Should be "socionext,milbeaut-m10v-xdmac" - reg: Should contain DMA registers location and length. - interrupts: Should contain all of the per-channel DMA int...
Documentation/devicetree/bindings/dma/milbeaut-m10v-xdmac.txt
null
null
null
null
null
source
linux
MOXA ART DMA Controller See dma.txt first Required properties: - compatible : Must be "moxa,moxart-dma" - reg : Should contain registers location and length - interrupts : Should contain an interrupt-specifier for the sole interrupt generated by the device - #dma-cells : Should be 1, a single cell holding a line ...
Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt
null
null
null
null
null
source
linux
* Freescale MPC512x and MPC8308 DMA Controller The DMA controller in Freescale MPC512x and MPC8308 SoCs can move blocks of memory contents between memory and peripherals or from memory to memory. Refer to "Generic DMA Controller and DMA request bindings" in the dma/dma.txt file for a more detailed description of bind...
Documentation/devicetree/bindings/dma/mpc512x-dma.txt
null
null
null
null
null
source
linux
* Renesas "Type-AXI" NBPFAXI* DMA controllers * DMA controller Required properties - compatible: must be one of "renesas,nbpfaxi64dmac1b4" "renesas,nbpfaxi64dmac1b8" "renesas,nbpfaxi64dmac1b16" "renesas,nbpfaxi64dmac4b4" "renesas,nbpfaxi64dmac4b8" "renesas,nbpfaxi64dmac4b16" "renesas,nbpfaxi64dmac8b4" ...
Documentation/devicetree/bindings/dma/renesas,nbpfaxi.txt
null
null
null
null
null
source
linux
* STMicroelectronics Flexible Direct Memory Access Device Tree bindings The FDMA is a general-purpose direct memory access controller capable of supporting 16 independent DMA channels. It accepts up to 32 DMA requests. The FDMA is based on a Slim processor which requires a firmware. * FDMA Controller Required proper...
Documentation/devicetree/bindings/dma/st_fdma.txt
null
null
null
null
null
source
linux
Texas Instruments DMA Crossbar (DMA request router) Required properties: - compatible: "ti,dra7-dma-crossbar" for DRA7xx DMA crossbar "ti,am335x-edma-crossbar" for AM335x and AM437x - reg: Memory map for accessing module - #dma-cells: Should be set to match with the DMA controller's dma-cells for ti,dra7-dma-cros...
Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt
null
null
null
null
null
source
linux
Texas Instruments eDMA The eDMA3 consists of two components: Channel controller (CC) and Transfer Controller(s) (TC). The CC is the main entry for DMA users since it is responsible for the DMA channel handling, while the TCs are responsible to execute the actual DMA tansfer. ------------------------------------------...
Documentation/devicetree/bindings/dma/ti-edma.txt
null
null
null
null
null
source
linux
Xilinx AXI VDMA engine, it does transfers between memory and video devices. It can be configured to have one channel or two channels. If configured as two channels, one is to transmit to the video device and another is to receive from the video device. Xilinx AXI DMA engine, it does transfers between memory and AXI4 s...
Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt
null
null
null
null
null
source
linux
Maxim Integrated MAX3355 USB OTG chip ------------------------------------- MAX3355 integrates a charge pump and comparators to enable a system with an integrated USB OTG dual-role transceiver to function as a USB OTG dual-role device. Required properties: - compatible: should be "maxim,max3355"; - maxim,shdn-gpios: ...
Documentation/devicetree/bindings/extcon/extcon-max3355.txt
null
null
null
null
null
source
linux
EXTCON FOR PALMAS/TWL CHIPS PALMAS USB COMPARATOR Required Properties: - compatible: should contain one of: * "ti,palmas-usb-vid". * "ti,twl6035-usb-vid". * "ti,palmas-usb" (DEPRECATED - use "ti,palmas-usb-vid"). * "ti,twl6035-usb" (DEPRECATED - use "ti,twl6035-usb-vid"). Optional Properties: - ti,wakeu...
Documentation/devicetree/bindings/extcon/extcon-palmas.txt
null
null
null
null
null
source
linux
COREBOOT firmware information The device tree node to communicate the location of coreboot's memory-resident bookkeeping structures to the kernel. Since coreboot itself cannot boot a device-tree-based kernel (yet), this node needs to be inserted by a second-stage bootloader (a coreboot "payload"). Required properties...
Documentation/devicetree/bindings/firmware/coreboot.txt
null
null
null
null
null
source
linux
NVIDIA Tegra210 Boot and Power Management Processor (BPMP) The Boot and Power Management Processor (BPMP) is a co-processor found in Tegra210 SoC. It is designed to handle the early stages of the boot process as well as to assisting in entering deep low power state (suspend to ram), and also offloading DRAM memory clo...
Documentation/devicetree/bindings/firmware/nvidia,tegra210-bpmp.txt
null
null
null
null
null
source
linux
Altera Arria10 Partial Reconfiguration IP Required properties: - compatible : should contain "altr,a10-pr-ip" - reg : base address and size for memory mapped io. Example: fpga_mgr: fpga-mgr@ff20c000 { compatible = "altr,a10-pr-ip"; reg = <0xff20c000 0x10>; };
Documentation/devicetree/bindings/fpga/altera-pr-ip.txt
null
null
null
null
null
source
linux
Altera SOCFPGA Arria10 FPGA Manager Required properties: - compatible : should contain "altr,socfpga-a10-fpga-mgr" - reg : base address and size for memory mapped io. - The first index is for FPGA manager register access. - The second index is for writing FPGA configuration data. -...
Documentation/devicetree/bindings/fpga/altera-socfpga-a10-fpga-mgr.txt
null
null
null
null
null
source
linux
Altera SOCFPGA FPGA Manager Required properties: - compatible : should contain "altr,socfpga-fpga-mgr" - reg : base address and size for memory mapped io. - The first index is for FPGA manager register access. - The second index is for writing FPGA configuration data. - interrupts ...
Documentation/devicetree/bindings/fpga/altera-socfpga-fpga-mgr.txt
null
null
null
null
null
source
linux
Lattice MachXO2 Slave SPI FPGA Manager Lattice MachXO2 FPGAs support a method of loading the bitstream over 'slave SPI' interface. See 'MachXO2ProgrammingandConfigurationUsageGuide.pdf' on www.latticesemi.com Required properties: - compatible: should contain "lattice,machxo2-slave-spi" - reg: spi chip select of the ...
Documentation/devicetree/bindings/fpga/lattice-machxo2-spi.txt
null
null
null
null
null
source
linux
FSI bus & engine generic device tree bindings ============================================= The FSI bus is probe-able, so the OS is able to enumerate FSI slaves, and engines within those slaves. However, we have a facility to match devicetree nodes to probed engines. This allows for fsi engines to expose non-probeable...
Documentation/devicetree/bindings/fsi/fsi.txt
null
null
null
null
null
source
linux
Avionic Design N-bit GPIO expander bindings Required properties: - compatible: should be "ad,gpio-adnp" - reg: The I2C slave address for this device. - interrupts: Interrupt specifier for the controllers interrupt. - #gpio-cells: Should be 2. The first cell is the GPIO number and the second cell is used to specify o...
Documentation/devicetree/bindings/gpio/gpio-adnp.txt
null
null
null
null
null
source
linux
Exportable MPIO interface of Exar UART chips Required properties of the device: - exar,first-pin: first exportable pins (0..15) - ngpios: number of exportable pins (1..16)
Documentation/devicetree/bindings/gpio/gpio-exar.txt
null
null
null
null
null
source
linux
Aeroflex Gaisler GRGPIO General Purpose I/O cores. The GRGPIO GPIO core is available in the GRLIB VHDL IP core library. Note: In the ordinary environment for the GRGPIO core, a Leon SPARC system, these properties are built from information in the AMBA plug&play. Required properties: - name : Should be "GAISLER_GPIO...
Documentation/devicetree/bindings/gpio/gpio-grgpio.txt
null
null
null
null
null
source
linux
Cavium ThunderX/OCTEON-TX GPIO controller bindings Required Properties: - reg: The controller bus address. - gpio-controller: Marks the device node as a GPIO controller. - #gpio-cells: Must be 2. - First cell is the GPIO pin number relative to the controller. - Second cell is a standard generic flag bitfield as de...
Documentation/devicetree/bindings/gpio/gpio-thunderx.txt
null
null
null
null
null
source
linux
Specifying GPIO information for devices ======================================= 1) gpios property ----------------- GPIO properties should be named "[<name>-]gpios", with <name> being the purpose of this GPIO for the device. While a non-existent <name> is considered valid for compatibility reasons (resolving to the "...
Documentation/devicetree/bindings/gpio/gpio.txt
null
null
null
null
null
source
linux
GPIO controller on CE4100 / Sodaville SoCs ========================================== The bindings for CE4100's GPIO controller match the generic description which is covered by the gpio.txt file in this folder. The only additional property is the intel,muxctl property which holds the value which is written into the ...
Documentation/devicetree/bindings/gpio/sodaville.txt
null
null
null
null
null
source
linux
Each HSI port is supposed to have one child node, which symbols the remote device connected to the HSI port. The following properties are standardized for HSI clients: Required HSI configuration properties: - hsi-channel-ids: A list of channel ids - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame") ...
Documentation/devicetree/bindings/hsi/client-devices.txt
null
null
null
null
null
source
linux
Nokia modem client bindings The Nokia modem HSI client follows the common HSI client binding and inherits all required properties. The following additional properties are needed by the Nokia modem HSI client: Required properties: - compatible: Should be one of "nokia,n900-modem" "nokia,n950-modem" ...
Documentation/devicetree/bindings/hsi/nokia-modem.txt
null
null
null
null
null
source
linux
OMAP SSI controller bindings OMAP3's Synchronous Serial Interface (SSI) controller implements a legacy variant of MIPI's High Speed Synchronous Serial Interface (HSI), while the controller found inside OMAP4 is supposed to be fully compliant with the HSI standard. Required properties: - compatible: Should include "t...
Documentation/devicetree/bindings/hsi/omap-ssi.txt
null
null
null
null
null
source
linux
Generic hwlock bindings ======================= Generic bindings that are common to all the hwlock platform specific driver implementations. Please also look through the individual platform specific hwlock binding documentations for identifying any additional properties specific to that platform. hwlock providers: =...
Documentation/devicetree/bindings/hwlock/hwlock.txt
null
null
null
null
null
source
linux
ltc2990: Linear Technology LTC2990 power monitor Required properties: - compatible: Must be "lltc,ltc2990" - reg: I2C slave address - lltc,meas-mode: An array of two integers for configuring the chip measurement mode. The first integer defines the bits 2..0 in the control register. In all cases the internal temper...
Documentation/devicetree/bindings/hwmon/ltc2990.txt
null
null
null
null
null
source
linux
max6697 properties Required properties: - compatible: Should be one of maxim,max6581 maxim,max6602 maxim,max6622 maxim,max6636 maxim,max6689 maxim,max6693 maxim,max6694 maxim,max6697 maxim,max6698 maxim,max6699 - reg: I2C address Optional properties: - smbus-timeout-disable Set to disable SMBus...
Documentation/devicetree/bindings/hwmon/max6697.txt
null
null
null
null
null
source
linux
Nuvoton NPCM PWM and Fan Tacho controller device The Nuvoton BMC NPCM7XX supports 8 Pulse-width modulation (PWM) controller outputs and 16 Fan tachometer controller inputs. The Nuvoton BMC NPCM8XX supports 12 Pulse-width modulation (PWM) controller outputs and 16 Fan tachometer controller inputs. Required properties...
Documentation/devicetree/bindings/hwmon/npcm750-pwm-fan.txt
null
null
null
null
null
source
linux
Bindings for the fan / temperature monitor microcontroller used on the Zyxel NSA 320 and several subsequent models. Required properties: - compatible : "zyxel,nsa320-mcu" - data-gpios : The GPIO pin connected to the data line on the MCU - clk-gpios : The GPIO pin connected to the clock line on the MCU - act-gpios : Th...
Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt
null
null
null
null
null
source
linux
Versatile Express hwmon sensors ------------------------------- Requires node properties: - "compatible" value : one of "arm,vexpress-volt" "arm,vexpress-amp" "arm,vexpress-temp" "arm,vexpress-power" "arm,vexpress-energy" - "arm,vexpress-sysreg,func" when controlled via vexpress-sysreg (see Documentation/device...
Documentation/devicetree/bindings/hwmon/vexpress.txt
null
null
null
null
null
source
linux
* Altera I2C Controller * This is Altera's synthesizable logic block I2C Controller for use * in Altera's FPGAs. Required properties : - compatible : should be "altr,softip-i2c-v1.0" - reg : Offset and length of the register set for the device - interrupts : <IRQ> where IRQ is the interrupt number. - clocks...
Documentation/devicetree/bindings/i2c/i2c-altera.txt
null
null
null
null
null
source
linux
LSI Axxia I2C Required properties : - compatible : Must be "lsi,api2c" - reg : Offset and length of the register set for the device - interrupts : the interrupt specifier - #address-cells : Must be <1>; - #size-cells : Must be <0>; - clock-names : Must contain "i2c". - clocks: Must contain an entry for each name in cl...
Documentation/devicetree/bindings/i2c/i2c-axxia.txt
null
null
null
null
null
source
linux
Device tree bindings for i2c-cbus-gpio driver Required properties: - compatible = "i2c-cbus-gpio"; - gpios: clk, dat, sel - #address-cells = <1>; - #size-cells = <0>; Optional properties: - child nodes conforming to i2c bus binding Example: i2c@0 { compatible = "i2c-cbus-gpio"; gpios = <&gpio 66 0 /* clk */ ...
Documentation/devicetree/bindings/i2c/i2c-cbus-gpio.txt
null
null
null
null
null
source
linux
* Texas Instruments Davinci/Keystone I2C This file provides information, what the device node for the davinci/keystone i2c interface contains. Required properties: - compatible: "ti,davinci-i2c" or "ti,keystone-i2c"; - reg : Offset and length of the register set for the device - clocks: I2C functional clock phandle. ...
Documentation/devicetree/bindings/i2c/i2c-davinci.txt
null
null
null
null
null
source
linux
Conexant Digicolor I2C controller Required properties: - compatible: must be "cnxt,cx92755-i2c" - reg: physical address and length of the device registers - interrupts: a single interrupt specifier - clocks: clock for the device - #address-cells: should be <1> - #size-cells: should be <0> Optional properties: -...
Documentation/devicetree/bindings/i2c/i2c-digicolor.txt
null
null
null
null
null
source
linux
IMG Serial Control Bus (SCB) I2C Controller Required Properties: - compatible: "img,scb-i2c" - reg: Physical base address and length of controller registers - interrupts: Interrupt number used by the controller - clocks : Should contain a clock specifier for each entry in clock-names - clock-names : Should contain the...
Documentation/devicetree/bindings/i2c/i2c-img-scb.txt
null
null
null
null
null
source
linux
i2c Controller on XScale platforms such as IOP3xx and IXP4xx Required properties: - compatible : Must be one of "intel,iop3xx-i2c" "intel,ixp4xx-i2c"; - reg - #address-cells = <1>; - #size-cells = <0>; Optional properties: - Child nodes conforming to i2c bus binding Example: i2c@c8011000 { compatible = "intel,...
Documentation/devicetree/bindings/i2c/i2c-iop3xx.txt
null
null
null
null
null
source
linux
* Linear Technology / Analog Devices I2C bus switch Required Properties: - compatible: Must contain one of the following. "lltc,ltc4305", "lltc,ltc4306" - reg: The I2C address of the device. The following required properties are defined externally: - Standard I2C mux properties. See i2c-mux.yaml in this...
Documentation/devicetree/bindings/i2c/i2c-mux-ltc4306.txt
null
null
null
null
null
source
linux
Register-based I2C Bus Mux This binding describes an I2C bus multiplexer that uses a single register to route the I2C signals. Required properties: - compatible: i2c-mux-reg - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side port is connected to. * Standard I2C mux properties. See i2c-mux....
Documentation/devicetree/bindings/i2c/i2c-mux-reg.txt
null
null
null
null
null
source
linux
* Two Wire Serial Interface (TWSI) / I2C - compatible: "cavium,octeon-3860-twsi" Compatibility with all cn3XXX, cn5XXX and cn6XXX SOCs. or compatible: "cavium,octeon-7890-twsi" Compatibility with cn78XX SOCs. - reg: The base address of the TWSI/I2C bus controller register bank. - #address-cells: Must be ...
Documentation/devicetree/bindings/i2c/i2c-octeon.txt
null
null
null
null
null
source
linux
Device-tree bindings for I2C OPAL driver ---------------------------------------- Most of the device node and properties layout is specific to the firmware and used by the firmware itself for configuring the port. From the linux perspective, the properties of use are "ibm,port-name" and "ibm,opal-id". Required proper...
Documentation/devicetree/bindings/i2c/i2c-opal.txt
null
null
null
null
null
source
linux
* NXP PCA PCA9564/PCA9665 I2C controller The PCA9564/PCA9665 serves as an interface between most standard parallel-bus microcontrollers/microprocessors and the serial I2C-bus and allows the parallel bus system to communicate bi-directionally with the I2C-bus. Required properties : - reg : Offset and length of the r...
Documentation/devicetree/bindings/i2c/i2c-pca-platform.txt
null
null
null
null
null
source
linux
CE4100 I2C ---------- CE4100 has one PCI device which is described as the I2C-Controller. This PCI device has three PCI-bars, each bar contains a complete I2C controller. So we have a total of three independent I2C-Controllers which share only an interrupt line. The driver is probed via the PCI-ID and is gathering the...
Documentation/devicetree/bindings/i2c/i2c-pxa-pci-ce4100.txt
null
null
null
null
null
source
linux
For discussion. Unclear are: * is the definition of +/- values practical or counterintuitive? * are the definitions unambiguous and easy to follow? * are the examples correct? * should we have HOWTO engineer a correct matrix for a new device (without comparing to a different one)? ==== Mounting matrix The mounting ...
Documentation/devicetree/bindings/iio/mount-matrix.txt
null
null
null
null
null
source
linux
LIS302 accelerometer devicetree bindings This device is matched via its bus drivers, and has a number of properties that apply in on the generic device (independent from the bus). Required properties for the SPI bindings: - compatible: should be set to "st,lis3lv02d-spi" - reg: the chipselect index - spi-max-...
Documentation/devicetree/bindings/iio/accel/lis302.txt
null
null
null
null
null
source
linux
Xilinx XADC device driver This binding document describes the bindings for the Xilinx 7 Series XADC as well as the UltraScale/UltraScale+ System Monitor. The Xilinx XADC is an ADC that can be found in the Series 7 FPGAs from Xilinx. The XADC has a DRP interface for communication. Currently two different frontends for...
Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
null
null
null
null
null
source
linux
Hisilicon RoCE DT description Hisilicon RoCE engine is a part of network subsystem. It works depending on other part of network subsystem, such as gmac and dsa fabric. Additional properties are described here: Required properties: - compatible: Should contain "hisilicon,hns-roce-v1". - reg: Physical base address of ...
Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt
null
null
null
null
null
source
linux
* Broadcom Keypad Controller device tree bindings Broadcom Keypad controller is used to interface a SoC with a matrix-type keypad device. The keypad controller supports multiple row and column lines. A key can be placed at each intersection of a unique row and a unique column. The keypad controller can sense a key-pre...
Documentation/devicetree/bindings/input/brcm,bcm-keypad.txt
null
null
null
null
null
source
linux
* Cirrus Logic CLPS711X matrix keypad device tree bindings Required Properties: - compatible: Shall contain "cirrus,ep7209-keypad". - row-gpios: List of GPIOs used as row lines. - poll-interval: Poll interval time in milliseconds. - linux,keymap: The definition can be found at bindings/input/m...
Documentation/devicetree/bindings/input/clps711x-keypad.txt
null
null
null
null
null
source
linux
Motorola CPCAP on key This module is part of the CPCAP. For more details about the whole chip see Documentation/devicetree/bindings/mfd/motorola-cpcap.txt. This module provides a simple power button event via an Interrupt. Required properties: - compatible: should be one of the following - "motorola,cpcap-pwrbutt...
Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
null
null
null
null
null
source
linux
* D-Link DIR-685 Touchkeys This is a I2C one-off touchkey controller based on the Cypress Semiconductor CY8C214 MCU with some firmware in its internal 8KB flash. The circuit board inside the router is named E119921. The touchkey device node should be placed inside an I2C bus node. Required properties: - compatible: ...
Documentation/devicetree/bindings/input/dlink,dir685-touchkeys.txt
null
null
null
null
null
source
linux
National Instruments Ettus Research USRP E3x0 button driver This module is part of the NI Ettus Research USRP E3x0 SDR. This module provides a simple power button event via two interrupts. Required properties: - compatible: should be one of the following - "ettus,e3x0-button": For devices such as the NI Ettus Rese...
Documentation/devicetree/bindings/input/e3x0-button.txt
null
null
null
null
null
source
linux
* GPIO Decoder DT bindings Required Properties: - compatible: should be "gpio-decoder" - gpios: a spec of gpios (at least two) to be decoded to a number with first entry representing the MSB. Optional Properties: - decoder-max-value: Maximum possible value that can be reported by the gpios. - linux,axis: the inpu...
Documentation/devicetree/bindings/input/gpio-decoder.txt
null
null
null
null
null
source
linux
Input: sysrq reset sequence A simple binding to represent a set of keys as described in include/uapi/linux/input.h. This is to communicate a sequence of keys to the sysrq driver. Upon holding the keys for a specified amount of time (if specified) the system is sync'ed and reset. Key sequences are global to the system...
Documentation/devicetree/bindings/input/input-reset.txt
null
null
null
null
null
source
linux
Microchip AT42QT1050 Five-channel Touch Sensor IC The AT42QT1050 (QT1050) is a QTouchADC sensor device. The device can sense from one to five keys, dependent on mode. The QT1050 includes all signal processing functions necessary to provide stable sensing under a wide variety of changing conditions, and the outputs are...
Documentation/devicetree/bindings/input/microchip,qt1050.txt
null
null
null
null
null
source
linux
* Tegra keyboard controller The key controller has maximum 24 pins to make matrix keypad. Any pin can be configured as row or column. The maximum column pin can be 8 and maximum row pins can be 16 for Tegra20/Tegra30. Required properties: - compatible: "nvidia,tegra20-kbc" - reg: Register base address of KBC. - interr...
Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt
null
null
null
null
null
source
linux
* TI's Keypad Controller device tree bindings TI's Keypad controller is used to interface a SoC with a matrix-type keypad device. The keypad controller supports multiple row and column lines. A key can be placed at each intersection of a unique row and a unique column. The keypad controller can sense a key-press and k...
Documentation/devicetree/bindings/input/omap-keypad.txt
null
null
null
null
null
source
linux
Aeroflex Gaisler APBPS2 PS/2 Core, supporting Keyboard or Mouse. The APBPS2 PS/2 core is available in the GRLIB VHDL IP core library. Note: In the ordinary environment for the APBPS2 core, a LEON SPARC system, these properties are built from information in the AMBA plug&play and from bootloader settings. Required pr...
Documentation/devicetree/bindings/input/ps2keyb-mouse-apbps2.txt
null
null
null
null
null
source
linux
* Marvell PXA Keypad controller Required Properties - compatible : should be "marvell,pxa27x-keypad" - reg : Address and length of the register set for the device - interrupts : The interrupt for the keypad controller - marvell,debounce-interval : How long time the key will be recognized when it is pressed. It is a ...
Documentation/devicetree/bindings/input/pxa27x-keypad.txt
null
null
null
null
null
source
linux
Raydium I2C touchscreen Required properties: - compatible: must be "raydium,rm32380" - reg: The I2C address of the device - interrupts: interrupt to which the chip is connected See ../interrupt-controller/interrupts.txt Optional properties: - avdd-supply: analog power supply needed to power device - vccio-supply: ...
Documentation/devicetree/bindings/input/raydium_i2c_ts.txt
null
null
null
null
null
source
linux
* SPEAr keyboard controller Required properties: - compatible: "st,spear300-kbd" Optional properties, in addition to those specified by the shared matrix-keyboard bindings: - autorepeat: bool: enables key autorepeat - st,mode: keyboard mode: 0 - 9x9, 1 - 6x6, 2 - 2x2 Example: kbd@fc400000 { compatible = "st,spear3...
Documentation/devicetree/bindings/input/spear-keyboard.txt
null
null
null
null
null
source
linux
* ST Keyscan controller Device Tree bindings The ST keyscan controller Device Tree binding is based on the matrix-keymap. Required properties: - compatible: "st,sti-keyscan" - reg: Register base address and size of st-keyscan controller. - interrupts: Interrupt number for the st-keyscan controller. - clocks: Must ...
Documentation/devicetree/bindings/input/st-keyscan.txt
null
null
null
null
null
source
linux
Texas Instruments Palmas family power button module This module is part of the Palmas family of PMICs. For more details about the whole chip see: Documentation/devicetree/bindings/mfd/palmas.txt. This module provides a simple power button event via an Interrupt. Required properties: - compatible: should be one of th...
Documentation/devicetree/bindings/input/ti,palmas-pwrbutton.txt
null
null
null
null
null
source
linux
Texas Instruments TPS65217 and TPS65218 power button This module is part of the TPS65217/TPS65218. For more details about the whole TPS65217 chip see Documentation/devicetree/bindings/regulator/tps65217.txt. This driver provides a simple power button event via an Interrupt. Required properties: - compatible: should ...
Documentation/devicetree/bindings/input/tps65218-pwrbutton.txt
null
null
null
null
null
source
linux
* AUO in-cell touchscreen controller using Pixcir sensors Required properties: - compatible: must be "auo,auo_pixcir_ts" - reg: I2C address of the chip - interrupts: interrupt to which the chip is connected - gpios: gpios the chip is connected to first one is the interrupt gpio and second one the reset gpio - x-size...
Documentation/devicetree/bindings/input/touchscreen/auo_pixcir_ts.txt
null
null
null
null
null
source
linux
* Broadcom's IPROC Touchscreen Controller Required properties: - compatible: must be "brcm,iproc-touchscreen" - ts_syscon: handler of syscon node defining physical base address of the controller and length of memory mapped region. If this property is selected please make sure MFD_SYSCON config is enabled in the ...
Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt
null
null
null
null
null