[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200910134239.192030-1-jonathanh@nvidia.com>
Date: Thu, 10 Sep 2020 14:42:34 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>
CC: <linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
Jon Hunter <jonathanh@...dia.com>
Subject: [PATCH 0/5] Add support for custom names for AT24 EEPROMs
For platforms that have multiple boards and hence have multiple EEPROMs
for identifying the different boards, it is useful to label the EEPROMs
in device-tree so that they can be easily identified. For example, MAC
address information is stored in the EEPROM on the processor module for
some Jetson platforms which is not only required by the kernel but the
bootloader as well. So having a simple way to identify the EEPROM is
needed.
Jon Hunter (5):
misc: eeprom: at24: Initialise AT24 NVMEM ID field
dt-bindings: eeprom: at24: Add label property for AT24
misc: eeprom: at24: Support custom device names for AT24 EEPROMs
arm64: tegra: Add label properties for EEPROMs
arm64: tegra: Populate EEPROMs for Jetson Xavier NX
.../devicetree/bindings/eeprom/at24.yaml | 4 ++++
.../boot/dts/nvidia/tegra186-p2771-0000.dts | 1 +
arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 1 +
arch/arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 1 +
.../boot/dts/nvidia/tegra194-p2972-0000.dts | 1 +
.../nvidia/tegra194-p3509-0000+p3668-0000.dts | 14 ++++++++++++++
.../boot/dts/nvidia/tegra194-p3668-0000.dtsi | 16 ++++++++++++++++
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 1 +
.../boot/dts/nvidia/tegra210-p2371-2180.dts | 1 +
.../boot/dts/nvidia/tegra210-p3450-0000.dts | 2 ++
drivers/misc/eeprom/at24.c | 11 ++++++++++-
11 files changed, 52 insertions(+), 1 deletion(-)
--
2.25.1
Powered by blists - more mailing lists