From: Alexander Dahl <post@lespocky.de>
To: Eugen Hristev <eugen.hristev@microchip.com>
Cc: Alexander Dahl <ada@thorsis.com>,
Durai Manickam KR <durai.manickamkr@microchip.com>,
Sergiu Moga <sergiu.moga@microchip.com>,
u-boot@lists.denx.de
Subject: [PATCH 2/5] ARM: dts: at91: sam9x60-curiosity: Fix EEPROM type
Date: Wed, 5 Jul 2023 22:16:58 +0200 [thread overview]
Message-ID: <20230705201701.322372-3-post@lespocky.de> (raw)
In-Reply-To: <20230705201701.322372-1-post@lespocky.de>
From: Alexander Dahl <ada@thorsis.com>
The user guide says it's a Microchip 24AA025E48 serial EEPROM, which is
a 2-Kbit I2C Serial EEPROM with EUI-48™ Identity. This is the chip
actually populated on board EV40E67A rev 4.
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
Notes:
Sadly this did not fix the problem, that I could not access that
eeprom through I²C.
arch/arm/dts/at91-sam9x60_curiosity.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/dts/at91-sam9x60_curiosity.dts b/arch/arm/dts/at91-sam9x60_curiosity.dts
index d6ae3d648d..da5e19b66b 100644
--- a/arch/arm/dts/at91-sam9x60_curiosity.dts
+++ b/arch/arm/dts/at91-sam9x60_curiosity.dts
@@ -31,7 +31,7 @@
status = "okay";
eeprom@53 {
- compatible = "atmel,24c32";
+ compatible = "atmel,24c02";
reg = <0x53>;
pagesize = <16>;
};
--
2.30.2
next prev parent reply other threads:[~2023-07-05 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 20:16 [PATCH 0/5] ARM: dts: at91: Improve sam9x60-curiosity Alexander Dahl
2023-07-05 20:16 ` [PATCH 1/5] ARM: dts: at91: sam9x60: Better align with upstream dtsi Alexander Dahl
2023-07-05 20:16 ` Alexander Dahl [this message]
2023-07-06 8:06 ` [PATCH 2/5] ARM: dts: at91: sam9x60-curiosity: Fix EEPROM type Eugen Hristev
2023-07-06 8:12 ` Eugen Hristev
2023-07-06 8:30 ` Durai.ManickamKR
2023-07-06 9:08 ` Durai.ManickamKR
2023-07-05 20:16 ` [PATCH 3/5] ARM: dts: at91: sam9x60: Change i2c compatible Alexander Dahl
2023-07-06 8:32 ` Durai.ManickamKR
2023-07-06 8:59 ` Alexander Dahl
2023-07-06 9:09 ` Durai.ManickamKR
2023-07-05 20:17 ` [PATCH 4/5] ARM: dts: at91: sam9x60-curiosity: Improve alignment with upstream Alexander Dahl
2023-07-05 20:17 ` [PATCH 5/5] ARM: dts: at91: sam9x60-curiosity: Add raw NAND flash Alexander Dahl
2023-08-02 7:29 ` [PATCH 0/5] ARM: dts: at91: Improve sam9x60-curiosity Eugen Hristev
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=20230705201701.322372-3-post@lespocky.de \
--to=post@lespocky.de \
--cc=ada@thorsis.com \
--cc=durai.manickamkr@microchip.com \
--cc=eugen.hristev@microchip.com \
--cc=sergiu.moga@microchip.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.