| /linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | sprd-thermal.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/sprd-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Orson Zhai <orsonzhai@gmail.com>
11 - Baolin Wang <baolin.wang7@gmail.com>
12 - Chunyan Zhang <zhang.lyra@gmail.com>
16 const: sprd,ums512-thermal
24 clock-names:
26 - const: enable
[all …]
|
| D | allwinner,sun8i-a83t-ths.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/thermal/allwinner,sun8i-a83t-ths.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vasily Khoruzhick <anarsoul@gmail.com>
11 - Yangtao Li <tiny.windzz@gmail.com>
16 - allwinner,sun8i-a83t-ths
17 - allwinner,sun8i-h3-ths
18 - allwinner,sun8i-r40-ths
19 - allwinner,sun50i-a64-ths
[all …]
|
| D | qcom-tsens.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR MIT)
4 ---
5 $id: http://devicetree.org/schemas/thermal/qcom-tsens.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Amit Kucheria <amitk@kernel.org>
22 - description: v0.1 of TSENS
24 - enum:
25 - qcom,msm8916-tsens
26 - qcom,msm8939-tsens
27 - qcom,msm8974-tsens
[all …]
|
| D | imx-thermal.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/imx-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Guo <shawnguo@kernel.org>
11 - Anson Huang <Anson.Huang@nxp.com>
16 - fsl,imx6q-tempmon
17 - fsl,imx6sx-tempmon
18 - fsl,imx7d-tempmon
32 nvmem-cells:
[all …]
|
| D | mediatek-thermal.txt | 4 which measures the on-SoC temperatures. This device does not have its own ADC,
11 - compatible:
12 - "mediatek,mt8173-thermal" : For MT8173 family of SoCs
13 - "mediatek,mt2701-thermal" : For MT2701 family of SoCs
14 - "mediatek,mt2712-thermal" : For MT2712 family of SoCs
15 - "mediatek,mt7622-thermal" : For MT7622 SoC
16 - "mediatek,mt8183-thermal" : For MT8183 family of SoCs
17 - reg: Address range of the thermal controller
18 - interrupts: IRQ for the thermal controller
19 - clocks, clock-names: Clocks needed for the thermal controller. required
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/nvmem/ |
| D | nvmem-consumer.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/nvmem-consumer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM (Non Volatile Memory) Consumer Device Tree Bindings
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
15 nvmem:
16 $ref: /schemas/types.yaml#/definitions/phandle-array
18 List of phandle to the nvmem providers.
20 nvmem-cells:
[all …]
|
| D | sprd-efuse.txt | 4 - compatible: Should be "sprd,ums312-efuse".
5 - reg: Specify the address offset of efuse controller.
6 - clock-names: Should be "enable".
7 - clocks: The phandle and specifier referencing the controller's clock.
8 - hwlocks: Reference to a phandle of a hwlock provider node.
12 bindings/nvmem/nvmem.txt
17 compatible = "sprd,ums312-efuse";
19 clock-names = "enable";
30 Are device nodes which consume nvmem data cells.
37 nvmem-cells = <&thermal_calib>;
[all …]
|
| D | mtk-efuse.txt | 1 = Mediatek MTK-EFUSE device tree bindings =
3 This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs.
6 - compatible: should be
7 "mediatek,mt7622-efuse", "mediatek,efuse": for MT7622
8 "mediatek,mt7623-efuse", "mediatek,efuse": for MT7623
9 "mediatek,mt8173-efuse" or "mediatek,efuse": for MT8173
10 - reg: Should contain registers location and length
13 Are child nodes of MTK-EFUSE, bindings of which as described in
14 bindings/nvmem/nvmem.txt
19 compatible = "mediatek,mt8173-efuse";
[all …]
|
| D | amlogic-efuse.txt | 4 - compatible: should be "amlogic,meson-gxbb-efuse"
5 - clocks: phandle to the efuse peripheral clock provided by the
7 - secure-monitor: phandle to the secure-monitor node
11 bindings/nvmem/nvmem.txt
16 compatible = "amlogic,meson-gxbb-efuse";
18 #address-cells = <1>;
19 #size-cells = <1>;
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
36 compatible = "amlogic,meson-gxbb-sm";
[all …]
|
| D | xlnx,zynqmp-nvmem.txt | 1 --------------------------------------------------------------------------
2 = Zynq UltraScale+ MPSoC nvmem firmware driver binding =
3 --------------------------------------------------------------------------
8 - compatible: should be "xlnx,zynqmp-nvmem-fw"
12 bindings/nvmem/nvmem.txt
14 -------
16 -------
18 zynqmp_firmware: zynqmp-firmware {
19 compatible = "xlnx,zynqmp-firmware";
23 compatible = "xlnx,zynqmp-nvmem-fw";
[all …]
|
| D | uniphier-efuse.txt | 3 This UniPhier eFuse must be under soc-glue.
6 - compatible: should be "socionext,uniphier-efuse"
7 - reg: should contain the register location and length
11 bindings/nvmem/nvmem.txt
15 soc-glue@5f900000 {
16 compatible = "socionext,uniphier-ld20-soc-glue-debug",
17 "simple-mfd";
18 #address-cells = <1>;
19 #size-cells = <1>;
23 compatible = "socionext,uniphier-efuse";
[all …]
|
| D | sc27xx-efuse.txt | 4 - compatible: Should be one of the following.
5 "sprd,sc2720-efuse"
6 "sprd,sc2721-efuse"
7 "sprd,sc2723-efuse"
8 "sprd,sc2730-efuse"
9 "sprd,sc2731-efuse"
10 - reg: Specify the address offset of efuse controller.
11 - hwlocks: Reference to a phandle of a hwlock provider node.
15 bindings/nvmem/nvmem.txt
22 spi-max-frequency = <26000000>;
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/net/ |
| D | nixge.txt | 4 - compatible: Should be "ni,xge-enet-3.00", but can be "ni,xge-enet-2.00" for
5 older device trees with DMA engines co-located in the address map,
7 - reg: Address and length of the register set for the device. It contains the
8 information of registers in the same order as described by reg-names.
9 - reg-names: Should contain the reg names
12 - interrupts: Should contain tx and rx interrupt
13 - interrupt-names: Should be "rx" and "tx"
14 - phy-mode: See ethernet.txt file in the same directory.
15 - nvmem-cells: Phandle of nvmem cell containing the MAC address
16 - nvmem-cell-names: Should be "address"
[all …]
|
| D | ti-bluetooth.txt | 2 ---------------------------------
21 - compatible: should be one of the following:
23 "ti,wl1271-st"
24 "ti,wl1273-st"
25 "ti,wl1281-st"
26 "ti,wl1283-st"
27 "ti,wl1285-st"
28 "ti,wl1801-st"
29 "ti,wl1805-st"
30 "ti,wl1807-st"
[all …]
|
| /linux-5.10/drivers/nvmem/ |
| D | core.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * nvmem framework core.
6 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
16 #include <linux/nvmem-consumer.h>
17 #include <linux/nvmem-provider.h>
54 struct nvmem_device *nvmem; member
69 static int nvmem_reg_read(struct nvmem_device *nvmem, unsigned int offset, in nvmem_reg_read() argument
72 if (nvmem->reg_read) in nvmem_reg_read()
73 return nvmem->reg_read(nvmem->priv, offset, val, bytes); in nvmem_reg_read()
75 return -EINVAL; in nvmem_reg_read()
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | nvmem-reboot-mode.txt | 1 NVMEM reboot mode driver
3 This driver gets reboot mode magic value from reboot-mode driver
4 and stores it in a NVMEM cell named "reboot-mode". Then the bootloader
9 - compatible: should be "nvmem-reboot-mode".
10 - nvmem-cells: A phandle to the reboot mode provided by a nvmem device.
11 - nvmem-cell-names: Should be "reboot-mode".
13 The rest of the properties should follow the generic reboot-mode description
14 found in reboot-mode.txt
17 reboot-mode {
18 compatible = "nvmem-reboot-mode";
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/iio/adc/ |
| D | sprd,sc2720-adc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/sprd,sc2720-adc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Baolin Wang <baolin.wang7@gmail.com>
18 - sprd,sc2720-adc
19 - sprd,sc2721-adc
20 - sprd,sc2723-adc
21 - sprd,sc2730-adc
22 - sprd,sc2731-adc
[all …]
|
| D | amlogic,meson-saradc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/amlogic,meson-saradc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Martin Blumenstingl <martin.blumenstingl@googlemail.com>
18 - const: amlogic,meson-saradc
19 - items:
20 - enum:
21 - amlogic,meson8-saradc
22 - amlogic,meson8b-saradc
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | socionext,uniphier-usb3hs-phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/socionext,uniphier-usb3hs-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Socionext UniPhier USB3 High-Speed (HS) PHY
12 Although the controller includes High-Speed PHY and Super-Speed PHY,
13 this describes about High-Speed PHY.
16 - Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
21 - socionext,uniphier-pro5-usb3-hsphy
22 - socionext,uniphier-pxs2-usb3-hsphy
[all …]
|
| D | phy-rockchip-inno-hdmi.txt | 4 - compatible : should be one of the listed compatibles:
5 * "rockchip,rk3228-hdmi-phy",
6 * "rockchip,rk3328-hdmi-phy";
7 - reg : Address and length of the hdmi phy control register set
8 - clocks : phandle + clock specifier for the phy clocks
9 - clock-names : string, clock name, must contain "sysclk" for system
10 control and register configuration, "refoclk" for crystal-
11 oscillator reference PLL clock input and "refpclk" for pclk-
13 - #clock-cells: should be 0.
14 - clock-output-names : shall be the name for the output clock.
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | qcom,gcc-apq8064.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/clock/qcom,gcc-apq8064.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Stephen Boyd <sboyd@kernel.org>
11 - Taniya Das <tdas@codeaurora.org>
18 - dt-bindings/clock/qcom,gcc-msm8960.h
19 - dt-bindings/reset/qcom,gcc-msm8960.h
23 const: qcom,gcc-apq8064
25 '#clock-cells':
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,dsi.txt | 5 drive up to 4-lane MIPI DSI output. Two DSIs can be synchronized for dual-
9 - compatible: "mediatek,<chip>-dsi"
10 - the supported chips are mt2701, mt7623, mt8173 and mt8183.
11 - reg: Physical base address and length of the controller's registers
12 - interrupts: The interrupt signal from the function block.
13 - clocks: device clocks
14 See Documentation/devicetree/bindings/clock/clock-bindings.txt for details.
15 - clock-names: must contain "engine", "digital", and "hs"
16 - phys: phandle link to the MIPI D-PHY controller.
17 - phy-names: must contain "dphy"
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-sp-wdt.txt | 3 RAVE SP watchdog device is a "MFD cell" device corresponding to
7 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)
11 - compatible: Depending on wire protocol implemented by RAVE SP
13 - "zii,rave-sp-watchdog"
14 - "zii,rave-sp-watchdog-legacy"
18 - wdt-timeout: Two byte nvmem cell specified as per
19 Documentation/devicetree/bindings/nvmem/nvmem.txt
23 rave-sp {
24 compatible = "zii,rave-sp-rdu1";
25 current-speed = <38400>;
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | sc27xx-fg.txt | 4 - compatible: Should be one of the following:
5 "sprd,sc2720-fgu",
6 "sprd,sc2721-fgu",
7 "sprd,sc2723-fgu",
8 "sprd,sc2730-fgu",
9 "sprd,sc2731-fgu".
10 - reg: The address offset of fuel gauge unit.
11 - battery-detect-gpios: GPIO for battery detection.
12 - io-channels: Specify the IIO ADC channels to get temperature and charge voltage.
13 - io-channel-names: Should be "bat-temp" or "charge-vol".
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/power/avs/ |
| D | qcom,cpr.txt | 10 - compatible:
13 Definition: should be "qcom,qcs404-cpr", "qcom,cpr" for qcs404
15 - reg:
17 Value type: <prop-encoded-array>
20 - interrupts:
22 Value type: <prop-encoded-array>
25 - clocks:
27 Value type: <prop-encoded-array>
30 - clock-names:
35 - vdd-apc-supply:
[all …]
|