From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org
Cc: sudeep.holla@arm.com, lorenzo.pieralisi@arm.com,
mika.westerberg@linux.intel.com, rafael@kernel.org,
mark.rutland@arm.com, broonie@kernel.org, robh@kernel.org,
ahs3@redhat.com
Subject: [PATCH v5 00/13] ACPI graph support
Date: Thu, 16 Mar 2017 14:31:08 +0200 [thread overview]
Message-ID: <1489667481-28521-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
Hello everyone,
This is the fifth version of the ACPI graph support patchset.
The previous RFC version of the set is available here:
<URL:http://www.spinics.net/lists/linux-acpi/msg69547.html>
There are also v1, v2, v3 and v4 which can be found here:
<URL:http://www.spinics.net/lists/linux-acpi/msg71661.html>
<URL:http://www.spinics.net/lists/linux-acpi/msg71809.html>
<URL:http://www.spinics.net/lists/linux-acpi/msg72171.html>
<URL:http://www.spinics.net/lists/linux-acpi/msg72346.html>
This set contains patches written by Mika Westerberg and by myself. The
patchset brings support for graphs to ACPI. The functionality achieved by
these patches is very similar to what the Device tree provides: the port
and the endpoint concept are being employed. The patches make use of the
_DSD property and data extensions to achieve this. The fwnode interface is
extended by graph functionality; this way graph information originating
from both OF and ACPI may be accessed using the same interface, without
being aware of the underlying firmware interface.
The last patch of the set contains ASL documentation including an example.
The entire set may also be found here (on mediatree.git master, but it
also applies cleanly on linux-next):
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=acpi-graph>
The resulting fwnode graph interface has been tested using V4L2 async with
fwnode matching and smiapp and omap3isp drivers, with appropriate changes
to make use of the fwnode interface in drivers.
I'm additionally moving the firmware implementation specific code from
drivers/base/property.c to firmware specific locations. I'll post that
patchset soon. It'll be available here:
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=acpi-graph-cleaned>
The V4L2 patches can be found here. The fwnode graph interface is used by
the newly added V4L2 fwnode framework which replaces the V4L2 OF
framework, with equivalent functionality.
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=v4l2-acpi>
changes since v4:
- Use port and endpoint numbers in references. This is more reliable, as
the port and endpoint numbers are more stable than their location in the
data extension array. Because of this, also require the "endpoint"
property to be there. The documentation (the last patch) is changed
accordingly.
- Move dev_fwnode() implementation back to property.c where it was.
EXPORT_SYMBOL_GPL() it, and add a prototype in include/linux/property.h.
This removes the need for patches "[PATCH v4 10/16] irqchip/gic: Add
missing forward declaration for struct device" and "of: No need to
include linux/property.h, linux/fwnode.h is sufficient".
- Fix fwnode_graph_parse_endpoint() KernelDoc documentation.
- Add documentation for struct fwnode_endpoint.
- Removed patch "[PATCH v4 09/16] driver core: Arrange headers
alphabetically" from the set.
changes since v3:
- Rebase on current PM tree including 4.11-rc1 merge --- there were a few
conflicts.
changes since v2.2:
- Drop device_fwnode_handle() function in favour of moving the existing
dev_fwnode() function from drivers/base/property.c to linux/property.h
(now patch 12).
- Unmerge two unrelated patches accidentally merged between RFC v1 and
PATCH v1 of the series. The patch adding device_fwnode_handle() was
accidentally merged with "device property: Obtain device's fwnode
independently of FW type".
- Remove redundant forward declaration of struct device in
linux/property.h.
changes since v2:
- Include linux/property.h for property fwnode API in additional drivers
(current patch 11).
changes since v1:
- Fix a few checkpatch.pl warnings in Mika's patches (too long lines),
- remove the "endpoint" property specifying the endpoint id. The endpoint
id is a software concept and the index in the endpoint array can be used
instead if needed. The changes are in patches "device property: Add
support for fwnode endpoints" and "ACPI / DSD: Document references,
ports and endpoints" and
- add patch "irqchip/gic: Add missing forward declaration for
struct device" (patch 9) to fix compilation warning on arm64 caused
by "of: No need to include linux/property.h, linux/fwnode.h is
sufficient" (now patch 10)
changes since RFC v1:
- Rebased the set --- there were a few conflicts.
- Fixed a bug in ACPI graph parsing. (Thanks to Mika!)
- Remove one layer (the "ports" node) of the _DSD hierarchical data
structure. Change the documentation accordingly. Instead, rely on the
presence of "port" and "endpoint" properties to identify port and
endpoint nodes.
- Add a reference the DSD property rule document [1].
--
Kind regards,
Sakari
next reply other threads:[~2017-03-16 12:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 12:31 Sakari Ailus [this message]
2017-03-16 12:31 ` [PATCH v5 01/13] ACPI / property: Add possiblity to retrieve parent firmware node Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 02/13] device property: Add fwnode_get_parent() Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 03/13] ACPI / property: Add fwnode_get_next_child_node() Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 04/13] device property: Add fwnode_get_named_child_node() Sakari Ailus
[not found] ` <1489667481-28521-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-16 12:31 ` [PATCH v5 05/13] ACPI / property: Add support for remote endpoints Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 09/13] device property: Make dev_fwnode() public Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 11/13] of: Add nop implementation of of_get_next_parent() Sakari Ailus
2017-03-17 12:08 ` [PATCH v5.1 " Sakari Ailus
[not found] ` <1489752538-23543-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-24 9:28 ` Sakari Ailus
2017-03-24 15:45 ` [PATCH v5 00/13] ACPI graph support Mika Westerberg
2017-03-26 21:17 ` Sakari Ailus
[not found] ` <0b9104c2-4a3a-47db-ff1d-8f835fe3b567-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-27 11:03 ` Mika Westerberg
2017-03-16 12:31 ` [PATCH v5 06/13] device property: Add support for remote endpoints Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 07/13] device property: Add fwnode_handle_get() Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 08/13] of: Add of_fwnode_handle() to convert device nodes to fwnode_handle Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 10/13] device property: Add support for fwnode endpoints Sakari Ailus
2017-03-16 13:22 ` [PATCH v5.1 " Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 12/13] device property: Add fwnode_get_next_parent() Sakari Ailus
2017-03-24 9:21 ` [PATCH v5.1 " Sakari Ailus
2017-03-16 12:31 ` [PATCH v5 13/13] ACPI / DSD: Document references, ports and endpoints Sakari Ailus
[not found] ` <1489667481-28521-14-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-23 14:12 ` [PATCH v5.1 " 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=1489667481-28521-1-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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).