From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@kernel.org>,
Herve Codina <herve.codina@bootlin.com>,
Paul Louvel <paul.louvel@bootlin.com>
Subject: Re: [PATCH] soc: fsl: qe: properly scan GPIO nodes at startup
Date: Thu, 30 Jul 2026 14:05:19 +0200 [thread overview]
Message-ID: <f1b4c866-6cd7-4d6f-812b-d95e94f69e83@kernel.org> (raw)
In-Reply-To: <223afb76-9f6f-48a1-a5c5-beb1a641916c@kernel.org>
On 30/07/2026 14:01, Christophe Leroy (CS GROUP) wrote:
>
>
> Le 30/07/2026 à 13:14, Krzysztof Kozlowski a écrit :
>> On 29/07/2026 16:10, Christophe Leroy (CS GROUP) wrote:
>>> Before commit 156460811def ("soc: fsl: qe: Change GPIO driver to a
>>> proper platform driver") qe_add_gpiochips() was walking the device
>>> tree to find all nodes with compatible "fsl,mpc8323-qe-pario-bank".
>>>
>>> After that commit the discovery is handled by the platform core,
>>> therefore it is necessary to call of_platform_default_populate() on
>>> the par_io node.
>>>
>>> Fixes: 156460811def ("soc: fsl: qe: Change GPIO driver to a proper platform driver")
>>> Signed-off-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
>>> ---
>>> drivers/soc/fsl/qe/qe_io.c | 15 +++++++++++++++
>>> 1 file changed, 15 insertions(+)
>>>
>>> diff --git a/drivers/soc/fsl/qe/qe_io.c b/drivers/soc/fsl/qe/qe_io.c
>>> index a5e2d0e5ab51..02ca556c8db0 100644
>>> --- a/drivers/soc/fsl/qe/qe_io.c
>>> +++ b/drivers/soc/fsl/qe/qe_io.c
>>> @@ -15,6 +15,7 @@
>>> #include <linux/errno.h>
>>> #include <linux/module.h>
>>> #include <linux/ioport.h>
>>> +#include <linux/of_platform.h>
>>>
>>> #include <asm/io.h>
>>> #include <soc/fsl/qe/qe.h>
>>> @@ -184,3 +185,17 @@ int par_io_of_config(struct device_node *np)
>>> return 0;
>>> }
>>> EXPORT_SYMBOL(par_io_of_config);
>>> +
>>> +static int __init par_io_populate(void)
>>> +{
>>> + struct device_node *np = of_find_node_by_name(NULL, "par_io");
>>
>> No, node name must not be ABI. Especially wrong node name.
>
> What's wrong with the node name ?
1. It causes W=2 warnings (which we might move to W=1 at some point)
2. It is not generic and DT spec asks for generic node names, although
maybe this part of code follows more of ePAPR than DT. But ePAPR v1.1
also was asking for generic node names.
>
> Regardless, I messed it up, I wanted to use type but copy/pasted
> of_find_node_by_name(NULL, "par_io") from quirk_mpc8360e_qe_enet10() in
> arch/powerpc/platforms/83xx/km83xx.c instead.
>
> Is it OK to use of_find_node_by_type(NULL, "par_io") instead ?
Well, depends. Is it a documented ABI?
>
> We have:
>
> $ git grep par_io arch/powerpc/boot/dts/
> arch/powerpc/boot/dts/fsl/mpc8568mds.dts: par_io@e0100 {
> arch/powerpc/boot/dts/fsl/mpc8568si-post.dtsi: par_io@e0100 {
> arch/powerpc/boot/dts/fsl/mpc8568si-post.dtsi: device_type =
> "par_io";
These are all DTS, does not matter really. ABI is not documented via DTS
but bindings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-30 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 14:10 [PATCH] soc: fsl: qe: properly scan GPIO nodes at startup Christophe Leroy (CS GROUP)
2026-07-29 15:14 ` Bartosz Golaszewski
2026-07-29 15:21 ` Herve Codina
2026-07-30 8:11 ` Christophe Leroy (CS GROUP)
2026-07-30 9:29 ` Herve Codina
2026-07-30 8:14 ` Christophe Leroy (CS GROUP)
2026-07-30 11:15 ` Krzysztof Kozlowski
2026-07-30 12:04 ` Christophe Leroy (CS GROUP)
2026-07-30 12:09 ` Bartosz Golaszewski
2026-07-30 11:14 ` Krzysztof Kozlowski
2026-07-30 12:01 ` Christophe Leroy (CS GROUP)
2026-07-30 12:05 ` Krzysztof Kozlowski [this message]
2026-07-30 12:14 ` Christophe Leroy (CS GROUP)
2026-07-30 12:15 ` Krzysztof Kozlowski
2026-07-30 12:27 ` Christophe Leroy (CS GROUP)
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=f1b4c866-6cd7-4d6f-812b-d95e94f69e83@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=chleroy@kernel.org \
--cc=herve.codina@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul.louvel@bootlin.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