From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com, devicetree@vger.kernel.org,
"Rafael J.Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: [PATCH v2 0/4] Shovel firmware specific code to appropriate locations
Date: Wed, 23 Mar 2022 17:47:33 +0200 [thread overview]
Message-ID: <20220323154737.169483-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
This set moves the implementation of recently added device property API
functions to OF and ACPI frameworks, where the rest of such functionality
resides.
Compile tested.
The dependencies can be found in Rafael's devprop branch now.
changes since v1:
- Drop wrongly placed Depends-on: tag from the first patch.
- Drop IS_ENABLED(CONFIG_OF_ADDRESS) && is_of_node(fwnode) check (3rd
patch).
Sakari Ailus (4):
device property: Convert device_{dma_supported,get_dma_attr} to fwnode
ACPI: property: Move acpi_fwnode_device_get_match_data() up
device property: Add iomap to fwnode operations
device property: Add irq_get to fwnode operation
drivers/acpi/property.c | 36 +++++++++++++++++++++++++++++++----
drivers/base/property.c | 42 ++++++-----------------------------------
drivers/of/property.c | 30 +++++++++++++++++++++++++++++
include/linux/fwnode.h | 5 +++++
4 files changed, 73 insertions(+), 40 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-23 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 15:47 Sakari Ailus [this message]
2022-03-23 15:47 ` [PATCH v2 1/4] device property: Convert device_{dma_supported,get_dma_attr} to fwnode Sakari Ailus
2022-03-23 15:47 ` [PATCH v2 2/4] ACPI: property: Move acpi_fwnode_device_get_match_data() up Sakari Ailus
2022-03-23 15:47 ` [PATCH v2 3/4] device property: Add iomap to fwnode operations Sakari Ailus
2022-03-23 22:37 ` kernel test robot
2022-03-24 9:25 ` Andy Shevchenko
2022-03-30 7:44 ` Sakari Ailus
2022-03-23 15:47 ` [PATCH v2 4/4] device property: Add irq_get to fwnode operation Sakari Ailus
2022-03-23 16:20 ` [PATCH v2 0/4] Shovel firmware specific code to appropriate locations Andy Shevchenko
2022-03-30 11:01 ` Sakari Ailus
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=20220323154737.169483-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=frowand.list@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).