public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chester Lin <chester62515@gmail.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	NXP S32 Linux Team <s32@nxp.com>
Subject: Re: [PATCH v3 2/4] dt-bindings: gpio: add support for NXP S32G2/S32G3 SoCs
Date: Sat, 21 Sep 2024 22:58:46 +0100	[thread overview]
Message-ID: <20240921-party-glass-bfb7099c7ded@spud> (raw)
In-Reply-To: <bd5a2d24-164c-4707-a5fd-6584e444ee0b@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2841 bytes --]

On Fri, Sep 20, 2024 at 03:40:31PM +0200, Krzysztof Kozlowski wrote:
> On 20/09/2024 15:33, Andrei Stefanescu wrote:
> > Hi Conor,
> > 
> > Thank you for your review!
> > 
> > On 20/09/2024 15:46, Conor Dooley wrote:
> >> On Thu, Sep 19, 2024 at 04:47:22PM +0300, Andrei Stefanescu wrote:
> >>> Add support for the GPIO driver of the NXP S32G2/S32G3 SoCs.
> >>>
> >>> Signed-off-by: Phu Luu An <phu.luuan@nxp.com>
> >>> Signed-off-by: Larisa Grigore <larisa.grigore@nxp.com>
> >>> Signed-off-by: Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
> >>> Signed-off-by: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
> >>> ---
> >>>  .../bindings/gpio/nxp,s32g2-siul2-gpio.yaml   | 107 ++++++++++++++++++
> >>>  1 file changed, 107 insertions(+)
> >>>  create mode 100644 Documentation/devicetree/bindings/gpio/nxp,s32g2-siul2-gpio.yaml
> >>>
> >>> diff --git a/Documentation/devicetree/bindings/gpio/nxp,s32g2-siul2-gpio.yaml b/Documentation/devicetree/bindings/gpio/nxp,s32g2-siul2-gpio.yaml
> >>> new file mode 100644
> >>> index 000000000000..0548028e6745
> >>> --- /dev/null
> >>> +++ b/Documentation/devicetree/bindings/gpio/nxp,s32g2-siul2-gpio.yaml
> >>> @@ -0,0 +1,107 @@
> >>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
> >>> +# Copyright 2024 NXP
> >>> +%YAML 1.2
> >>> +---
> >>> +$id: http://devicetree.org/schemas/gpio/nxp,s32g2-siul2-gpio.yaml#
> >>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >>> +
> >>> +title: NXP S32G2 SIUL2 GPIO controller
> >>> +
> >>> +maintainers:
> >>> +  - Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>
> >>> +  - Larisa Grigore <larisa.grigore@nxp.com>
> >>> +  - Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
> >>> +
> >>> +description:
> >>> +  Support for the SIUL2 GPIOs found on the S32G2 and S32G3
> >>> +  chips. It includes an IRQ controller for all pins which have
> >>> +  an EIRQ associated.
> >>> +
> >>> +properties:
> >>> +  compatible:
> >>> +    items:
> >>> +      - const: nxp,s32g2-siul2-gpio
> >>
> >> Commit message and binding description say s32g2 and s32g3, but there's
> >> only a compatible here for g2.
> > 
> > Yes, the SIUL2 GPIO hardware is the same for both S32G2 and S32G3 SoCs. I plan
> > to reuse the same compatible when I add the SIUL2 GPIO device tree node for
> > the S32G3 boards. Would that be ok?
> 
> There are only few exceptions where re-using compatible is allowed. Was
> S32G on them? Please consult existing practice/maintainers and past reviews.

Pretty sure I had a similar conversation about another peripheral on
these devices, and it was established that these are not different fusings
etc, but rather are independent SoCs that reuse an IP core. Given that,
I'd expect to see a fallback compatible used here, as is the norm.

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-09-21 22:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 13:47 [PATCH v3 0/4] gpio: siul2-s32g2: add initial GPIO driver Andrei Stefanescu
2024-09-19 13:47 ` [PATCH v3 1/4] drivers: provide devm_platform_get_and_ioremap_resource_byname() Andrei Stefanescu
2024-09-19 13:47 ` [PATCH v3 2/4] dt-bindings: gpio: add support for NXP S32G2/S32G3 SoCs Andrei Stefanescu
2024-09-20 12:46   ` Conor Dooley
2024-09-20 13:33     ` Andrei Stefanescu
2024-09-20 13:40       ` Krzysztof Kozlowski
2024-09-21 21:58         ` Conor Dooley [this message]
2024-09-22 21:04           ` Krzysztof Kozlowski
2024-09-22 21:07             ` Conor Dooley
2024-09-23 10:47               ` Andrei Stefanescu
2024-09-23 21:34                 ` Conor Dooley
2024-09-23 21:35                   ` Conor Dooley
2024-09-22 21:04   ` Krzysztof Kozlowski
2024-09-23 15:05     ` Andrei Stefanescu
2024-09-19 13:47 ` [PATCH v3 3/4] gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support Andrei Stefanescu
2024-09-22 14:35   ` kernel test robot
2024-09-22 21:47   ` Amit Singh Tomar
2024-09-23 10:57     ` Andrei Stefanescu
2024-09-19 13:47 ` [PATCH v3 4/4] MAINTAINERS: add MAINTAINER for S32G2 SIUL2 GPIO driver Andrei Stefanescu

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=20240921-party-glass-bfb7099c7ded@spud \
    --to=conor@kernel.org \
    --cc=andrei.stefanescu@oss.nxp.com \
    --cc=brgl@bgdev.pl \
    --cc=chester62515@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbrugger@suse.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=s32@nxp.com \
    /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