Home
last modified time | relevance | path

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

1234

/Linux-v5.4/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>
20 #include "nvmem.h"
29 struct nvmem_device *nvmem; member
45 static int nvmem_reg_read(struct nvmem_device *nvmem, unsigned int offset, in nvmem_reg_read() argument
48 if (nvmem->reg_read) in nvmem_reg_read()
49 return nvmem->reg_read(nvmem->priv, offset, val, bytes); in nvmem_reg_read()
[all …]
Dnvmem.h1 /* SPDX-License-Identifier: GPL-2.0 */
10 #include <linux/nvmem-consumer.h>
11 #include <linux/nvmem-provider.h>
26 struct list_head cells; member
37 struct nvmem_device *nvmem,
39 int nvmem_sysfs_setup_compat(struct nvmem_device *nvmem,
41 void nvmem_sysfs_remove_compat(struct nvmem_device *nvmem,
45 struct nvmem_device *nvmem, in nvmem_sysfs_get_groups() argument
51 static inline int nvmem_sysfs_setup_compat(struct nvmem_device *nvmem, in nvmem_sysfs_setup_compat() argument
54 return -ENOSYS; in nvmem_sysfs_setup_compat()
[all …]
/Linux-v5.4/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
8 = Data cells =
10 bindings/nvmem/nvmem.txt
15 compatible = "amlogic,meson-gxbb-efuse";
17 #address-cells = <1>;
18 #size-cells = <1>;
34 Are device nodes which consume nvmem data cells.
40 nvmem-cells = <&eth_mac>;
41 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 …]
Dnvmem.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/nvmem.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM (Non Volatile Memory) Device Tree Bindings
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
17 some data on NVMEM, for the OS to be able to retrieve these
24 pattern: "^(eeprom|efuse|nvram)(@.*|-[0-9a-f])*$"
26 "#address-cells":
29 "#size-cells":
[all …]
Dzii,rave-sp-eeprom.txt7 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)
11 - compatible: Should be "zii,rave-sp-eeprom"
15 - zii,eeprom-name: Unique EEPROM identifier describing its function in the
16 system. Will be used as created NVMEM deivce's name.
18 Data cells:
20 Data cells are child nodes of eerpom node, bindings for which are
21 documented in Documentation/devicetree/bindings/nvmem/nvmem.txt
25 rave-sp {
26 compatible = "zii,rave-sp-rdu1";
27 current-speed = <38400>;
[all …]
/Linux-v5.4/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 * struct nvmem_config - NVMEM device configuration
36 * @cells: Optional array of pre-defined NVMEM cells.
37 * @ncells: Number of elements in cells.
38 * @type: Type of the nvmem storage
39 * @read_only: Device is read-only.
49 * Note: A default "nvmem<id>" name will be assigned to the device if
53 * Note: Specifying name and setting id to -1 implies a unique device
[all …]
/Linux-v5.4/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 …]
/Linux-v5.4/Documentation/devicetree/bindings/thermal/
Dqcom-tsens.txt4 - compatible:
6 - "qcom,msm8916-tsens" (MSM8916)
7 - "qcom,msm8974-tsens" (MSM8974)
8 - "qcom,msm8996-tsens" (MSM8996)
9 - "qcom,qcs404-tsens", "qcom,tsens-v1" (QCS404)
10 - "qcom,msm8998-tsens", "qcom,tsens-v2" (MSM8998)
11 - "qcom,sdm845-tsens", "qcom,tsens-v2" (SDM845)
12 The generic "qcom,tsens-v2" property must be used as a fallback for any SoC
15 Similarly, the generic "qcom,tsens-v1" property must be used as a fallback for
18 - reg: Address range of the thermal registers.
[all …]
Dmediatek-thermal.txt4 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 …]
Dimx-thermal.txt4 - compatible : must be one of following:
5 - "fsl,imx6q-tempmon" for i.MX6Q,
6 - "fsl,imx6sx-tempmon" for i.MX6SX,
7 - "fsl,imx7d-tempmon" for i.MX7S/D.
8 - interrupts : the interrupt output of the controller:
13 - fsl,tempmon : phandle pointer to system controller that contains TEMPMON
15 - nvmem-cells: A phandle to the calibration cells provided by ocotp.
16 - nvmem-cell-names: Should be "calib", "temp_grade".
19 - fsl,tempmon-data : phandle pointer to fuse controller that contains TEMPMON
23 Direct access to OCOTP via fsl,tempmon-data is incorrect on some newer chips
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/phy/
Duniphier-usb3-hsphy.txt1 Socionext UniPhier USB3 High-Speed (HS) PHY
5 Although the controller includes High-Speed PHY and Super-Speed PHY,
6 this describes about High-Speed PHY.
9 - compatible: Should contain one of the following:
10 "socionext,uniphier-pro4-usb3-hsphy" - for Pro4 SoC
11 "socionext,uniphier-pxs2-usb3-hsphy" - for PXs2 SoC
12 "socionext,uniphier-ld20-usb3-hsphy" - for LD20 SoC
13 "socionext,uniphier-pxs3-usb3-hsphy" - for PXs3 SoC
14 - reg: Specifies offset and length of the register set for the device.
15 - #phy-cells: Should be 0.
[all …]
Dphy-rockchip-inno-hdmi.txt4 - 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-v5.4/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 …]
Dti-bluetooth.txt2 ---------------------------------
19 ../serial/slave-device.txt.
22 - compatible: should be one of the following:
24 "ti,wl1271-st"
25 "ti,wl1273-st"
26 "ti,wl1281-st"
27 "ti,wl1283-st"
28 "ti,wl1285-st"
29 "ti,wl1801-st"
30 "ti,wl1805-st"
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/opp/
Dsun50i-nvmem-cpufreq.txt1 Allwinner Technologies, Inc. NVMEM CPUFreq and OPP bindings
7 speedbin blown in the efuse combination. The sun50i-cpufreq-nvmem driver
12 --------------------
14 - operating-points-v2: Phandle to the operating-points-v2 table to use.
16 In 'operating-points-v2' table:
17 - compatible: Should be
18 - 'allwinner,sun50i-h6-operating-points'.
19 - nvmem-cells: A phandle pointing to a nvmem-cells node representing the
22 pair. Please refer the for nvmem-cells bindings
23 Documentation/devicetree/bindings/nvmem/nvmem.txt and
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/power/reset/
Dnvmem-reboot-mode.txt1 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-v5.4/Documentation/devicetree/bindings/iio/adc/
Dsprd,sc27xx-adc.txt4 - compatible: Should be one of the following.
5 "sprd,sc2720-adc"
6 "sprd,sc2721-adc"
7 "sprd,sc2723-adc"
8 "sprd,sc2730-adc"
9 "sprd,sc2731-adc"
10 - reg: The address offset of ADC controller.
11 - interrupt-parent: The interrupt controller.
12 - interrupts: The interrupt number for the ADC device.
13 - #io-channel-cells: Number of cells in an IIO specifier.
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/power/supply/
Dsc27xx-fg.txt4 - 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 …]

1234