[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170629213247.qk54ocaomcz42gn7@rob-hp-laptop>
Date: Thu, 29 Jun 2017 16:32:47 -0500
From: Rob Herring <robh@...nel.org>
To: Georgi Djakov <georgi.djakov@...aro.org>
Cc: linux-pm@...r.kernel.org, rjw@...ysocki.net, khilman@...libre.com,
mturquette@...libre.com, gregkh@...uxfoundation.org,
vincent.guittot@...aro.org, skannan@...eaurora.org,
sboyd@...eaurora.org, andy.gross@...aro.org,
seansw@....qualcomm.com, davidai@...cinc.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v1 3/3] dt-bindings: Interconnect device-tree bindings
draft
On Tue, Jun 27, 2017 at 08:49:03PM +0300, Georgi Djakov wrote:
> The interconnect API is not yet using DT bindings for expressing
> the relations between the API consumers and providers. This is
> posted a separate patch as it needs further discussions on how
> to represent this with DT.
I would recommend continuing to sort out how this works within the
kernel before fixing things in DT. Something like this needs to be a
core binding in the DT spec.
Also, you should CC some ARM, Ltd. folks like Mark R and Lorenzo.
There's been some discussion in the past how to describe the DMA master
side of the bus topology.
Rob
Powered by blists - more mailing lists