From: <Durai.ManickamKR@microchip.com>
To: <post@lespocky.de>, <eugen.hristev@microchip.com>
Cc: <ada@thorsis.com>, <sergiu.moga@microchip.com>,
<michael@amarulasolutions.com>,
<dario.binacchi@amarulasolutions.com>,
<Balamanikandan.Gunasundar@microchip.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 3/5] ARM: dts: at91: sam9x60: Change i2c compatible
Date: Thu, 6 Jul 2023 08:32:41 +0000 [thread overview]
Message-ID: <a5d85b10-6b7c-88c7-2cb6-faceff6ecae4@microchip.com> (raw)
In-Reply-To: <20230705201701.322372-4-post@lespocky.de>
Hi Alexander,
sam9x60_curiosity and sam9x60ek belongs to same SOC family. So the
compatible string is updated as "microchip,sam9x60-i2c" in the
sam9x60.dtsi file. These changes are available in linux-6.4.y branch.
On 06/07/23 01:46, Alexander Dahl wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Alexander Dahl <ada@thorsis.com>
>
> There's a more specific compatible string for the i2c interface, use it.
>
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> ---
>
> Notes:
> I²C access to the eeprom did not work though, neither before nor after
> this change.
>
> arch/arm/dts/at91-sam9x60_curiosity.dts | 2 +-
> arch/arm/dts/sam9x60ek.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/dts/at91-sam9x60_curiosity.dts b/arch/arm/dts/at91-sam9x60_curiosity.dts
> index da5e19b66b..ae707dd64b 100644
> --- a/arch/arm/dts/at91-sam9x60_curiosity.dts
> +++ b/arch/arm/dts/at91-sam9x60_curiosity.dts
> @@ -21,7 +21,7 @@
> status = "okay";
>
> i2c@600 {
> - compatible = "atmel,sama5d2-i2c";
> + compatible = "microchip,sam9x60-i2c";
> reg = <0x600 0x200>;
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_flx0>;
> diff --git a/arch/arm/dts/sam9x60ek.dts b/arch/arm/dts/sam9x60ek.dts
> index 45e2f4cc40..74016f5e28 100644
> --- a/arch/arm/dts/sam9x60ek.dts
> +++ b/arch/arm/dts/sam9x60ek.dts
> @@ -62,7 +62,7 @@
> status = "okay";
>
> i2c@600 {
> - compatible = "atmel,sama5d2-i2c";
> + compatible = "microchip,sam9x60-i2c";
> reg = <0x600 0x200>;
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_flx0>;
> --
> 2.30.2
>
next prev parent reply other threads:[~2023-07-06 13:15 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 ` [PATCH 2/5] ARM: dts: at91: sam9x60-curiosity: Fix EEPROM type Alexander Dahl
2023-07-06 8:06 ` 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 [this message]
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=a5d85b10-6b7c-88c7-2cb6-faceff6ecae4@microchip.com \
--to=durai.manickamkr@microchip.com \
--cc=Balamanikandan.Gunasundar@microchip.com \
--cc=ada@thorsis.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=eugen.hristev@microchip.com \
--cc=michael@amarulasolutions.com \
--cc=post@lespocky.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox