public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: <Eugen.Hristev@microchip.com>
To: <michael@walle.cc>
Cc: <hs@denx.de>, <rasmus.villemoes@prevas.dk>,
	<u-boot@lists.denx.de>, <Claudiu.Beznea@microchip.com>
Subject: Re: [PATCH 1/3] ARM: dts: at91: replace microchip,24aa02e48 with atmel,at24c02
Date: Thu, 26 May 2022 14:18:43 +0000	[thread overview]
Message-ID: <f8486d2d-9b4f-b1ff-aea5-57701f4729de@microchip.com> (raw)
In-Reply-To: <ff11480b40048965e4dc66f304295e59@walle.cc>

On 5/26/22 5:11 PM, Michael Walle wrote:

[snip]

>> @@ -92,7 +92,7 @@
>>                               status = "okay";
>>
>>                               i2c_eeprom: i2c_eeprom@50 {
> 
> Nit: that one should actually be just "eeprom@50".

Hi Michael,

That's true, but my patch just changes the compatible .

With time, I want to completely sync the DT with Linux. It will take 
some effort, but I am gathering the pieces of the puzzle slowly.

Thanks !

Eugen


> 
> -michael
> 
>> -                                     compatible = "microchip,24aa02e48";
>> +                                     compatible = "atmel,24c02"; /* 
>> EEPROM is 2Kbits microchip
>> 24aa02e48 */
>>                                       reg = <0x50>;
>>                               };
>>                       };


  reply	other threads:[~2022-05-26 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 14:04 [PATCH 1/3] ARM: dts: at91: replace microchip, 24aa02e48 with atmel, at24c02 Eugen Hristev
2022-05-26 14:04 ` [PATCH 2/3] misc: i2c_eeprom: remove 24aa02e48 Eugen Hristev
2022-05-26 14:11   ` Michael Walle
2022-05-31  4:44   ` Heiko Schocher
2022-05-26 14:04 ` [PATCH 3/3] ARM: dts: at91: sam9x60ek: fix eeprom compatible Eugen Hristev
2022-05-31  4:45   ` Heiko Schocher
2022-05-26 14:11 ` [PATCH 1/3] ARM: dts: at91: replace microchip,24aa02e48 with atmel,at24c02 Michael Walle
2022-05-26 14:18   ` Eugen.Hristev [this message]
2022-05-31  4:43     ` Heiko Schocher
2022-06-22 13:02       ` 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=f8486d2d-9b4f-b1ff-aea5-57701f4729de@microchip.com \
    --to=eugen.hristev@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=hs@denx.de \
    --cc=michael@walle.cc \
    --cc=rasmus.villemoes@prevas.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox