Re: [PATCH 2/3] device property: Move fwnode graph ops to firmware specific locations
From: Mika Westerberg <hidden>
Date: 2017-03-27 11:52:00
Also in:
linux-acpi
On Fri, Mar 24, 2017 at 01:03:51PM +0200, Sakari Ailus wrote:
quoted hunk
const struct fwnode_operations acpi_fwnode_ops = { .property_present = acpi_fwnode_property_present, .property_read_int_array = acpi_fwnode_property_read_int_array,@@ -1193,4 +1248,9 @@ const struct fwnode_operations acpi_fwnode_ops = { .get_parent = acpi_fwnode_get_parent, .get_next_child_node = acpi_get_next_subnode, .get_named_child_node = acpi_fwnode_get_named_child_node, + .graph_get_next_endpoint = acpi_fwnode_graph_get_next_endpoint, + .graph_get_remote_endpoint = acpi_fwnode_graph_get_remote_endpoint, + .graph_get_remote_port = acpi_fwnode_graph_get_remote_port, + .graph_get_remote_port_parent = acpi_fwnode_graph_get_remote_port_parent, + .graph_parse_endpoint = acpi_fwnode_graph_parse_endpoint, };
Not sure if it is possible but it would be nice to have a single primitive implementation specific graph callback and then build everything else on top of that in generic code. Here you have 5 callbacks just for graph support. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html