From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Georgi Djakov <djakov@kernel.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
Alex Elder <elder@linaro.org>, Taniya Das <quic_tdas@quicinc.com>,
Mike Tipton <quic_mdtipton@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH 0/2] interconnect: qcom: Remove IP0 resource
Date: Wed, 13 Apr 2022 19:32:55 -0700 [thread overview]
Message-ID: <YleH1+V9RCtMGege@ripper> (raw)
In-Reply-To: <20220412220033.1273607-1-swboyd@chromium.org>
On Tue 12 Apr 15:00 PDT 2022, Stephen Boyd wrote:
> These two patches remove the IP0 interconnect used for IPA because
> they're also present in the clk-rpmh driver. I see there are some more
> IP0 usages in the interconnect drivers, but I don't see a corresponding
> IPA clk in clk-rpmh, so I left these out. We can remove all of them if
> desired, but the sc7180 patch is most important to me as it fixes
> boot on my trogdor lazor device.
>
> Stephen Boyd (2):
> interconnect: qcom: sc7180: Drop IP0 interconnects
> interconnect: qcom: sdx55: Drop IP0 interconnects
>
> drivers/interconnect/qcom/sc7180.c | 21 ---------------------
> drivers/interconnect/qcom/sdx55.c | 21 ---------------------
> 2 files changed, 42 deletions(-)
>
> Cc: Alex Elder <elder@linaro.org>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Taniya Das <quic_tdas@quicinc.com>
> Cc: Mike Tipton <quic_mdtipton@quicinc.com>
> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> base-commit: 3123109284176b1532874591f7c81f3837bbdc17
> --
> https://chromeos.dev
>
next prev parent reply other threads:[~2022-04-14 2:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 22:00 [PATCH 0/2] interconnect: qcom: Remove IP0 resource Stephen Boyd
2022-04-12 22:00 ` [PATCH 1/2] interconnect: qcom: sc7180: Drop IP0 interconnects Stephen Boyd
2022-04-12 22:54 ` Alex Elder
2022-04-13 20:55 ` Doug Anderson
2022-04-13 21:02 ` Alex Elder
2022-04-13 23:14 ` Stephen Boyd
2022-04-14 0:59 ` Alex Elder
2022-04-12 22:00 ` [PATCH 2/2] interconnect: qcom: sdx55: " Stephen Boyd
2022-04-12 22:54 ` Alex Elder
2022-04-13 7:37 ` Manivannan Sadhasivam
2022-04-14 2:32 ` Bjorn Andersson [this message]
2022-04-15 0:58 ` [PATCH 3/2] arm64: dts: qcom: sc7180: Remove ipa interconnect node Stephen Boyd
2022-04-15 0:58 ` [PATCH 4/2] ARM: dts: qcom: sdx55: " Stephen Boyd
2022-04-15 20:11 ` Alex Elder
2022-05-04 17:21 ` (subset) " Bjorn Andersson
2022-04-15 0:58 ` [PATCH 5/2] dt-bindings: interconnect: Remove sc7180/sdx55 ipa compatibles Stephen Boyd
2022-04-15 20:15 ` Alex Elder
2022-04-18 19:48 ` Stephen Boyd
2022-05-16 22:16 ` Alex Elder
2022-05-19 17:48 ` Georgi Djakov
2022-04-15 20:11 ` [PATCH 3/2] arm64: dts: qcom: sc7180: Remove ipa interconnect node Alex Elder
2022-04-20 2:56 ` Bjorn Andersson
2022-04-22 7:01 ` Georgi Djakov
2022-04-22 20:34 ` Stephen Boyd
2022-05-04 17:21 ` (subset) " 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=YleH1+V9RCtMGege@ripper \
--to=bjorn.andersson@linaro.org \
--cc=djakov@kernel.org \
--cc=elder@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=patches@lists.linux.dev \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=swboyd@chromium.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).