From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Luca Weiss <luca.weiss@fairphone.com>, linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Georgi Djakov <djakov@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/4] interconnect: qcom: Add SM6350 driver support
Date: Sat, 23 Apr 2022 21:50:37 +0200 [thread overview]
Message-ID: <0c5a6c77-afc6-9314-e238-28fde7eacc85@linaro.org> (raw)
In-Reply-To: <20220422144021.232993-4-luca.weiss@fairphone.com>
On 22/04/2022 16:40, Luca Weiss wrote:
> Add a driver that handles the different NoCs found on SM6350, generated
> from the downstream dtb.
>
> We're exluding ALC, IP0 and all _display nodes. ALC will not be voted
> from the kernel[1] and IP0 is handled by the clk-rpmh driver[2].
(...)
> +
> +static struct qcom_icc_desc sm6350_system_noc = {
> + .nodes = system_noc_nodes,
> + .num_nodes = ARRAY_SIZE(system_noc_nodes),
> + .bcms = system_noc_bcms,
> + .num_bcms = ARRAY_SIZE(system_noc_bcms),
Apply all the changes I did in this set:
https://lore.kernel.org/all/20220412102623.227607-1-krzysztof.kozlowski@linaro.org/
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-23 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 14:40 [PATCH 0/4] Add interconnect support for SM6350 Luca Weiss
2022-04-22 14:40 ` [PATCH 1/4] interconnect: qcom: icc-rpmh: Support child NoC device probe Luca Weiss
2022-04-22 14:40 ` [PATCH 2/4] dt-bindings: interconnect: Add Qualcomm SM6350 NoC support Luca Weiss
2022-04-23 19:55 ` Krzysztof Kozlowski
2022-04-22 14:40 ` [PATCH 3/4] interconnect: qcom: Add SM6350 driver support Luca Weiss
2022-04-23 19:50 ` Krzysztof Kozlowski [this message]
2022-04-22 14:40 ` [PATCH 4/4] arm64: dts: qcom: sm6350: Add interconnect support Luca Weiss
2022-04-27 21:43 ` 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=0c5a6c77-afc6-9314-e238-28fde7eacc85@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=djakov@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).