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 v3 13/16] device property: Add support for fwnode endpoints
Date: Thu, 23 Feb 2017 18:19:33 +0200 [thread overview]
Message-ID: <1487866776-24578-14-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1487866776-24578-1-git-send-email-sakari.ailus@linux.intel.com>
Similar to OF endpoints, endpoint type nodes can be also supported on
ACPI. In order to make it possible for drivers to ignore the matter,
add a type for fwnode_endpoint and a function to parse them.
On ACPI, find the child node index instead of relying on the "endpoint"
property.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/base/property.c | 36 ++++++++++++++++++++++++++++++++++++
include/linux/fwnode.h | 6 ++++++
include/linux/property.h | 3 +++
3 files changed, 45 insertions(+)
diff --git a/drivers/base/property.c b/drivers/base/property.c
index cf8bc2f..a866e80 100644
--- a/drivers/base/property.c
+++ b/drivers/base/property.c
@@ -1239,3 +1239,39 @@ fwnode_graph_get_remote_endpoint(struct fwnode_handle *fwnode)
return endpoint;
}
EXPORT_SYMBOL_GPL(fwnode_graph_get_remote_endpoint);
+
+/*
+ * fwnode_graph_parse_endpoint() - parse common endpoint node properties
+ * @node: pointer to endpoint device_node
+ * @endpoint: pointer to the fwnode endpoint data structure
+ *
+ * The caller should hold a reference to @node.
+ */
+int fwnode_graph_parse_endpoint(struct fwnode_handle *fwnode,
+ struct fwnode_endpoint *endpoint)
+{
+ struct fwnode_handle *port_fwnode = fwnode_get_parent(fwnode);
+
+ memset(endpoint, 0, sizeof(*endpoint));
+
+ endpoint->local_fwnode = fwnode;
+
+ if (is_acpi_node(port_fwnode)) {
+ struct fwnode_handle *iter;
+
+ fwnode_property_read_u32(port_fwnode, "port", &endpoint->port);
+
+ for (iter = fwnode_get_next_child_node(port_fwnode, NULL);
+ iter != fwnode;
+ iter = fwnode_get_next_child_node(port_fwnode, iter))
+ endpoint->id++;
+ } else {
+ fwnode_property_read_u32(port_fwnode, "reg", &endpoint->port);
+ fwnode_property_read_u32(fwnode, "reg", &endpoint->id);
+ }
+
+ fwnode_handle_put(port_fwnode);
+
+ return 0;
+}
+EXPORT_SYMBOL(fwnode_graph_parse_endpoint);
diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h
index 8bd28ce..cb60f29 100644
--- a/include/linux/fwnode.h
+++ b/include/linux/fwnode.h
@@ -27,4 +27,10 @@ struct fwnode_handle {
struct fwnode_handle *secondary;
};
+struct fwnode_endpoint {
+ unsigned int port;
+ unsigned int id;
+ const struct fwnode_handle *local_fwnode;
+};
+
#endif
diff --git a/include/linux/property.h b/include/linux/property.h
index 09a75b1..df29a5f 100644
--- a/include/linux/property.h
+++ b/include/linux/property.h
@@ -279,4 +279,7 @@ struct fwnode_handle *fwnode_graph_get_remote_port(
struct fwnode_handle *fwnode_graph_get_remote_endpoint(
struct fwnode_handle *fwnode);
+int fwnode_graph_parse_endpoint(struct fwnode_handle *fwnode,
+ struct fwnode_endpoint *endpoint);
+
#endif /* _LINUX_PROPERTY_H_ */
--
2.7.4
next prev parent reply other threads:[~2017-02-23 16:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:19 [PATCH v3 00/16] ACPI graph support Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 01/16] ACPI / property: Add possiblity to retrieve parent firmware node Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 02/16] device property: Add fwnode_get_parent() Sakari Ailus
[not found] ` <1487866776-24578-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-02-23 16:19 ` [PATCH v3 03/16] ACPI / property: Add fwnode_get_next_child_node() Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 04/16] device property: Add fwnode_get_named_child_node() Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 05/16] ACPI / property: Add support for remote endpoints Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 15/16] device property: Add fwnode_get_next_parent() Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 06/16] device property: Add support for remote endpoints Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 07/16] device property: Add fwnode_handle_get() Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 08/16] of: Add of_fwnode_handle() to convert device nodes to fwnode_handle Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 09/16] driver core: Arrange headers alphabetically Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 10/16] irqchip/gic: Add missing forward declaration for struct device Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 11/16] of: No need to include linux/property.h, linux/fwnode.h is sufficient Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 12/16] device property: Move dev_fwnode() to linux/property.h Sakari Ailus
2017-02-23 16:19 ` Sakari Ailus [this message]
2017-02-23 16:19 ` [PATCH v3 14/16] of: Add nop implementation of of_get_next_parent() Sakari Ailus
2017-02-23 16:19 ` [PATCH v3 16/16] ACPI / DSD: Document references, ports and endpoints Sakari Ailus
2017-02-24 9:13 ` [PATCH v3 00/16] ACPI graph support 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=1487866776-24578-14-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).