From: Georgi Djakov <georgi.djakov@linaro.org>
To: linux-pm@vger.kernel.org, bjorn.andersson@linaro.org
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
sibis@codeaurora.org, mka@chromium.org, dianders@chromium.org,
georgi.djakov@linaro.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/7] interconnect: Introduce xlate_extended()
Date: Thu, 3 Sep 2020 16:31:27 +0300 [thread overview]
Message-ID: <20200903133134.17201-1-georgi.djakov@linaro.org> (raw)
Currently the interconnect framework provides the xlate() callback for
mapping the endpoints from phandle arguments in DT. This is implemented
by the provider drivers. But the endpoints (or the path between the
endpoints) might have an additional attributes, which should be parsed
and populated. During previous discussions [1], it was suggested that
adding more and more DT properties will not scale very well. So instead
of adding DT properties, such data should be put into the 'interconnects'
arguments.
This patchset is introducing a new xlate_extended() callback, which
would allow the interconnect provider drivers to parse additional data
(such as path tags) and allow the framework to make use of them.
Thanks to Sibi for the preliminary feedback and testing this patchset
on the sc7180 platform.
The patchset is based on linux-next (next-20200903).
Changelog:
v3:
* Rebase and update both dts patches as Doug reported that i missed to
update the cells for the GPU and also other stuff changed in DT recently.
* Pick Rob's Reviewed-by
v2: http://lore.kernel.org/r/20200806163126.22667-1-georgi.djakov@linaro.org
* Add a patch to update the DT documentation, which i missed initially.
* Minor changes in commit text of patch 1/7. (Sibi)
* Remove a useless null check in patch 4/7. (Sibi)
* Print a warning if the number of DT args is higher than what we expect
in patch 3/7. (Matthias)
* Pick Reviewed-by/Tested-by tags.
* TODO: Replace tag IDs with macros in patches 5/7 and 7/7 when [2] lands.
v1: http://lore.kernel.org/r/20200723130942.28491-1-georgi.djakov@linaro.org
[1] https://lore.kernel.org/linux-devicetree/20200519185836.GA469006@bogus/
[2] https://lore.kernel.org/r/20200801033215.1440-2-mdtipton@codeaurora.org
Georgi Djakov (5):
interconnect: Introduce xlate_extended() callback
dt-bindings: interconnect: Document the support of optional path tag
interconnect: qcom: Implement xlate_extended() to parse tags
interconnect: qcom: sdm845: Replace xlate with xlate_extended
arm64: dts: qcom: sdm845: Increase the number of interconnect cells
Sibi Sankar (2):
interconnect: qcom: sc7180: Replace xlate with xlate_extended
arm64: dts: qcom: sc7180: Increase the number of interconnect cells
.../bindings/interconnect/interconnect.txt | 24 +-
arch/arm64/boot/dts/qcom/sc7180.dtsi | 218 +++++++++---------
arch/arm64/boot/dts/qcom/sdm845.dtsi | 48 ++--
drivers/interconnect/core.c | 73 ++++--
drivers/interconnect/qcom/icc-rpmh.c | 27 +++
drivers/interconnect/qcom/icc-rpmh.h | 1 +
drivers/interconnect/qcom/sc7180.c | 2 +-
drivers/interconnect/qcom/sdm845.c | 2 +-
include/linux/interconnect-provider.h | 17 +-
9 files changed, 251 insertions(+), 161 deletions(-)
next reply other threads:[~2020-09-03 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:31 Georgi Djakov [this message]
2020-09-03 13:31 ` [PATCH v3 1/7] interconnect: Introduce xlate_extended() callback Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 2/7] dt-bindings: interconnect: Document the support of optional path tag Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 3/7] interconnect: qcom: Implement xlate_extended() to parse tags Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 4/7] interconnect: qcom: sdm845: Replace xlate with xlate_extended Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 5/7] arm64: dts: qcom: sdm845: Increase the number of interconnect cells Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 6/7] interconnect: qcom: sc7180: Replace xlate with xlate_extended Georgi Djakov
2020-09-03 13:31 ` [PATCH v3 7/7] arm64: dts: qcom: sc7180: Increase the number of interconnect cells Georgi Djakov
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=20200903133134.17201-1-georgi.djakov@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.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).