[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180925181735.GA28385@bogus>
Date: Tue, 25 Sep 2018 13:17:35 -0500
From: Rob Herring <robh@...nel.org>
To: Georgi Djakov <georgi.djakov@...aro.org>
Cc: linux-pm@...r.kernel.org, gregkh@...uxfoundation.org,
rjw@...ysocki.net, mturquette@...libre.com, khilman@...libre.com,
vincent.guittot@...aro.org, skannan@...eaurora.org,
bjorn.andersson@...aro.org, amit.kucheria@...aro.org,
seansw@....qualcomm.com, daidavid1@...eaurora.org,
evgreen@...omium.org, mark.rutland@....com,
lorenzo.pieralisi@....com, abailon@...libre.com,
maxime.ripard@...tlin.com, arnd@...db.de,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v9 5/8] interconnect: qcom: Add RPM communication
On Fri, Aug 31, 2018 at 05:01:48PM +0300, Georgi Djakov wrote:
> On some Qualcomm SoCs, there is a remote processor, which controls some of
> the Network-On-Chip interconnect resources. Other CPUs express their needs
> by communicating with this processor. Add a driver to handle communication
> with this remote processor.
I don't think you should have a binding nor a separate driver for this.
It's not actually an interconnect provider, so it doesn't belong in
bindings/interconnect. And it just looks like abuse of DT to instantiate
some driver.
All the driver amounts to is a 1 function wrapper for RPM_KEY_BW
messages. Can't this be part of the parent?
Rob
Powered by blists - more mailing lists