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
TI SOC based PWM Subsystem Required properties: - compatible: Must be "ti,<soc>-pwmss". for am33xx - compatible = "ti,am33xx-pwmss"; for am4372 - compatible = "ti,am4372-pwmss","ti,am33xx-pwmss"; for dra746 - compatible = "ti,dra746-pwmss", "ti,am33xx-pwmss" - reg: physical base address and size of the regist...
Documentation/devicetree/bindings/pwm/pwm-tipwmss.txt
null
null
null
null
null
source
linux
Specifying PWM information for devices ====================================== 1) PWM user nodes ----------------- PWM users should specify a list of PWM devices that they want to use with a property containing a 'pwm-list': pwm-list ::= <single-pwm> [pwm-list] single-pwm ::= <pwm-phandle> <pwm-specifier> pwm-phan...
Documentation/devicetree/bindings/pwm/pwm.txt
null
null
null
null
null
source
linux
== ST SPEAr SoC PWM controller == Required properties: - compatible: should be one of: - "st,spear320-pwm" - "st,spear1340-pwm" - reg: physical base address and length of the controller's registers - #pwm-cells: should be 2. See pwm.yaml in this directory for a description of the cells format. Example: ...
Documentation/devicetree/bindings/pwm/spear-pwm.txt
null
null
null
null
null
source
linux
== ST STMPE PWM controller == This is a PWM block embedded in the ST Microelectronics STMPE (ST Multi-Purpose Expander) chips. The PWM is registered as a subdevices of the STMPE MFD device. Required properties: - compatible: should be: - "st,stmpe-pwm" - #pwm-cells: should be 2. See pwm.yaml in this directory for a...
Documentation/devicetree/bindings/pwm/st,stmpe-pwm.txt
null
null
null
null
null
source
linux
Devicetree binding for regmap Optional properties: little-endian, big-endian, native-endian: See common-properties.txt for a definition Note: Regmap defaults to little-endian register access on MMIO based devices, this is by far the most common setting. On CPU architectures that typically run big-endian ope...
Documentation/devicetree/bindings/regmap/regmap.txt
null
null
null
null
null
source
linux
Marvell 88PG867/88PG868 voltage regulators Required properties: - compatible: one of "marvell,88pg867", "marvell,88pg868"; - reg: I2C slave address. Optional subnodes for regulators: "buck1", "buck2", using common regulator bindings given in <Documentation/devicetree/bindings/regulator/regulator.txt>. Example: pg8...
Documentation/devicetree/bindings/regulator/88pg86x.txt
null
null
null
null
null
source
linux
Marvell 88PM800 regulator Required properties: - compatible: "marvell,88pm800" - reg: I2C slave address - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using the node's name (or the deprecated regulator-compatible property if present), with valid values...
Documentation/devicetree/bindings/regulator/88pm800.txt
null
null
null
null
null
source
linux
Marvell 88PM860x regulator Required properties: - compatible: "marvell,88pm860x" - reg: I2C slave address - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using the regulator-compatible property, with valid values listed below. Example: pmic: 88pm860x...
Documentation/devicetree/bindings/regulator/88pm860x.txt
null
null
null
null
null
source
linux
Regulator of AMS AS3722 PMIC. Name of the regulator subnode must be "regulators". Optional properties: -------------------- The input supply of regulators are the optional properties on the regulator node. The AS3722 is having 7 DCDC step-down regulators as sd[0-6], 10 LDOs as ldo[0-7], ldo[9-11]. The input supply of ...
Documentation/devicetree/bindings/regulator/as3722-regulator.txt
null
null
null
null
null
source
linux
Motorola CPCAP PMIC voltage regulators ------------------------------------ Requires node properties: - "compatible" value one of: "motorola,cpcap-regulator" "motorola,mapphone-cpcap-regulator" "motorola,xoom-cpcap-regulator" Required regulator properties: - "regulator-name" - "regulator-enable-ramp-delay...
Documentation/devicetree/bindings/regulator/cpcap-regulator.txt
null
null
null
null
null
source
linux
Hisilicon Hi655x Voltage regulators Note: The Hi655x regulator control is managed by Hi655x PMIC. So the node of this regulator must be child node of Hi655x PMIC node. The driver uses the regulator core framework, so please also take the bindings of regulator.txt for reference. The valid names for regulators are: L...
Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt
null
null
null
null
null
source
linux
Intersil ISL9305/ISL9305H voltage regulator Required properties: - compatible: "isil,isl9305" or "isil,isl9305h" - reg: I2C slave address, usually 0x68. - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using the node's name, with valid values being "dcd...
Documentation/devicetree/bindings/regulator/isl9305.txt
null
null
null
null
null
source
linux
TI LMU LM363x regulator device tree bindings LM363x regulator driver supports LM3631 and LM3632. LM3631 has five regulators and LM3632 supports three regulators. Required property: - compatible: "ti,lm363x-regulator" Optional properties: LM3632 has external enable pins for two LDOs. - enable-gpios: Two GPIO sp...
Documentation/devicetree/bindings/regulator/lm363x-regulator.txt
null
null
null
null
null
source
linux
Binding for TI/National Semiconductor LP872x Driver Required properties: - compatible: "ti,lp8720" or "ti,lp8725" - reg: I2C slave address. 0x7d = LP8720, 0x7a = LP8725 Optional properties: - ti,general-config: the value of LP872X_GENERAL_CFG register (u8) (LP8720) bit[2]: BUCK output voltage control by...
Documentation/devicetree/bindings/regulator/lp872x.txt
null
null
null
null
null
source
linux
Linear Technology LTC3589, LTC3589-1, and LTC3589-2 8-output regulators Required properties: - compatible: "lltc,ltc3589", "lltc,ltc3589-1" or "lltc,ltc3589-2" - reg: I2C slave address Required child node: - regulators: Contains eight regulator child nodes sw1, sw2, sw3, bb-out, ldo1, ldo2, ldo3, and ldo4, specifyi...
Documentation/devicetree/bindings/regulator/ltc3589.txt
null
null
null
null
null
source
linux
Maxim MAX1586 voltage regulator Required properties: - compatible: must be "maxim,max1586" - reg: I2C slave address, usually 0x14 - v3-gain: integer specifying the V3 gain as per datasheet (1 + R24/R25 + R24/185.5kOhm) - any required generic properties defined in regulator.txt Example: i2c_master { max...
Documentation/devicetree/bindings/regulator/max1586-regulator.txt
null
null
null
null
null
source
linux
MAX8907 regulator Required properties: - compatible: "maxim,max8907" - reg: I2C slave address - interrupts: The interrupt output of the controller - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC. - in-v1-supply: The input supply for SD1. - in-v2-supply: The input supply for SD2. - in-v3-supply: The input ...
Documentation/devicetree/bindings/regulator/max8907.txt
null
null
null
null
null
source
linux
Max8925 Voltage regulators Required nodes: -nodes: - SDV1 for SDV SDV1 - SDV2 for SDV SDV2 - SDV3 for SDV SDV3 - LDO1 for LDO LDO1 - LDO2 for LDO LDO2 - LDO3 for LDO LDO3 - LDO4 for LDO LDO4 - LDO5 for LDO LDO5 - LDO6 for LDO LDO6 - LDO7 for LDO LDO7 - LDO8 for LDO LDO8 - LDO9 for LDO LDO9 - ...
Documentation/devicetree/bindings/regulator/max8925-regulator.txt
null
null
null
null
null
source
linux
Monolithic Power Systems MP8859 voltage regulator Required properties: - compatible: "mps,mp8859"; - reg: I2C slave address. Optional subnode for regulator: "mp8859_dcdc", using common regulator bindings given in <Documentation/devicetree/bindings/regulator/regulator.txt>. Example: mp8859: regulator@66 { compati...
Documentation/devicetree/bindings/regulator/mp8859.txt
null
null
null
null
null
source
linux
Mediatek MT6311 Regulator Required properties: - compatible: "mediatek,mt6311-regulator" - reg: I2C slave address, usually 0x6b. - regulators: List of regulators provided by this controller. It is named to VDVFS and VBIASN. The definition for each of these nodes is defined using the standard binding for regulato...
Documentation/devicetree/bindings/regulator/mt6311-regulator.txt
null
null
null
null
null
source
linux
Mediatek MT6323 Regulator All voltage regulators are defined as subnodes of the regulators node. A list of regulators provided by this controller are defined as subnodes of the PMIC's node. Each regulator is named according to its regulator type, buck_<name> and ldo_<name>. The definition for each of these nodes is de...
Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
null
null
null
null
null
source
linux
MediaTek MT6380 Regulator All voltage regulators provided by the MT6380 PMIC are described as the subnodes of the MT6380 regulators node. Each regulator is named according to its regulator type, buck-<name> and ldo-<name>. The definition for each of these nodes is defined using the standard binding for regulators at D...
Documentation/devicetree/bindings/regulator/mt6380-regulator.txt
null
null
null
null
null
source
linux
NVIDIA Tegra Regulators Coupling ================================ NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators. Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30 there are 2. Tegra20 voltage coupling ------------------------ On Tegra20 SoC's there are 3 coupled regulator...
Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt
null
null
null
null
null
source
linux
* palmas regulator IP block devicetree bindings The tps659038 for the AM57x class have OTP spins that have different part numbers but the same functionality. There is not a need to add the OTP spins to the palmas driver. The spin devices should use the tps659038 as it's compatible value. This is the list of those devi...
Documentation/devicetree/bindings/regulator/palmas-pmic.txt
null
null
null
null
null
source
linux
PBIAS internal regulator for SD card dual voltage i/o pads on OMAP SoCs. Required properties: - compatible: - should be "ti,pbias-dra7" for DRA7 - should be "ti,pbias-omap2" for OMAP2 - should be "ti,pbias-omap3" for OMAP3 - should be "ti,pbias-omap4" for OMAP4 - should be "ti,pbias-omap5" for OMAP5 - "ti,...
Documentation/devicetree/bindings/regulator/pbias-regulator.txt
null
null
null
null
null
source
linux
* Powerventure Semiconductor PV88060 Voltage Regulator Required properties: - compatible: "pvs,pv88060". - reg: I2C slave address, usually 0x49. - interrupts: the interrupt outputs of the controller - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using th...
Documentation/devicetree/bindings/regulator/pv88060.txt
null
null
null
null
null
source
linux
* Powerventure Semiconductor PV88080 Voltage Regulator Required properties: - compatible: Must be one of the following, depending on the silicon version: - "pvs,pv88080" (DEPRECATED) - "pvs,pv88080-aa" for PV88080 AA or AB silicon - "pvs,pv88080-ba" for PV88080 BA or BB silicon NOTE: The use of the compatibles...
Documentation/devicetree/bindings/regulator/pv88080.txt
null
null
null
null
null
source
linux
* Powerventure Semiconductor PV88090 Voltage Regulator Required properties: - compatible: "pvs,pv88090". - reg: I2C slave address, usually 0x48. - interrupts: the interrupt outputs of the controller - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using th...
Documentation/devicetree/bindings/regulator/pv88090.txt
null
null
null
null
null
source
linux
Regulator DT binding for MAX77620 Power management IC from Maxim Semiconductor. Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply of these regulators are defined under parent device node. Details of regulator properties are defined as child node under sub-node "regulators" which is child node of de...
Documentation/devicetree/bindings/regulator/regulator-max77620.txt
null
null
null
null
null
source
linux
SKY81452 voltage regulator Required properties: - regulator node named lout. - any required generic properties defined in regulator.txt Optional properties: - any available generic properties defined in regulator.txt Example: regulator { lout { regulator-name = "sky81452-lout"; regulator-min-microvolt = <4...
Documentation/devicetree/bindings/regulator/sky81452-regulator.txt
null
null
null
null
null
source
linux
Adaptive Body Bias(ABB) SoC internal LDO regulator for Texas Instruments SoCs Required Properties: - compatible: Should be one of: - "ti,abb-v1" for older SoCs like OMAP3 - "ti,abb-v2" for newer SoCs like OMAP4, OMAP5 - "ti,abb-v3" for a generic definition where setup and control registers are provided (exa...
Documentation/devicetree/bindings/regulator/ti-abb-regulator.txt
null
null
null
null
null
source
linux
TPS51632 Voltage regulators Required properties: - compatible: Must be "ti,tps51632" - reg: I2C slave address Optional properties: - ti,enable-pwm-dvfs: Enable the DVFS voltage control through the PWM interface. - ti,dvfs-step-20mV: The 20mV step voltage when PWM DVFS enabled. Missing this will set 10mV step voltage...
Documentation/devicetree/bindings/regulator/tps51632-regulator.txt
null
null
null
null
null
source
linux
TPS65023 family of regulators Required properties: - compatible: Must be one of the following. "ti,tps65020", "ti,tps65021", "ti,tps65023", - reg: I2C slave address - regulators: list of regulators provided by this controller, must be named after their hardware counterparts: VDCDC[1-3] and LDO[1-2] - regulators: ...
Documentation/devicetree/bindings/regulator/tps65023.txt
null
null
null
null
null
source
linux
TPS65090 regulators Required properties: - compatible: "ti,tps65090" - reg: I2C slave address - interrupts: the interrupt outputs of the controller - regulators: A node that houses a sub-node for each regulator within the device. Each sub-node is identified using the node's name, with valid values listed below. Th...
Documentation/devicetree/bindings/regulator/tps65090.txt
null
null
null
null
null
source
linux
TPS65217 family of regulators Required properties: - compatible: "ti,tps65217" - reg: I2C slave address - regulators: list of regulators provided by this controller, must be named after their hardware counterparts: dcdc[1-3] and ldo[1-4] - regulators: This is the list of child nodes that specify the regulator init...
Documentation/devicetree/bindings/regulator/tps65217.txt
null
null
null
null
null
source
linux
TPS65218 family of regulators Required properties: - compatible: "ti,tps65218" - reg: I2C slave address - List of regulators provided by this controller, must be named after their hardware counterparts: dcdc[1-6] and ldo1 - This is the list of child nodes that specify the regulator initialization data for defined...
Documentation/devicetree/bindings/regulator/tps65218.txt
null
null
null
null
null
source
linux
TPS6586x family of regulators Required properties: - compatible: "ti,tps6586x" - reg: I2C slave address - interrupts: the interrupt outputs of the controller - #gpio-cells: number of cells to describe a GPIO - gpio-controller: mark the device as a GPIO controller - regulators: A node that houses a sub-node for each re...
Documentation/devicetree/bindings/regulator/tps6586x.txt
null
null
null
null
null
source
linux
Versatile Express voltage regulators ------------------------------------ Requires node properties: - "compatible" value: "arm,vexpress-volt" - "arm,vexpress-sysreg,func" when controlled via vexpress-sysreg (see Documentation/devicetree/bindings/arm/vexpress-config.yaml for more details) Required regulator proper...
Documentation/devicetree/bindings/regulator/vexpress.txt
null
null
null
null
null
source
linux
Qualcomm Hexagon Peripheral Image Loader This document defines the binding for a component that loads and boots firmware on the Qualcomm Hexagon core. - compatible: Usage: required Value type: <string> Definition: must be one of: "qcom,ipq8074-wcss-pil" "qcom,qcs404-wcss-pil" - reg: Usage: required ...
Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
null
null
null
null
null
source
linux
STMicroelectronics Co-Processor Bindings ---------------------------------------- This binding provides support for adjunct processors found on ST SoCs. Co-processors can be controlled from the bootloader or the primary OS. If the bootloader starts a co-processor, the primary OS must detect its state and act accordin...
Documentation/devicetree/bindings/remoteproc/st-rproc.txt
null
null
null
null
null
source
linux
TI Davinci DSP devices ======================= The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that is used to offload some of the processor-intensive tasks or algorithms, for achieving various system level goals. The processor cores in the sub-system usually contain additional sub-modules lik...
Documentation/devicetree/bindings/remoteproc/ti,davinci-rproc.txt
null
null
null
null
null
source
linux
TI Keystone DSP devices ======================= The TI Keystone 2 family of SoCs usually have one or more (upto 8) TI DSP Core sub-systems that are used to offload some of the processor-intensive tasks or algorithms, for achieving various system level goals. These processor sub-systems usually contain additional sub-...
Documentation/devicetree/bindings/remoteproc/ti,keystone-rproc.txt
null
null
null
null
null
source
linux
TI Wakeup M3 Remoteproc Driver ============================== The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor (commonly referred to as Wakeup M3 or CM3) to help with various low power tasks that cannot be controlled from the MPU. This CM3 processor requires a firmware binary to accomplish...
Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt
null
null
null
null
null
source
linux
* Xen hypervisor reserved-memory binding Expose one or more memory regions as reserved-memory to the guest virtual machine. Typically, a region is configured at VM creation time to be a shared memory area across multiple virtual machines for communication among them. For each of these pre-shared memory regions, a ran...
Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
null
null
null
null
null
source
linux
Broadcom BCM63138 Processor Monitor Bus binding =============================================== Please also refer to reset.txt in this directory for common reset controller binding usage. Require properties: - compatible: must be "brcm,bcm63138-pmb" - reg: base register address and size for this bus controller - #re...
Documentation/devicetree/bindings/reset/brcm,bcm63138-pmb.txt
null
null
null
null
null
source
linux
Pistachio Reset Controller ============================================================================= This binding describes a reset controller device that is used to enable and disable individual IP blocks within the Pistachio SoC using "soft reset" control bits found in the Pistachio SoC top level registers. The...
Documentation/devicetree/bindings/reset/img,pistachio-reset.txt
null
null
null
null
null
source
linux
= Reset Signal Device Tree Bindings = This binding is intended to represent the hardware reset signals present internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole standalone chips are most likely better represented as GPIOs, although there are likely to be exceptions to this rule. Hardware blocks ...
Documentation/devicetree/bindings/reset/reset.txt
null
null
null
null
null
source
linux
Binding for the Synopsys HSDK reset controller This binding uses the common reset binding[1]. [1] Documentation/devicetree/bindings/reset/reset.txt Required properties: - compatible: should be "snps,hsdk-reset". - reg: should always contain 2 pairs address - length: first for reset configuration register and secon...
Documentation/devicetree/bindings/reset/snps,hsdk-reset.txt
null
null
null
null
null
source
linux
STMicroelectronics STi family Sysconfig Peripheral SoftReset Controller ============================================================================= This binding describes a reset controller device that is used to enable and disable on-chip peripheral controllers such as USB and SATA, using "softreset" control bits f...
Documentation/devicetree/bindings/reset/st,sti-softreset.txt
null
null
null
null
null
source
linux
STMicroelectronics STM32 Peripheral Reset Controller ==================================================== The RCC IP is both a reset and a clock controller. Please see Documentation/devicetree/bindings/clock/st,stm32-rcc.yaml
Documentation/devicetree/bindings/reset/st,stm32-rcc.txt
null
null
null
null
null
source
linux
STMicroelectronics STM32MP1 Peripheral Reset Controller ======================================================= The RCC IP is both a reset and a clock controller. Please see Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt
null
null
null
null
null
source
linux
TI SysCon Reset Controller ======================= Almost all SoCs have hardware modules that require reset control in addition to clock and power control for their functionality. The reset control is typically provided by means of memory-mapped I/O registers. These registers are sometimes a part of a larger register ...
Documentation/devicetree/bindings/reset/ti-syscon-reset.txt
null
null
null
null
null
source
linux
Xilinx Zynq Reset Manager The Zynq AP-SoC has several different resets. See Chapter 26 of the Zynq TRM (UG585) for more information about Zynq resets. Required properties: - compatible: "xlnx,zynq-reset" - reg: SLCR offset and size taken via syscon <0x200 0x48> - syscon: <&slcr> This should be a phandle to the Zyn...
Documentation/devicetree/bindings/reset/zynq-reset.txt
null
null
null
null
null
source
linux
Cadence Real Time Clock The Cadence RTC controller with date, time and alarm capabilities. The alarm may wake the system from low-power state. Required properties: - compatible: Should be "cdns,rtc-r109v3" - reg: Specifies base physical address and size of the register area. - interrupts: A single interrupt specifier...
Documentation/devicetree/bindings/rtc/cdns,rtc.txt
null
null
null
null
null
source
linux
* Dallas DS1390 SPI Serial Real-Time Clock Required properties: - compatible: Should contain "dallas,ds1390". - reg: SPI address for chip Optional properties: - trickle-resistor-ohms : Selected resistor for trickle charger Values usable for ds1390 are 250, 2000, 4000 Should be given if trickle charger should be en...
Documentation/devicetree/bindings/rtc/dallas,ds1390.txt
null
null
null
null
null
source
linux
Epson RX6110 Real Time Clock ============================ The Epson RX6110 can be used with SPI or I2C busses. The kind of bus depends on the SPISEL pin and can not be configured via software. I2C mode -------- Required properties: - compatible: should be: "epson,rx6110" - reg : the I2C address of the device for...
Documentation/devicetree/bindings/rtc/epson,rx6110.txt
null
null
null
null
null
source
linux
ISL12026 I2C RTC/EEPROM ISL12026 is an I2C RTC/EEPROM combination device. The RTC and control registers respond at bus address 0x6f, and the EEPROM array responds at bus address 0x57. The canonical "reg" value will be for the RTC portion. Required properties supported by the device: - "compatible": must be "isil,...
Documentation/devicetree/bindings/rtc/isil,isl12026.txt
null
null
null
null
null
source
linux
* Maxim/Dallas Semiconductor DS-1302 RTC Simple device which could be used to store date/time between reboots. The device uses the standard MicroWire half-duplex transfer timing. Master output is set on low clock and sensed by the RTC on the rising edge. Master input is set by the RTC on the trailing edge and is sens...
Documentation/devicetree/bindings/rtc/maxim-ds1302.txt
null
null
null
null
null
source
linux
* Microchip PIC32 Real Time Clock and Calendar The RTCC keeps time in hours, minutes, and seconds, and one half second. It provides a calendar in weekday, date, month, and year. It also provides a configurable alarm. Required properties: - compatible: should be: "microchip,pic32mzda-rtc" - reg: physical base address ...
Documentation/devicetree/bindings/rtc/microchip,pic32-rtc.txt
null
null
null
null
null
source
linux
MOXA ART real-time clock Required properties: - compatible : Should be "moxa,moxart-rtc" - rtc-sclk-gpios : RTC sclk gpio, with zero flags - rtc-data-gpios : RTC data gpio, with zero flags - rtc-reset-gpios : RTC reset gpio, with zero flags Example: rtc: rtc { compatible = "moxa,moxart-rtc"; rtc-sclk-gpios = <...
Documentation/devicetree/bindings/rtc/moxa,moxart-rtc.txt
null
null
null
null
null
source
linux
Realtek RTD129x Real-Time Clock =============================== Required properties: - compatible : Should be "realtek,rtd1295-rtc" - reg : Specifies the physical base address and size - clocks : Specifies the clock gate Example: rtc@9801b600 { compatible = "realtek,rtd1295-clk"; reg = <0x9801b60...
Documentation/devicetree/bindings/rtc/realtek,rtd119x.txt
null
null
null
null
null
source
linux
Motorola mc146818 compatible RTC ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Required properties: - compatible : "motorola,mc146818" - reg : should contain registers location and length. Optional properties: - interrupts : should contain interrupt. - ctrl-reg : Contains the initial value of the control register also ...
Documentation/devicetree/bindings/rtc/rtc-cmos.txt
null
null
null
null
null
source
linux
TI Real Time Clock Required properties: - compatible: - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family. - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family. This RTC IP has special WAKE-EN Register to enable Wakeup generation for event Alarm. It can also be ...
Documentation/devicetree/bindings/rtc/rtc-omap.txt
null
null
null
null
null
source
linux
IBM OPAL real-time clock ------------------------ Required properties: - compatible: Should be "ibm,opal-rtc" Optional properties: - wakeup-source: Decides if the wakeup is supported or not (Legacy property supported: "has-tpo") Example: rtc { compatible = "ibm,opal-rtc"; wakeup-source; phandle = <0x100000...
Documentation/devicetree/bindings/rtc/rtc-opal.txt
null
null
null
null
null
source
linux
Palmas RTC controller bindings Required properties: - compatible: - "ti,palmas-rtc" for palma series of the RTC controller - interrupts: Interrupt number of RTC submodule on device. Optional properties: - ti,backup-battery-chargeable: The Palmas series device like TPS65913 or TPS80036 supports the backup battery ...
Documentation/devicetree/bindings/rtc/rtc-palmas.txt
null
null
null
null
null
source
linux
STMicroelectronics Low Power Controller (LPC) - RTC =================================================== LPC currently supports Watchdog OR Real Time Clock OR Clocksource functionality. [See: ../watchdog/st_lpc_wdt.txt for Watchdog options] [See: ../timer/st,stih407-lpc for Clocksource options] Required properties -...
Documentation/devicetree/bindings/rtc/rtc-st-lpc.txt
null
null
null
null
null
source
linux
* HiSilicon SAS controller The HiSilicon SAS controller supports SAS/SATA. Main node required properties: - compatible : value should be as follows: (a) "hisilicon,hip05-sas-v1" for v1 hw in hip05 chipset (b) "hisilicon,hip06-sas-v2" for v2 hw in hip06 chipset (c) "hisilicon,hip07-sas-v2" for v2 hw in hip07 chip...
Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
null
null
null
null
null
source
linux
Altera UP PS/2 controller Required properties: - compatible : should be "ALTR,ps2-1.0". <DEPRECATED> - compatible : should be "altr,ps2-1.0".
Documentation/devicetree/bindings/serio/altera_ps2.txt
null
null
null
null
null
source
linux
OLPC AP-SP serio interface Required properties: - compatible : "olpc,ap-sp" - reg : base address and length of SoC's WTM registers - interrupts : SP-AP interrupt Example: ap-sp@d4290000 { compatible = "olpc,ap-sp"; reg = <0xd4290000 0x1000>; interrupts = <40>; }
Documentation/devicetree/bindings/serio/olpc,ap-sp.txt
null
null
null
null
null
source
linux
* ARC PS/2 driver: PS/2 block used in some ARC FPGA's & nSIM OSCI model Required properties: - compatible : "snps,arc_ps2" - reg : offset and length (always 0x14) of registers - interrupts : interrupt - interrupt-names : name of interrupt, must be "arc_ps2_irq" Example: serio@c9000400 { compatible = "snps,arc_p...
Documentation/devicetree/bindings/serio/snps-arc_ps2.txt
null
null
null
null
null
source
linux
DT compatible string versioning for SiFive open-source IP blocks This document describes the version specification for DT "compatible" strings for open-source SiFive IP blocks. HDL for these IP blocks can be found in this public repository: https://github.com/sifive/sifive-blocks IP block-specific DT compatible str...
Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt
null
null
null
null
null
source
linux
Device Tree bindings for Marvell PMU Required properties: - compatible: value should be "marvell,dove-pmu". May also include "simple-bus" if there are child devices, in which case the ranges node is required. - reg: two base addresses and sizes of the PM controller and PMU. - interrupts: single interrupt nu...
Documentation/devicetree/bindings/soc/dove/pmu.txt
null
null
null
null
null
source
linux
* Global Utilities Block The global utilities block controls power management, I/O device enabling, power-on-reset configuration monitoring, general-purpose I/O signal configuration, alternate function selection for multiplexed signals, and clock control. Required properties: - compatible : Should define the compat...
Documentation/devicetree/bindings/soc/fsl/guts.txt
null
null
null
null
null
source
linux
* Freescale Communications Processor Module NOTE: This is an interim binding, and will likely change slightly, as more devices are supported. The QE bindings especially are incomplete. * Root CPM node Properties: - compatible : "fsl,cpm1", "fsl,cpm2", or "fsl,qe". - reg : A 48-byte region beginning with CPCR. Exam...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm.txt
null
null
null
null
null
source
linux
Every GPIO controller node must have #gpio-cells property defined, this information will be used to translate gpio-specifiers. On CPM1 devices, all ports are using slightly different register layouts. Ports A, C and D are 16bit ports and Ports B and E are 32bit ports. On CPM2 devices, all ports are 32bit ports and us...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/gpio.txt
null
null
null
null
null
source
linux
* Serial Currently defined compatibles: - fsl,cpm1-smc-uart - fsl,cpm2-smc-uart - fsl,cpm1-scc-uart - fsl,cpm2-scc-uart - fsl,qe-uart Modem control lines connected to GPIO controllers are listed in the gpios property as described in booting-without-of.txt, section IX.1 in the following order: CTS, RTS, DCD, DSR, DTR...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/serial.txt
null
null
null
null
null
source
linux
* Serial Required Properties: compatible : must be "fsl,<chip>-ucc-uart". For t1040, must be "fsl,t1040-ucc-uart". port-number : port number of UCC-UART tx/rx-clock-name : should be "brg1"-"brg16" for internal clock source, should be "clk1"-"clk28" for external clock source. Example: ucc_serial: ucc@2200 { c...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/uqe_serial.txt
null
null
null
null
null
source
linux
* Baud Rate Generators Currently defined compatibles: fsl,cpm-brg fsl,cpm1-brg fsl,cpm2-brg Properties: - reg : There may be an arbitrary number of reg resources; BRG numbers are assigned to these in order. - clock-frequency : Specifies the base frequency driving the BRG. Example: brg@119f0 { compatible = "fs...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/brg.txt
null
null
null
null
null
source
linux
* I2C The I2C controller is expressed as a bus under the CPM node. Properties: - compatible : "fsl,cpm1-i2c", "fsl,cpm2-i2c" - reg : On CPM2 devices, the second resource doesn't specify the I2C Parameter RAM itself, but the I2C_BASE field of the CPM2 Parameter RAM (typically 0x8afc 0x2). - #address-cells : Should...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/i2c.txt
null
null
null
null
null
source
linux
* Interrupt Controllers Currently defined compatibles: - fsl,cpm1-pic - only one interrupt cell - fsl,pq1-pic - fsl,cpm2-pic - second interrupt cell is level/sense: - 2 is falling edge - 8 is active low Example: interrupt-controller@10c00 { #interrupt-cells = <2>; interrupt-controller; reg = <10c00...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/pic.txt
null
null
null
null
null
source
linux
* USB (Universal Serial Bus Controller) Properties: - compatible : "fsl,cpm1-usb", "fsl,cpm2-usb", "fsl,qe-usb" Example: usb@11bc0 { #address-cells = <1>; #size-cells = <0>; compatible = "fsl,cpm2-usb"; reg = <11b60 18 8b00 100>; interrupts = <b 8>; interrupt-parent = <&PIC>; fsl,cpm-command = <2e60000...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/usb.txt
null
null
null
null
null
source
linux
* Uploaded QE firmware If a new firmware has been uploaded to the QE (usually by the boot loader), then a 'firmware' child node should be added to the QE node. This node provides information on the uploaded firmware that device drivers may need. Required properties: - id: The stri...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/firmware.txt
null
null
null
null
null
source
linux
* Parallel I/O Ports This node configures Parallel I/O ports for CPUs with QE support. The node should reside in the "soc" node of the tree. For each device that using parallel I/O ports, a child node should be created. See the definition of the Pin configuration nodes below for more information. Required properties...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/par_io.txt
null
null
null
null
null
source
linux
* Pin configuration nodes Required properties: - pio-map : array of pin configurations. Each pin is defined by 6 integers. The six numbers are respectively: port, pin, dir, open_drain, assignment, has_irq. - port : port number of the pin; 0-6 represent port A-G in UM. - pin : pin number in the port. - dir ...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/pincfg.txt
null
null
null
null
null
source
linux
* UCC (Unified Communications Controllers) Required properties: - device_type : should be "network", "hldc", "uart", "transparent" "bisync", "atm", or "serial". - compatible : could be "ucc_geth" or "fsl_atm" and so on. - cell-index : the ucc number(1-8), corresponding to UCCx in UM. - reg : Offset and length of the...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ucc.txt
null
null
null
null
null
source
linux
Freescale QUICC Engine USB Controller Required properties: - compatible : should be "fsl,<chip>-qe-usb", "fsl,mpc8323-qe-usb". - reg : the first two cells should contain usb registers location and length, the next two two cells should contain PRAM location and length. - interrupts : should contain USB interrupt. -...
Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/usb.txt
null
null
null
null
null
source
linux
MediaTek SCPSYS =============== The System Control Processor System (SCPSYS) has several power management related tasks in the system. The tasks include thermal measurement, dynamic voltage frequency scaling (DVFS), interrupt filter and lowlevel sleep control. The System Power Manager (SPM) inside the SCPSYS is for th...
Documentation/devicetree/bindings/soc/mediatek/scpsys.txt
null
null
null
null
null
source
linux
Keystone Navigator DMA Controller This document explains the device tree bindings for the packet dma on keystone devices. The Keystone Navigator DMA driver sets up the dma channels and flows for the QMSS(Queue Manager SubSystem) who triggers the actual data movements across clients using destination queues. Every clie...
Documentation/devicetree/bindings/soc/ti/keystone-navigator-dma.txt
null
null
null
null
null
source
linux
* Texas Instruments Keystone Navigator Queue Management SubSystem driver The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of the main hardware sub system which forms the backbone of the Keystone multi-core Navigator. QMSS consist of queue managers, packed-data structure processors(PDSP), linking RAM, ...
Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
null
null
null
null
null
source
linux
Generic AC97 Device Properties This documents describes the devicetree bindings for an ac97 controller child node describing ac97 codecs. Required properties: -compatible : Must be "ac97,vendor_id1,vendor_id2 The ids shall be the 4 characters hexadecimal encoding, such as given by "%04x" formatting of p...
Documentation/devicetree/bindings/sound/ac97-bus.txt
null
null
null
null
null
source
linux
Analog Devices ADAU1701 Required properties: - compatible: Should contain "adi,adau1701" - reg: The i2c address. Value depends on the state of ADDR0 and ADDR1, as wired in hardware. Optional properties: - reset-gpio: A GPIO spec to define which pin is connected to the chip's !RESET pin. If specified, ...
Documentation/devicetree/bindings/sound/adi,adau1701.txt
null
null
null
null
null
source
linux
ADI AXI-I2S controller The core can be generated with transmit (playback), only receive (capture) or both directions enabled. Required properties: - compatible : Must be "adi,axi-i2s-1.00.a" - reg : Must contain I2S core's registers location and length - clocks : Pairs of phandle and specifier referencing the cont...
Documentation/devicetree/bindings/sound/adi,axi-i2s.txt
null
null
null
null
null
source
linux
ADI AXI-SPDIF controller Required properties: - compatible : Must be "adi,axi-spdif-tx-1.00.a" - reg : Must contain SPDIF core's registers location and length - clocks : Pairs of phandle and specifier referencing the controller's clocks. The controller expects two clocks, the clock used for the AXI interface and...
Documentation/devicetree/bindings/sound/adi,axi-spdif-tx.txt
null
null
null
null
null
source
linux
Analog Devices SSM2305 Speaker Amplifier ======================================== Required properties: - compatible : "adi,ssm2305" - shutdown-gpios : The gpio connected to the shutdown pin. The gpio signal is ACTIVE_LOW. Example: ssm2305: analog-amplifier { compatible = "adi,ssm2305"; shu...
Documentation/devicetree/bindings/sound/adi,ssm2305.txt
null
null
null
null
null
source
linux
AK4118 S/PDIF transceiver This device supports I2C mode. Required properties: - compatible : "asahi-kasei,ak4118" - reg : The I2C address of the device for I2C - reset-gpios: A GPIO specifier for the reset pin - irq-gpios: A GPIO specifier for the IRQ pin Example: &i2c { ak4118: ak4118@13 { #sound-dai-cells = <...
Documentation/devicetree/bindings/sound/ak4118.txt
null
null
null
null
null
source
linux
AK5386 Single-ended 24-Bit 192kHz delta-sigma ADC This device has no control interface. Required properties: - compatible : "asahi-kasei,ak5386" Optional properties: - reset-gpio : a GPIO spec for the reset/power down pin. If specified, it will be deasserted at probe time. - va-supply : a regulator spec, ...
Documentation/devicetree/bindings/sound/ak5386.txt
null
null
null
null
null
source
linux
Device Tree bindings for the Armada 370 DB audio ================================================ These Device Tree bindings are used to describe the audio complex found on the Armada 370 DB platform. Mandatory properties: * compatible: must be "marvell,a370db-audio" * marvell,audio-controller: a phandle that poi...
Documentation/devicetree/bindings/sound/armada-370db-audio.txt
null
null
null
null
null
source
linux
* Atmel AC97 controller Required properties: - compatible: "atmel,at91sam9263-ac97c" - reg: Address and length of the register set for the device - interrupts: Should contain AC97 interrupt - ac97-gpios: Please refer to soc-ac97link.txt, only ac97-reset is used Optional properties: - pinctrl-names, pinctrl-0...
Documentation/devicetree/bindings/sound/atmel_ac97c.txt
null
null
null
null
null
source
linux
Devicetree bindings for the Axentia TSE-850 audio complex Required properties: - compatible: "axentia,tse850-pcm5142" - axentia,cpu-dai: The phandle of the cpu dai. - axentia,audio-codec: The phandle of the PCM5142 codec. - axentia,add-gpios: gpio specifier that controls the mixer. - axentia,loop1-gpios: gpi...
Documentation/devicetree/bindings/sound/axentia,tse850-pcm5142.txt
null
null
null
null
null
source
linux
Broadcom DSL/PON BCM63xx Audio I2S controller Required properties: - compatible: Should be "brcm,bcm63xx-i2s". - #address-cells: 32bit valued, 1 cell. - #size-cells: 32bit valued, 0 cell. - reg: Should contain audio registers location and length - interrupts: Should contain the interrupt for the ...
Documentation/devicetree/bindings/sound/brcm,bcm63xx-audio.txt
null
null
null
null
null