From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: "Santosh Kumar Yadav" <santoshkumar.yadav@barco.com>,
"Peter Korsgaard" <peter.korsgaard@barco.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Subject: Re: [PATCH] platform/x86: barco-p50-gpio: attach software node to its target GPIO device
Date: Thu, 2 Apr 2026 10:30:51 -0700 [thread overview]
Message-ID: <ac6m36bzve2gdSLa@google.com> (raw)
In-Reply-To: <CAMRc=McbuVrw5eNp6vhF1DJP=5YM8BA4yTM6wf_1Dcg_T2gBhQ@mail.gmail.com>
On Thu, Apr 02, 2026 at 06:39:16PM +0200, Bartosz Golaszewski wrote:
>
> Ah, maybe sashiko wasn't wrong after all but it definitely could do a
> better job explaining the actual issue.
Yeah, I agree. OTOH it did notice the problem. I missed it when I first
read the patch.
> I missed the fact that this is
> not a device described in firmware and as such doesn't have a firmware
> node. I see it now. Ok, I'll fix it in v2. In fact, I'll probably wait
> until v7.1-rc1 and use the new .swnode field.
Danilo tagged the commit adding swnode to platform_device_info so you
can ask to pull it in when applying the patch:
https://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git/tag/?h=platform_device_info_swnode-7.1-rc1
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-04-02 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 11:28 [PATCH] platform/x86: barco-p50-gpio: attach software node to its target GPIO device Bartosz Golaszewski
2026-04-01 2:09 ` Dmitry Torokhov
2026-04-02 8:29 ` Bartosz Golaszewski
2026-04-02 15:53 ` Dmitry Torokhov
2026-04-02 16:39 ` Bartosz Golaszewski
2026-04-02 17:30 ` Dmitry Torokhov [this message]
2026-04-03 7:30 ` Bartosz Golaszewski
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=ac6m36bzve2gdSLa@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=santoshkumar.yadav@barco.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