From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Arnd Bergmann <arnd@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Hans de Goede <hansg@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Allow attaching software node when registering platform devices
Date: Fri, 13 Feb 2026 18:52:42 -0800 [thread overview]
Message-ID: <20260214025246.2095239-1-dmitry.torokhov@gmail.com> (raw)
When converting legacy board code to use static device properties,
especially when using static device properties for GPIO references,
it is often required to attach a secondary software node to platform
devices being created.
To reduce the amount of boilerplate needed add 'swnode' field to
platform_device_info structure and attach this software node (and
register it if it is not yet registered) as a secondary node to the
new platform device.
v2:
- add kerneldoc for platform_device_info
- split out formatting changes into a separate patch
Dmitry Torokhov (3):
driver core: platform: add kerneldoc to struct platform_device_info
driver core: platform: allow attaching software nodes when creating
devices
driver core: platform: fix various formatting issues
drivers/base/platform.c | 58 ++++++++++++++++-----------------
include/linux/platform_device.h | 58 ++++++++++++++++++++++++++-------
2 files changed, 76 insertions(+), 40 deletions(-)
Thanks.
--
Dmitry
next reply other threads:[~2026-02-14 2:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 2:52 Dmitry Torokhov [this message]
2026-02-14 2:52 ` [PATCH v2 1/3] driver core: platform: add kerneldoc to struct platform_device_info Dmitry Torokhov
2026-02-16 13:31 ` Bartosz Golaszewski
2026-02-14 2:52 ` [PATCH v2 2/3] driver core: platform: allow attaching software nodes when creating devices Dmitry Torokhov
2026-02-16 13:31 ` Bartosz Golaszewski
2026-02-14 2:52 ` [PATCH v2 3/3] driver core: platform: fix various formatting issues Dmitry Torokhov
2026-02-16 13:31 ` Bartosz Golaszewski
2026-02-14 10:55 ` [PATCH v2 0/3] Allow attaching software node when registering platform devices Danilo Krummrich
2026-03-01 5:02 ` Dmitry Torokhov
2026-03-02 0:42 ` Danilo Krummrich
2026-03-02 14:39 ` Danilo Krummrich
2026-03-03 15:55 ` Dmitry Torokhov
2026-03-03 16:45 ` Danilo Krummrich
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=20260214025246.2095239-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@kernel.org \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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
Powered by JetHome