From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Marek Vasut <marex@denx.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: NXP i.MX U-Boot Team <uboot-imx@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Stefano Babic <sbabic@denx.de>, Tom Rini <trini@konsulko.com>,
u-boot <u-boot@dh-electronics.com>
Subject: RE: [PATCH V3 1/3] arm64: dts: imx8mp: Add aliases for the access to the EEMPROM ID page node
Date: Fri, 22 Nov 2024 21:57:51 +0000 [thread overview]
Message-ID: <9d26daffc5974e18b3f00dc4407dd402@dh-electronics.com> (raw)
In-Reply-To: <044e0ac0-9c86-404e-acb4-e1db149c4bf6@denx.de>
From: Marek Vasut <marex@denx.de>
Sent: Thursday, November 21, 2024 6:37 PM
> On 11/21/24 6:21 PM, Christoph Niedermaier wrote:
>> The new i.MX8M Plus DHCOM rev.200 is populated with M24C32-D EEPROM
>> that contains an additional write-lockable page called ID page. Add
>> aliases eeprom0wl and eeprom1wl for the access to the EEMPROM ID
>> page node.
>>
>> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> Subject reads EEMPROM , should be EEPROM
>
> With that fixed:
>
> Reviewed-by: Marek Vasut <marex@denx.de>
I see it is also wrong in the commit text.
Will fix both in V4.
Regards
Christoph
prev parent reply other threads:[~2024-11-22 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 17:21 [PATCH V3 1/3] arm64: dts: imx8mp: Add aliases for the access to the EEMPROM ID page node Christoph Niedermaier
2024-11-21 17:21 ` [PATCH V3 2/3] arm64: imx8mp: Read values from M24C32-D write-lockable page on DHCOM i.MX8MP Christoph Niedermaier
2024-11-24 21:01 ` Marek Vasut
2024-11-26 16:18 ` Christoph Niedermaier
2024-11-21 17:21 ` [PATCH V3 3/3] board: dhelectronics: Sync env variable dh_som_serial_number with SN Christoph Niedermaier
2024-11-24 21:10 ` Marek Vasut
2024-11-24 22:11 ` Marek Vasut
2024-11-27 16:11 ` Christoph Niedermaier
2024-11-21 17:37 ` [PATCH V3 1/3] arm64: dts: imx8mp: Add aliases for the access to the EEMPROM ID page node Marek Vasut
2024-11-22 21:57 ` Christoph Niedermaier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d26daffc5974e18b3f00dc4407dd402@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=festevam@gmail.com \
--cc=marex@denx.de \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@dh-electronics.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox