From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 0/6] device property: Introducing software nodes
Date: Thu, 29 Nov 2018 22:11:29 +0100 [thread overview]
Message-ID: <1859438.TcbhMcUUHz@aspire.rjw.lan> (raw)
In-Reply-To: <20181109142138.54770-1-heikki.krogerus@linux.intel.com>
On Friday, November 9, 2018 3:21:32 PM CET Heikki Krogerus wrote:
> Hi,
>
> This is the second version of my proposal for "software nodes". There
> was a "dereferencing freed memory" bug in patch 3/5 which is now
> fixed. device_add_properties() and device_remove_properties() no
> longer change places in the code as requested by Andy.
>
> The original RFC can be checked from here:
> https://lkml.org/lkml/2018/10/12/518
>
> The origin commit message:
>
> To continue the discussion started by Dmitry [1], this is my proposal
> that I mentioned in my last mail. In short, the idea is that instead
> of trying to extend the support for the currently used struct
> property_set, I'm proposing that we introduce a completely new,
> independent type of fwnode, and replace the struct property_set with
> it. I'm calling the type "software node" here.
>
> The reason for a complete separation of the software nodes from the
> generic property handling code is the need to be able to create the
> nodes independently from the devices that they are bind to.
>
> The way this works is that every node that is created will have a
> kobject registered. That will take care the ref counting for us, and
> also allow us to for example display the properties in sysfs.
>
> There are a few more details in patch 3/5 about the software nodes in
> the commit message.
>
> [1] https://lkml.org/lkml/2018/9/17/1067
>
> --
> heikki
>
>
> Heikki Krogerus (6):
> driver core: platform: Remove duplicated device_remove_properties()
> call
> drivers core: Prepare support for multiple platform notifications
> ACPI / glue: Add acpi_platform_notify() function
> drivers: base: Introducing software nodes to the firmware node
> framework
> device property: Move device_add_properties() to swnode.c
> device property: Remove struct property_set
>
> .../ABI/testing/sysfs-devices-software_node | 10 +
> drivers/acpi/bus.c | 1 -
> drivers/acpi/glue.c | 21 +-
> drivers/acpi/internal.h | 1 -
> drivers/base/Makefile | 2 +-
> drivers/base/core.c | 34 +-
> drivers/base/platform.c | 1 -
> drivers/base/property.c | 511 +------------
> drivers/base/swnode.c | 678 ++++++++++++++++++
> include/linux/acpi.h | 10 +
> include/linux/property.h | 12 +
> 11 files changed, 768 insertions(+), 513 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-devices-software_node
> create mode 100644 drivers/base/swnode.c
>
>
All [1-6/6] applied, thanks!
prev parent reply other threads:[~2018-11-29 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 14:21 [PATCH v2 0/6] device property: Introducing software nodes Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 1/6] driver core: platform: Remove duplicated device_remove_properties() call Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 2/6] drivers core: Prepare support for multiple platform notifications Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 3/6] ACPI / glue: Add acpi_platform_notify() function Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 4/6] drivers: base: Introducing software nodes to the firmware node framework Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 5/6] device property: Move device_add_properties() to swnode.c Heikki Krogerus
2018-11-09 14:21 ` [PATCH v2 6/6] device property: Remove struct property_set Heikki Krogerus
2018-11-09 15:13 ` Andy Shevchenko
2019-07-06 17:48 ` Dmitry Torokhov
2018-11-09 15:14 ` [PATCH v2 0/6] device property: Introducing software nodes Andy Shevchenko
2018-11-14 12:45 ` Linus Walleij
2018-11-29 21:11 ` Rafael J. Wysocki [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=1859438.TcbhMcUUHz@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).