From: Georgi Djakov <djakov@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abel.vesa@linaro.org>
Subject: Re: [PATCH v2 0/2] interconnect: qcom: Introduce support for SM8650
Date: Mon, 27 Nov 2023 16:08:37 +0200 [thread overview]
Message-ID: <7fbe4090-94cd-4aaf-98b6-07f2a089d51a@kernel.org> (raw)
In-Reply-To: <20231123-topic-sm8650-upstream-interconnect-v2-0-7e050874f59b@linaro.org>
On 23.11.23 15:32, Neil Armstrong wrote:
> This covers the RPMh Network-On-Chip Interconnect bindings
> and driver for the interconnect framework.
Thanks Neil!
> As reported for earlier Interconnect drivers, the IDs
> for multi-rsc voting has been removed from this driver
> so the proper solution can be developed without having
> to remove entries later on.
>
> To easy Bjorn into merging the DT bits, would it be possible
> to have an immutable branch with bindings shared with Bjorn once
> this patchset have been properly reviewed and accepted ?
Hi Bjorn,
Here is a stable branch with the DT bindings header that might be needed
for SM8650 dts patches.
https://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git/log/?h=icc-sm8650
Thanks,
Georgi
>
> Dependencies: None
>
> For convenience, a regularly refreshed linux-next based git tree containing
> all the SM8650 related work is available at:
> https://git.codelinaro.org/neil.armstrong/linux/-/tree/topic/sm8650/upstream/integ
>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
> Changes in v2:
> - Collected Reviewed-by
> - Moved required block in bindings as requested by Krzysztof
> - Link to v1: https://lore.kernel.org/r/20231025-topic-sm8650-upstream-interconnect-v1-0-b7277e03aa3d@linaro.org
next prev parent reply other threads:[~2023-11-27 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 13:32 [PATCH v2 0/2] interconnect: qcom: Introduce support for SM8650 Neil Armstrong
2023-11-23 13:32 ` [PATCH v2 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip Interconnect in Qualcomm SM8650 SoC Neil Armstrong
2023-11-23 13:32 ` [PATCH v2 2/2] interconnect: qcom: introduce RPMh Network-On-Chip Interconnect on " Neil Armstrong
2023-11-27 14:08 ` Georgi Djakov [this message]
2023-11-27 14:14 ` [PATCH v2 0/2] interconnect: qcom: Introduce support for SM8650 Neil Armstrong
2023-12-08 3:19 ` Bjorn Andersson
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=7fbe4090-94cd-4aaf-98b6-07f2a089d51a@kernel.org \
--to=djakov@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.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).