Re: [PATCH 0/6] of_graph_get_remote_endpoint()

Hi Rob > This looks okay, but I think we need to be improving the graph api at > a higher level. Each user seems to be doing too much open coding of > walking of the graph. The user typically just wants the remote node > parent of a given port and endpoint number. Why does the user walk the >

Re: [PATCH 0/6] of_graph_get_remote_endpoint()

Hi Rob > This looks okay, but I think we need to be improving the graph api at > a higher level. Each user seems to be doing too much open coding of > walking of the graph. The user typically just wants the remote node > parent of a given port and endpoint number. Why does the user walk the >

Re: [PATCH 0/6] of_graph_get_remote_endpoint()

On Thu, Jan 19, 2017 at 12:31 AM, Kuninori Morimoto wrote: > > > > Hi Rob > > Now many driver is getting remote-endpoint by manually, > but we should use same method to get same result IMO. > Thus this patch adds of_graph_get_remote_endpoint() for this purpose. >

Re: [PATCH 0/6] of_graph_get_remote_endpoint()

On Thu, Jan 19, 2017 at 12:31 AM, Kuninori Morimoto wrote: > > > > Hi Rob > > Now many driver is getting remote-endpoint by manually, > but we should use same method to get same result IMO. > Thus this patch adds of_graph_get_remote_endpoint() for this purpose. > And use it on several drivers

[PATCH 0/6] of_graph_get_remote_endpoint()

Hi Rob Now many driver is getting remote-endpoint by manually, but we should use same method to get same result IMO. Thus this patch adds of_graph_get_remote_endpoint() for this purpose. And use it on several drivers Kuninori Morimoto (6): of_graph: add of_graph_get_remote_endpoint()

[PATCH 0/6] of_graph_get_remote_endpoint()

Hi Rob Now many driver is getting remote-endpoint by manually, but we should use same method to get same result IMO. Thus this patch adds of_graph_get_remote_endpoint() for this purpose. And use it on several drivers Kuninori Morimoto (6): of_graph: add of_graph_get_remote_endpoint()