From: Stephen Boyd <swboyd@chromium.org>
To: David Dai <daidavid1@codeaurora.org>,
bjorn.andersson@linaro.org, georgi.djakov@linaro.org,
robh+dt@kernel.org
Cc: evgreen@google.com, ilina@codeaurora.org,
seansw@qti.qualcomm.com, elder@linaro.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: Update Qualcomm SDM845 DT bindings
Date: Wed, 24 Jul 2019 11:27:40 -0700 [thread overview]
Message-ID: <5d38a31d.1c69fb81.80992.0052@mx.google.com> (raw)
In-Reply-To: <8efd5c48-5d3a-97e1-1dec-6a9cdc4c8ef6@codeaurora.org>
Quoting David Dai (2019-07-24 10:22:57)
>
> The way that I view this is that the consumers consume both bandwidth
> and QoS from these physical NoC devices by getting some path between two
> endpoints on these different NoCs and applying some constraints. The NoC
> providers can accomplish that either by writing to MMIO spaces or by
> talking to some remote processor/hardware to tune its clock speed. The
> consumer doesn't interact with the RSCs directly, but can select a
> different bcm voter based on the endpoints that are associated with a
> particular bcm(apps or disp rsc). Each node(endpoints) will have its own
> BCM designation and an unique bcm voter.
Ok. I get it now. The MMIO nodes will be interconnect providers and
they'll know what RSCs they can use by exposing the same RSC "resource"
multiple times for each RSC that can be targeted? This is what the
postfix is with _DISP on your examples? Presumably there's an _APPS
version of the same prefixed endpoint in case the consumer wants to use
the APPS RSC instead of the DISP one, or maybe there's just no postfix
in this case because APPS is the "default".
next prev parent reply other threads:[~2019-07-24 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 20:32 [PATCH 0/2] Redefine interconnect provider DT nodes for SDM845 David Dai
2019-07-19 20:32 ` [PATCH 1/2] dt-bindings: interconnect: Update Qualcomm SDM845 DT bindings David Dai
2019-07-21 19:10 ` Bjorn Andersson
2019-07-23 14:42 ` Stephen Boyd
2019-07-23 21:48 ` David Dai
2019-07-24 14:18 ` Stephen Boyd
2019-07-24 17:22 ` David Dai
2019-07-24 18:27 ` Stephen Boyd [this message]
2019-07-24 20:42 ` David Dai
2019-07-19 20:32 ` [PATCH 2/2] arm64: dts: sdm845: Redefine interconnect provider DT nodes David Dai
2019-07-21 19:13 ` Bjorn Andersson
2019-07-23 18:24 ` David Dai
2019-12-12 19:36 ` Evan Green
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=5d38a31d.1c69fb81.80992.0052@mx.google.com \
--to=swboyd@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@google.com \
--cc=georgi.djakov@linaro.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=seansw@qti.qualcomm.com \
/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).