From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-arm-msm@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFT] driver core: faux: allow to set the firmware node for a faux device
Date: Tue, 10 Mar 2026 13:43:18 +0100 [thread overview]
Message-ID: <2026031034-blazer-equal-871e@gregkh> (raw)
In-Reply-To: <CAMRc=MdWMMi0wP8jd9YMOLqfafwWf5TTbd4diM-fJKk72XVQBA@mail.gmail.com>
On Tue, Mar 10, 2026 at 01:29:53PM +0100, Bartosz Golaszewski wrote:
> On a completely unrelated note though - Greg: I think this patch could
> still be considered because we now have quite a lot of functionality
> put into software nodes and already have some auxiliary devices that
> use software nodes as a source of device properties/config using the
> same API as platform devices (fwnode). I think faux devices could also
> profit from it and not necessairly use custom struct. If that sounds
> good to you, I may convert one or two faux devices and send a series
> with actual users of this.
I don't understand why a device that has a fwnode would ever be a "faux"
device? Why wouldn't that just be a normal platform device?
faux devices were created to be not platform devices, to take away the
abuse where platform devices were being used because the api was simple
and people wanted a device in the tree somewhere, but there was not
actually any backing platform device present.
So the use of a fwnode here feels very odd to me, what am I missing?
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-10 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 13:45 [PATCH RFT] driver core: faux: allow to set the firmware node for a faux device Bartosz Golaszewski
2026-03-06 13:54 ` Greg Kroah-Hartman
2026-03-06 14:07 ` Bartosz Golaszewski
2026-03-06 14:13 ` Greg Kroah-Hartman
2026-03-06 14:24 ` Bartosz Golaszewski
2026-03-09 15:46 ` Shivendra Pratap
2026-03-09 15:55 ` Greg Kroah-Hartman
2026-03-10 12:29 ` Bartosz Golaszewski
2026-03-10 12:43 ` Greg Kroah-Hartman [this message]
2026-03-10 13:18 ` Bartosz Golaszewski
2026-03-12 15:25 ` Greg Kroah-Hartman
2026-03-10 13:16 ` Bartosz Golaszewski
2026-03-10 13:21 ` 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=2026031034-blazer-equal-871e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shivendra.pratap@oss.qualcomm.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