From: Georgi Djakov <georgi.djakov@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org,
rjw@rjwysocki.net, mturquette@baylibre.com, khilman@baylibre.com,
vincent.guittot@linaro.org, skannan@codeaurora.org,
bjorn.andersson@linaro.org, amit.kucheria@linaro.org,
seansw@qti.qualcomm.com, daidavid1@codeaurora.org,
evgreen@chromium.org, mark.rutland@arm.com,
lorenzo.pieralisi@arm.com, abailon@baylibre.com,
maxime.ripard@bootlin.com, arnd@arndb.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Krishna Sitaraman <ksitaraman@nvidia.com>
Subject: Re: [PATCH v9 2/8] dt-bindings: Introduce interconnect binding
Date: Tue, 27 Nov 2018 20:05:39 +0200 [thread overview]
Message-ID: <bfed1f52-1544-8491-9f0f-b46c2787b45e@linaro.org> (raw)
In-Reply-To: <b67253fb-d86d-2ddd-6c30-0833d6ed62ad@linaro.org>
Hi Rob,
On 9/26/18 17:42, Georgi Djakov wrote:
> Hi Rob,
>
> Thanks for the comments!
>
> On 09/25/2018 09:02 PM, Rob Herring wrote:
>> On Fri, Aug 31, 2018 at 05:01:45PM +0300, Georgi Djakov wrote:
>>> This binding is intended to represent the relations between the interconnect
>>> controllers (providers) and consumer device nodes. It will allow creating links
>>> between consumers and interconnect paths (exposed by interconnect providers).
>>
>> As I mentioned in person, I want to see other SoC families using this
>> before accepting. They don't have to be ready for upstream, but WIP
>> patches or even just a "yes, this works for us and we're going to use
>> this binding on X".
Patches for the iMX7ULP platform are already available [1]. Thanks
Alexandre Bailon!
The interconnect API seems to be also a good fit for Nvidia SoCs. There
is an ongoing discussion about implementing an interconnect provider
driver for Tegra [2]. Thanks Thierry and Krishna!
In addition of the above, i also checked privately with a few other SoC
maintainers and made them aware of these patches. Some are not ready for
upstream yet, but the feedback was positive and i expect more SoCs to
make use of this in the future.
BR,
Georgi
[1] https://lkml.org/lkml/2018/11/17/368
[2] https://marc.info/?t=154056181900001&r=1&w=2
> Other than the 3 Qualcomm SoCs (msm8916, msm8996, sdm845) that are
> currently using this binding, there is ongoing work from at least two
> other vendors that would be using this same binding. I will check on
> what is their progress so far.
>
>> Also, I think the QCom GPU use of this should be fully sorted out. Or
>> more generically how this fits into OPP binding which seems to be never
>> ending extended...
>
> I see this as a further step. It could be OPP binding which include
> bandwidth values or some separate DT property. Jordan has already
> proposed something, do you have any initial comments on that?
>
> BR,
> Georgi
>
next prev parent reply other threads:[~2018-11-27 18:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 14:01 [PATCH v9 0/8] Introduce on-chip interconnect API Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 1/8] interconnect: Add generic " Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 2/8] dt-bindings: Introduce interconnect binding Georgi Djakov
2018-09-25 18:02 ` Rob Herring
2018-09-26 14:34 ` Jordan Crouse
2018-10-01 20:56 ` Saravana Kannan
2018-10-01 21:26 ` Jordan Crouse
2018-10-01 21:51 ` Saravana Kannan
2018-09-26 14:42 ` Georgi Djakov
2018-09-26 14:48 ` Sudeep Holla
2018-09-26 15:03 ` Georgi Djakov
2018-10-01 23:49 ` Saravana Kannan
2018-10-02 11:17 ` Sudeep Holla
2018-10-02 18:56 ` Saravana Kannan
2018-10-03 9:33 ` Sudeep Holla
2018-10-03 18:06 ` Saravana Kannan
2018-10-10 15:02 ` Sudeep Holla
2018-11-27 18:05 ` Georgi Djakov [this message]
2018-08-31 14:01 ` [PATCH v9 3/8] interconnect: Allow endpoints translation via DT Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 4/8] interconnect: Add debugfs support Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 5/8] interconnect: qcom: Add RPM communication Georgi Djakov
2018-09-25 18:17 ` Rob Herring
2018-10-02 11:02 ` Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 6/8] dt-bindings: interconnect: Document qcom,msm8916 NoC bindings Georgi Djakov
2018-09-25 18:22 ` Rob Herring
2018-10-02 11:02 ` Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 7/8] interconnect: qcom: Add msm8916 interconnect provider driver Georgi Djakov
2018-08-31 14:01 ` [PATCH v9 8/8] MAINTAINERS: add a maintainer for the interconnect API Georgi Djakov
2018-09-04 10:24 ` [PATCH v9 0/8] Introduce on-chip " Amit Kucheria
2018-09-04 23:36 ` Stephen Rothwell
2018-09-05 14:50 ` Georgi Djakov
2018-09-05 15:05 ` Stephen Rothwell
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=bfed1f52-1544-8491-9f0f-b46c2787b45e@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=abailon@baylibre.com \
--cc=amit.kucheria@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=ksitaraman@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=seansw@qti.qualcomm.com \
--cc=skannan@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.guittot@linaro.org \
/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).