Home
last modified time | relevance | path

Searched +full:nvmem +full:- +full:cells (Results 1 – 25 of 144) sorted by relevance

123456

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/
Dsprd-thermal.yaml1 # 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 …]
Dallwinner,sun8i-a83t-ths.yaml1 # 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/nvmem/
Dnvmem.txt1 = NVMEM(Non Volatile Memory) Data Device Tree Bindings =
7 some data on NVMEM, for the OS to be able to retrieve these information
14 Contains bindings specific to provider drivers and data cells as children
18 read-only: Mark the provider as read only.
20 = Data cells =
22 information like offset and size in nvmem provider.
31 Offset takes values from 0-7.
39 /* Data cells */
49 pvs_version: pvs-version@6 {
54 speed_bin: speed-bin@c{
[all …]
Dsc27xx-efuse.txt4 - 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.
13 = Data cells =
15 bindings/nvmem/nvmem.txt
[all …]
Duniphier-efuse.txt3 This UniPhier eFuse must be under soc-glue.
6 - compatible: should be "socionext,uniphier-efuse"
7 - reg: should contain the register location and length
9 = Data cells =
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>;
[all …]
Dmtk-efuse.txt1 = 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
12 = Data cells =
13 Are child nodes of MTK-EFUSE, bindings of which as described in
14 bindings/nvmem/nvmem.txt
[all …]
Damlogic-efuse.txt4 - compatible: should be "amlogic,meson-gxbb-efuse"
6 = Data cells =
8 bindings/nvmem/nvmem.txt
13 compatible = "amlogic,meson-gxbb-efuse";
14 #address-cells = <1>;
15 #size-cells = <1>;
31 Are device nodes which consume nvmem data cells.
37 nvmem-cells = <&eth_mac>;
38 nvmem-cell-names = "eth_mac";
Dqfprom.txt6 - compatible: should be "qcom,qfprom"
7 - reg: Should contain registers location and length
9 = Data cells =
11 bindings/nvmem/nvmem.txt
19 /* Data cells */
27 Are device nodes which consume nvmem data cells.
33 nvmem-cells = <&tsens_calibration>;
34 nvmem-cell-names = "calibration";
Drockchip-efuse.txt4 - compatible: Should be one of the following.
5 - "rockchip,rk3066a-efuse" - for RK3066a SoCs.
6 - "rockchip,rk3188-efuse" - for RK3188 SoCs.
7 - "rockchip,rk3228-efuse" - for RK3228 SoCs.
8 - "rockchip,rk3288-efuse" - for RK3288 SoCs.
9 - "rockchip,rk3328-efuse" - for RK3328 SoCs.
10 - "rockchip,rk3368-efuse" - for RK3368 SoCs.
11 - "rockchip,rk3399-efuse" - for RK3399 SoCs.
12 - reg: Should contain the registers location and exact eFuse size
13 - clocks: Should be the clock id of eFuse
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/nvmem/
Dnvmem-consumer.yaml1 # 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 …]
Dxlnx,zynqmp-nvmem.txt1 --------------------------------------------------------------------------
2 = Zynq UltraScale+ MPSoC nvmem firmware driver binding =
3 --------------------------------------------------------------------------
8 - compatible: should be "xlnx,zynqmp-nvmem-fw"
10 = Data cells =
12 bindings/nvmem/nvmem.txt
14 -------
16 -------
18 zynqmp_firmware: zynqmp-firmware {
19 compatible = "xlnx,zynqmp-firmware";
[all …]
Dsc27xx-efuse.txt4 - 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.
13 = Data cells =
15 bindings/nvmem/nvmem.txt
[all …]
Duniphier-efuse.txt3 This UniPhier eFuse must be under soc-glue.
6 - compatible: should be "socionext,uniphier-efuse"
7 - reg: should contain the register location and length
9 = Data cells =
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>;
[all …]
Dmtk-efuse.txt1 = 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
12 = Data cells =
13 Are child nodes of MTK-EFUSE, bindings of which as described in
14 bindings/nvmem/nvmem.txt
[all …]
Damlogic-efuse.txt4 - 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
9 = Data cells =
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 {
[all …]
Dsprd-efuse.txt4 - 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.
10 = Data cells =
12 bindings/nvmem/nvmem.txt
17 compatible = "sprd,ums312-efuse";
19 clock-names = "enable";
23 /* Data cells */
[all …]
/kernel/linux/linux-5.10/drivers/nvmem/
Dcore.c1 // 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>
36 struct list_head cells; member
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()
[all …]
/kernel/linux/linux-4.19/drivers/nvmem/
Dcore.c2 * nvmem framework core.
5 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
23 #include <linux/nvmem-consumer.h>
24 #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()
78 static int nvmem_reg_write(struct nvmem_device *nvmem, unsigned int offset, in nvmem_reg_write() argument
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dqcom,gcc-apq8064.yaml1 # 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/
Dsprd,sc2720-adc.yaml1 # 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 …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dnvmem.rst1 .. SPDX-License-Identifier: GPL-2.0
4 NVMEM Subsystem
9 This document explains the NVMEM Framework along with the APIs provided,
14 *NVMEM* is the abbreviation for Non Volatile Memory layer. It is used to
18 Before this framework existed, NVMEM drivers like eeprom were stored in
20 register a sysfs file, allow in-kernel users to access the content of the
23 This was also a problem as far as other in-kernel users were involved, since
33 NVMEM Providers
36 NVMEM provider refers to an entity that implements methods to initialize, read
37 and write the non-volatile memory.
[all …]
/kernel/linux/linux-5.10/include/linux/
Dnvmem-provider.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * nvmem framework provider.
6 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
30 #define NVMEM_DEVID_NONE (-1)
31 #define NVMEM_DEVID_AUTO (-2)
34 * struct nvmem_config - NVMEM device configuration
40 * @cells: Optional array of pre-defined NVMEM cells.
41 * @ncells: Number of elements in cells.
42 * @type: Type of the nvmem storage
43 * @read_only: Device is read-only.
[all …]
/kernel/linux/linux-4.19/include/linux/
Dnvmem-provider.h2 * nvmem framework provider.
5 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
26 * struct nvmem_config - NVMEM device configuration
32 * @cells: Optional array of pre-defined NVMEM cells.
33 * @ncells: Number of elements in cells.
34 * @read_only: Device is read-only.
43 * Note: A default "nvmem<id>" name will be assigned to the device if
47 * Note: Specifying name and setting id to -1 implies a unique device
48 * whose name is provided as-is (kept unaltered).
55 const struct nvmem_cell_info *cells; member
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dnixge.txt4 - 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/
Dsocionext,uniphier-usb3hs-phy.yaml1 # 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 …]

123456