From: Li Yang <leoyang.li@nxp.com>
To: Raag Jadav <raagjadav@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
linux-i2c@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] arm64: dts: ls1046a: fix eeprom entries
Date: Fri, 6 Aug 2021 18:46:03 -0500 [thread overview]
Message-ID: <CADRPPNTkdLEwSa2Bg1enzWBpcGco6twcQwvk_QqDXa=V1foBLg@mail.gmail.com> (raw)
In-Reply-To: <1628105086-8172-2-git-send-email-raagjadav@gmail.com>
On Wed, Aug 4, 2021 at 4:32 PM Raag Jadav <raagjadav@gmail.com> wrote:
>
> ls1046afrwy and ls1046ardb boards have CAT24C04[1] and CAT24C05[2]
> eeproms respectively. Both are 4Kb (512 bytes) in size,
> and compatible with AT24C04[3].
> Remove multi-address entries, as both the boards have a single chip each.
>
> [1] https://www.onsemi.com/pdf/datasheet/cat24c01-d.pdf
> [2] https://www.onsemi.com/pdf/datasheet/cat24c03-d.pdf
> [3] https://ww1.microchip.com/downloads/en/DeviceDoc/doc0180.pdf
>
> Signed-off-by: Raag Jadav <raagjadav@gmail.com>
Acked-by: Li Yang <leoyang.li@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1046a-frwy.dts | 8 +-------
> arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts | 7 +------
> 2 files changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a-frwy.dts b/arch/arm64/boot/dts/freescale/fsl-ls1046a-frwy.dts
> index db3d303..6d22efb 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a-frwy.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a-frwy.dts
> @@ -83,15 +83,9 @@
> };
>
> eeprom@52 {
> - compatible = "atmel,24c512";
> + compatible = "onnn,cat24c04", "atmel,24c04";
> reg = <0x52>;
> };
> -
> - eeprom@53 {
> - compatible = "atmel,24c512";
> - reg = <0x53>;
> - };
> -
> };
> };
> };
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
> index 60acdf0..7025aad 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
> @@ -59,14 +59,9 @@
> };
>
> eeprom@52 {
> - compatible = "atmel,24c512";
> + compatible = "onnn,cat24c05", "atmel,24c04";
> reg = <0x52>;
> };
> -
> - eeprom@53 {
> - compatible = "atmel,24c512";
> - reg = <0x53>;
> - };
> };
>
> &i2c3 {
> --
> 2.7.4
>
next prev parent reply other threads:[~2021-08-06 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 19:24 [PATCH v2 0/2] fix eeprom entries for ls1046afrwy and ls1046ardb Raag Jadav
2021-08-04 19:24 ` [PATCH v2 1/2] arm64: dts: ls1046a: fix eeprom entries Raag Jadav
2021-08-06 23:46 ` Li Yang [this message]
2021-08-09 7:46 ` Shawn Guo
2021-08-04 19:24 ` [PATCH v2 2/2] dt-bindings: at24: add ON Semi CAT24C04 and CAT24C05 Raag Jadav
2021-08-05 19:08 ` Bartosz Golaszewski
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='CADRPPNTkdLEwSa2Bg1enzWBpcGco6twcQwvk_QqDXa=V1foBLg@mail.gmail.com' \
--to=leoyang.li@nxp.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raagjadav@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).