Home
last modified time | relevance | path

Searched refs:DTS (Results 1 – 25 of 144) sorted by relevance

123456

/linux/Documentation/devicetree/bindings/
H A Ddts-coding-style.rst4 Devicetree Sources (DTS) Coding Style
7 When writing Devicetree Sources (DTS) please observe below guidelines. They
60 3. When extending nodes in the board DTS via &label, the entries shall be
66 in navigating through the DTS source.
92 /* Board DTS - alphabetical order */
102 /* Board DTS - alternative order, keep as DTSI */
163 /* Board DTS */
197 Organizing DTSI and DTS
200 The DTSI and DTS files shall be organized in a way representing the common,
201 reusable parts of hardware. Typically, this means organizing DTSI and DTS files
[all …]
H A Dsubmitting-patches.rst57 6) Any compatible strings used in a chip or board DTS file must be
65 7) DTS is treated in general as driver-independent hardware description, thus
66 any DTS patches, regardless whether using existing or new bindings, should
68 the DTS. DTS will be anyway applied through separate tree or branch, so
72 their relevant portion of patchset, please split the DTS patches into
101 4) The DTS files should however never be applied via driver subsystem tree,
/linux/Documentation/process/
H A Dmaintainer-soc-clean-dts.rst4 SoC Platforms with DTS Compliance Requirements
14 Strict DTS DT Schema and dtc Compliance
17 No changes to the SoC platform Devicetree sources (DTS files) should introduce
18 new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are
/linux/drivers/thermal/intel/
H A DKconfig46 tristate "Intel SoCs DTS thermal driver"
52 temperature sensor (DTS). These SoCs have two additional DTSs in
53 addition to DTSs on CPU cores. Each DTS will be registered as a
60 tristate "Intel Quark DTS thermal driver"
64 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
65 The DTS will be registered as a thermal zone. There are two trip points:
/linux/arch/arm64/boot/dts/renesas/
H A Drenesas-smarc2.dtsi10 * corresponding macro SW_SDIO_M2E on the board DTS:
17 * corresponding macro SW_SER0_PMOD on the board DTS:
24 * corresponding macro SW_GPIO8_CAN0_STB/SW_GPIO8_CAN0_STB on the board DTS:
/linux/Documentation/hwmon/
H A Dpeci-cputemp.rst37 Thermal Sensor (DTS) thermal readings of the CPU package and CPU cores that are
58 temp2_label "DTS"
60 to match DTS thermal profile.
/linux/Documentation/arch/arm/keystone/
H A Doverview.rst57 specified through DTS. Following are the DTS used:
/linux/Documentation/sound/cards/
H A Daudiophile-usb.rst22 - Added AC3/DTS passthru info
73 * The Do port additionally supports surround-encoded AC-3 and DTS passthrough,
129 * hw:1,2 is Do in AC3/DTS passthrough mode
259 AC3 w/ DTS passthru mode
267 - AC3 with DTS passthru
270 The command line used to playback the AC3/DTS encoded .wav-files in this mode:
334 | 0 | 0 | 0 | Di|24B|96K|DTS|SET|
343 * b1 is the ``DTS`` bit
345 - it is set only for Digital output with DTS/AC3
462 * if DTS is chosen, only Interface 2 with AltSet nb.6 must be
/linux/arch/arm64/boot/dts/arm/
H A Dfoundation-v8-gicv3-psci.dts4 * ARMv8 Foundation model DTS (GICv3+PSCI configuration)
H A Dfoundation-v8-psci.dts4 * ARMv8 Foundation model DTS (GICv2+PSCI configuration)
H A Dfoundation-v8.dts5 * ARMv8 Foundation model DTS (GICv2 configuration)
H A Dfoundation-v8-gicv3.dts5 * ARMv8 Foundation model DTS (GICv3 configuration)
H A Dfoundation-v8-psci.dtsi4 * ARMv8 Foundation model DTS (PSCI configuration)
H A Dfoundation-v8-gicv2.dtsi4 * ARMv8 Foundation model DTS (GICv2 configuration)
H A Dfoundation-v8-spin-table.dtsi4 * ARMv8 Foundation model DTS (spin table configuration)
H A Dfoundation-v8-gicv3.dtsi4 * ARMv8 Foundation model DTS (GICv3 configuration)
/linux/Documentation/i2c/
H A Di2c-sysfs.rst101 to a different number in logical I2C bus level in Device Tree Source (DTS) under
103 for an example of DTS file.
127 | |-- 73-0070 (I2C MUX at 0x70, exists in DTS, but failed to probe)
188 in DTS. There is a 4-channel MUX at address 0x71 on that bus. There is another
280 If not specified in DTS, when an I2C MUX driver is applied and the MUX device is
288 logical I2C bus number in the DTS. This doc will not go through the details on
289 how to implement this in DTS, but we can see an example in:
293 I2C bus 2. The channel 2 of the MUX is defined as ``imux18`` in DTS,
/linux/arch/mips/loongson32/
H A DKconfig8 for the DTS file that will be used to produce the DTB linked into
/linux/arch/arm64/boot/dts/amd/
H A Damd-overdrive-rev-b1.dts3 * DTS file for AMD Seattle Overdrive Development Board
/linux/arch/arm64/boot/dts/sprd/
H A Dsp9863a-1h10.dts3 * Unisoc SP9863A-1h10 boards DTS file
H A Dums9620-2h10.dts3 * Unisoc UMS9620-2h10 board DTS file
H A Dsc9836-openphone.dts3 * Spreadtrum SC9836 openphone board DTS file
/linux/arch/arm/boot/dts/broadcom/
H A Dbcm47081.dtsi4 * DTS for BCM47081 SoC.
H A Dbcm963138dvt.dts3 * Broadcom BCM63138 Reference Board DTS
/linux/arch/arm64/boot/dts/ti/
H A Dk3-am6254atl.dtsi3 * DTS for AM625 SiP SoC family in Quad core configuration and 512MiB RAM.

123456