From: "Arnd Bergmann" <arnd@kernel.org>
To: "Bartosz Golaszewski" <brgl@kernel.org>
Cc: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Janusz Krzysztofik" <jmkrzyszt@gmail.com>,
"Tony Lindgren" <tony@atomide.com>,
"Russell King" <linux@armlinux.org.uk>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFT PATCH v2] ARM: omap1: enable real software node lookup of GPIOs on Nokia 770
Date: Thu, 12 Feb 2026 12:45:28 +0100 [thread overview]
Message-ID: <8a4b2d6f-acf4-414a-b695-65dd7eaa8863@app.fastmail.com> (raw)
In-Reply-To: <CAMRc=MeWgo3b8DTG3w8U2bxR6ejd2UmFVGASvRe7_tJkK2f4ug@mail.gmail.com>
On Thu, Feb 12, 2026, at 12:40, Bartosz Golaszewski wrote:
> On Wed, Feb 11, 2026 at 5:32 PM Arnd Bergmann <arnd@kernel.org> wrote:
>> On Wed, Feb 11, 2026, at 14:13, Bartosz Golaszewski wrote:
>
> Add a pointer to const struct software_node to platform_device_info
> and then use this if it's set and there's no fwnode? It's in line with
> what MFD does with its cells.
Right, that's what Dmitry also suggested, see his earlier patch/
> In any case, I'd prefer to not overcomplicate this patch, let's do it
> separately?
Sure, I mainly wanted to make sure we're not blocking future
changes here that I had already planned, and this sounds like
we can change that later without undoing all of your patch again.
Arnd
prev parent reply other threads:[~2026-02-12 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 13:13 Bartosz Golaszewski
2026-02-11 13:19 ` Bartosz Golaszewski
2026-02-11 16:31 ` Arnd Bergmann
2026-02-11 21:40 ` Dmitry Torokhov
2026-02-12 1:12 ` Dmitry Torokhov
2026-02-12 6:57 ` Arnd Bergmann
2026-02-12 11:40 ` Bartosz Golaszewski
2026-02-12 11:45 ` Arnd Bergmann [this message]
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=8a4b2d6f-acf4-414a-b695-65dd7eaa8863@app.fastmail.com \
--to=arnd@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hansg@kernel.org \
--cc=jmkrzyszt@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tony@atomide.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®