From: Linus Walleij <linusw@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
brgl@kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: RB532: attach the software node to its target GPIO controller
Date: Thu, 30 Apr 2026 13:47:11 +0200 [thread overview]
Message-ID: <CAD++jLkBmnvL0FMFdCc-sto10vqRs6wpXuGTme4cvH2vTZzg6g@mail.gmail.com> (raw)
In-Reply-To: <20260430-mips-rb532-gpio-v1-1-845a0c6206a5@oss.qualcomm.com>
On Thu, Apr 30, 2026 at 1:23 PM Bartosz Golaszewski
<bartosz.golaszewski@oss.qualcomm.com> wrote:
> GPIOLIB wants to remove the software node's name matching against GPIO
> controller's label that is going on behind the scenes in software node
> lookup. To that end, we need to convert all existing users to using
> software nodes actually attached to the GPIO devices they represent.
>
> In order to use an attached software node with the GPIO controller on
> rb532: convert the GPIO module into a real platform device, provide
> platform device info for it in device.c and assign the software node
> using its swnode field.
>
> The software node will get inherited by the GPIO chip from the parent
> platform device in devm_gpiochip_add_data() as we don't set the fwnode
> using any other of the mechanisms.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Looks good to me (TM).
Reviewed-by: Linus Walleij <linusw@kernel.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2026-04-30 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 11:23 [PATCH] MIPS: RB532: attach the software node to its target GPIO controller Bartosz Golaszewski
2026-04-30 11:47 ` Linus Walleij [this message]
2026-05-26 14:43 ` Thomas Bogendoerfer
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=CAD++jLkBmnvL0FMFdCc-sto10vqRs6wpXuGTme4cvH2vTZzg6g@mail.gmail.com \
--to=linusw@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).