From: Conor Dooley <conor@kernel.org>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>
Subject: Re: [PATCH 1/2] dt-bindings: i2c: imx: add SoC specific compatible strings for S32G
Date: Mon, 4 Nov 2024 18:44:47 +0000 [thread overview]
Message-ID: <20241104-stifling-remake-f5abdc8d82bc@spud> (raw)
In-Reply-To: <20241104100044.3634076-2-ciprianmarian.costea@oss.nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On Mon, Nov 04, 2024 at 12:00:43PM +0200, Ciprian Costea wrote:
> From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>
> S32G2 and S32G3 SoCs use the same I2C controller as i.MX.
> But there are small differences such as specific
> <clock divider, register value> pairs.
> So add new compatible strings 'nxp,s32g2-i2c'and 'nxp,s32g3-i2c'
> for S32G2/S32G3 Socs.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Signed-off-by: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
> index 85ee1282d6d2..0682a5a10d41 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
> +++ b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml
> @@ -18,6 +18,7 @@ properties:
> - const: fsl,imx1-i2c
> - const: fsl,imx21-i2c
> - const: fsl,vf610-i2c
> + - const: nxp,s32g2-i2c
> - items:
> - enum:
> - fsl,ls1012a-i2c
> @@ -54,6 +55,9 @@ properties:
> - fsl,imx8mn-i2c
> - fsl,imx8mp-i2c
> - const: fsl,imx21-i2c
> + - items:
> + - const: nxp,s32g3-i2c
> + - const: nxp,s32g2-i2c
>
> reg:
> maxItems: 1
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-04 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 10:00 [PATCH 0/2] add I2C support for S32G2/S32G3 SoCs Ciprian Costea
2024-11-04 10:00 ` [PATCH 1/2] dt-bindings: i2c: imx: add SoC specific compatible strings for S32G Ciprian Costea
2024-11-04 16:37 ` Frank Li
2024-11-04 18:44 ` Conor Dooley [this message]
2024-11-04 10:00 ` [PATCH 2/2] i2c: imx: add support for S32G2/S32G3 SoCs Ciprian Costea
2024-11-04 16:42 ` Frank Li
2024-11-05 15:02 ` [PATCH 0/2] add I2C " Andi Shyti
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=20241104-stifling-remake-f5abdc8d82bc@spud \
--to=conor@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=aruizrui@redhat.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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