File Manager

003 File Manager

Current Path: /usr/src/sys/contrib/device-tree/Bindings/nvmem

usr / src / sys / contrib / device-tree / Bindings / nvmem /

📁 ..
📄 allwinner,sun4i-a10-sid.yaml(1.07 KB)
📄 amlogic-efuse.txt(907 B)
📄 amlogic-meson-mx-efuse.txt(600 B)
📄 brcm,ocotp.txt(533 B)
📄 imx-iim.yaml(1.04 KB)
📄 imx-ocotp.yaml(1.91 KB)
📄 ingenic,jz4780-efuse.yaml(789 B)
📄 lpc1850-otp.txt(533 B)
📄 lpc1857-eeprom.txt(918 B)
📄 mtk-efuse.txt(943 B)
📄 mxs-ocotp.yaml(811 B)
📄 nvmem-consumer.yaml(1.07 KB)
📄 nvmem.txt(64 B)
📄 nvmem.yaml(2.54 KB)
📄 qcom,qfprom.yaml(2.16 KB)
📄 qcom,spmi-sdam.yaml(1.7 KB)
📄 qfprom.txt(701 B)
📄 rockchip-efuse.yaml(1.54 KB)
📄 rockchip-otp.txt(844 B)
📄 sc27xx-efuse.txt(1.08 KB)
📄 snvs-lpgpr.txt(615 B)
📄 sprd-efuse.txt(883 B)
📄 st,stm32-romem.yaml(1.44 KB)
📄 uniphier-efuse.txt(961 B)
📄 vf610-ocotp.txt(507 B)
📄 xlnx,zynqmp-nvmem.txt(1 KB)
📄 zii,rave-sp-eeprom.txt(1.01 KB)

Editing: zii,rave-sp-eeprom.txt

Zodiac Inflight Innovations RAVE EEPROM Bindings

RAVE SP EEPROM device is a "MFD cell" device exposing physical EEPROM
attached to RAVE Supervisory Processor. It is expected that its Device
Tree node is specified as a child of the node corresponding to the
parent RAVE SP device (as documented in
Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)

Required properties:

- compatible: Should be "zii,rave-sp-eeprom"

Optional properties:

- zii,eeprom-name: Unique EEPROM identifier describing its function in the
  system. Will be used as created NVMEM deivce's name.

Data cells:

Data cells are child nodes of eerpom node, bindings for which are
documented in Documentation/devicetree/bindings/nvmem/nvmem.txt

Example:

rave-sp {
		compatible = "zii,rave-sp-rdu1";
		current-speed = <38400>;

eeprom@a4 {
			compatible = "zii,rave-sp-eeprom";
			reg = <0xa4 0x4000>;
			#address-cells = <1>;
			#size-cells = <1>;
			zii,eeprom-name = "main-eeprom";

wdt_timeout: wdt-timeout@81 {
				reg = <0x81 2>;
			};
		};
	}

003 File Manager

Editing: zii,rave-sp-eeprom.txt

Upload File

Create Folder