From: <Claudiu.Beznea@microchip.com>
To: <Eugen.Hristev@microchip.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH 1/2] ARM: dts: at91: sam9x60ek: fix eeprom compatible and size
Date: Tue, 28 Jun 2022 13:37:13 +0000 [thread overview]
Message-ID: <2b092bc6-5abc-d5db-8135-6a03bafa848c@microchip.com> (raw)
In-Reply-To: <20220607090455.80433-1-eugen.hristev@microchip.com>
On 07.06.2022 12:04, Eugen Hristev wrote:
> The board has a microchip 24aa025e48 eeprom, which is a 2 Kbits memory,
> so it's compatible with at24c02 not at24c32.
> Also the size property is wrong, it's not 128 bytes, but 256 bytes.
> Thus removing and leaving it to the default (256).
>
> Fixes: 1e5f532c27371 ("ARM: dts: at91: sam9x60: add device tree for soc and board")
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
Applied to at91-fixes. Thanks!
> ---
> arch/arm/boot/dts/at91-sam9x60ek.dts | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/at91-sam9x60ek.dts b/arch/arm/boot/dts/at91-sam9x60ek.dts
> index 7719ea3d4933c..81ccb0636a009 100644
> --- a/arch/arm/boot/dts/at91-sam9x60ek.dts
> +++ b/arch/arm/boot/dts/at91-sam9x60ek.dts
> @@ -233,10 +233,9 @@ i2c0: i2c@600 {
> status = "okay";
>
> eeprom@53 {
> - compatible = "atmel,24c32";
> + compatible = "atmel,24c02";
> reg = <0x53>;
> pagesize = <16>;
> - size = <128>;
> status = "okay";
> };
> };
prev parent reply other threads:[~2022-06-28 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 9:04 [PATCH 1/2] ARM: dts: at91: sam9x60ek: fix eeprom compatible and size Eugen Hristev
2022-06-07 9:04 ` [PATCH 2/2] ARM: dts: at91: sama5d2_icp: fix eeprom compatibles Eugen Hristev
2022-06-08 7:37 ` Claudiu.Beznea
2022-06-28 13:37 ` Claudiu.Beznea
2022-06-08 7:37 ` [PATCH 1/2] ARM: dts: at91: sam9x60ek: fix eeprom compatible and size Claudiu.Beznea
2022-06-28 13:37 ` Claudiu.Beznea [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=2b092bc6-5abc-d5db-8135-6a03bafa848c@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).