From: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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>,
Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>,
Larisa Grigore <larisa.grigore@nxp.com>
Cc: 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 2/3] drivers: gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support
Date: Mon, 26 Aug 2024 17:03:20 +0300 [thread overview]
Message-ID: <974b2f66-e855-4322-99ba-23cecd45c2c5@oss.nxp.com> (raw)
In-Reply-To: <fd18295c-6544-4da6-aab0-6d6b9c12581a@kernel.org>
Hi Krzysztof,
On 26/08/2024 12:10, Krzysztof Kozlowski wrote:
> On 26/08/2024 10:42, Andrei Stefanescu wrote:
Thank you for the quick review!
>> + raw_spin_lock_init(&gpio_dev->lock);
>
> Why do you use raw spin? Are you sure you need it (some people just
> replace it thinking this will help them in PREEMPT_RT without actually
> thinking if it is needed). IOW, do you have here irqchip anywhere?
I don't have an irqchip in this current patch series. There are, however,
other patches which add support for interrupts and implementations for
power management callbacks. I thought it would be easier for review if I
sent those after the current series gets merged.
>> +
>> +static const struct of_device_id siul2_gpio_dt_ids[] = {
>> + { .compatible = "nxp,s32g2-siul2-gpio", .data = &s32g2_device_data },
>
> Why do you have match data? There are no other variants.
We do have another match data in our downstream version. Could I keep it
here or should I remove it?
I will fix the other comments in v2.
Best regards,
Andrei
next prev parent reply other threads:[~2024-08-26 14:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 8:42 [PATCH 0/3] gpio: siul2-s32g2: add initial GPIO driver Andrei Stefanescu
2024-08-26 8:42 ` [PATCH 1/3] dt-bindings: gpio: add schema for NXP S32G2/S32G3 SoCs Andrei Stefanescu
2024-08-26 9:14 ` Krzysztof Kozlowski
2024-08-26 9:36 ` Krzysztof Kozlowski
2024-08-26 8:42 ` [PATCH 2/3] drivers: gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support Andrei Stefanescu
2024-08-26 9:10 ` Krzysztof Kozlowski
2024-08-26 14:03 ` Andrei Stefanescu [this message]
2024-08-26 14:04 ` Krzysztof Kozlowski
2024-09-06 8:43 ` Andrei Stefanescu
2024-09-06 9:39 ` Krzysztof Kozlowski
2024-09-06 9:45 ` Andrei Stefanescu
2024-09-06 9:53 ` Krzysztof Kozlowski
2024-09-06 11:50 ` Andrei Stefanescu
2024-09-06 12:02 ` Krzysztof Kozlowski
2024-08-26 9:42 ` Linus Walleij
2024-08-26 14:03 ` Andrei Stefanescu
2024-08-26 14:06 ` Andrew Lunn
2024-08-27 2:23 ` kernel test robot
2024-08-27 4:38 ` kernel test robot
2024-08-26 8:42 ` [PATCH 3/3] 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=974b2f66-e855-4322-99ba-23cecd45c2c5@oss.nxp.com \
--to=andrei.stefanescu@oss.nxp.com \
--cc=Ghennadi.Procopciuc@nxp.com \
--cc=brgl@bgdev.pl \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=larisa.grigore@nxp.com \
--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=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
all inboxes | Powered by JetHome®