From: Alex Elder <elder@linaro.org>
To: Doug Anderson <dianders@chromium.org>,
Stephen Boyd <swboyd@chromium.org>
Cc: Georgi Djakov <djakov@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>,
Mike Tipton <quic_mdtipton@quicinc.com>
Subject: Re: [PATCH 1/2] interconnect: qcom: sc7180: Drop IP0 interconnects
Date: Wed, 13 Apr 2022 16:02:00 -0500 [thread overview]
Message-ID: <d80ece40-fdd7-f304-3989-47ae152d5ac9@linaro.org> (raw)
In-Reply-To: <CAD=FV=UFbOhs0ggxDbVwKM_8x=ELT85zFd-Wk6dJ_M+Awz+Pxw@mail.gmail.com>
On 4/13/22 3:55 PM, Doug Anderson wrote:
> Hi,
>
> On Tue, Apr 12, 2022 at 4:20 PM Stephen Boyd <swboyd@chromium.org> wrote:
>>
>> @@ -519,8 +500,6 @@ static const struct of_device_id qnoc_of_match[] = {
>> .data = &sc7180_dc_noc},
>> { .compatible = "qcom,sc7180-gem-noc",
>> .data = &sc7180_gem_noc},
>> - { .compatible = "qcom,sc7180-ipa-virt",
>> - .data = &sc7180_ipa_virt},
>> { .compatible = "qcom,sc7180-mc-virt",
>> .data = &sc7180_mc_virt},
>> { .compatible = "qcom,sc7180-mmss-noc",
>
> I have no objection to ${SUBJECT} change landing and based on all your
> research and Alex's review/testing I think it's good to go.
>
> However, now that you're removed the driver that cared about
> "qcom,sc7180-ipa-virt", should we also be removing it from the
> `bindings/interconnect/qcom,rpmh.yaml` file and the `sc7180.dtsi`
> file? I think that removing it from _either_ the driver (like your
> patch here does) _or_ the sc7180.dtsi file would fix the bug, right?
> ...and then removing it from the yaml would just be cleanup...
That's a good point, I hadn't thought about that but you're right.
I think we were too pleased about identifying the problem and
proving it could happen (and cause a crash), so we didn't think
hard enough about this other piece.
Stephen, I think you should re-spin the series and add the
proper change to the binding. You can keep the tags I gave
before.
I've got a note to follow up with similar changes to other
platforms where the interconnect driver includes resource "IP0"
and will plan to do what Doug suggests there too.
-Alex
> -Doug
next prev parent reply other threads:[~2022-04-13 21:02 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 [this message]
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 ` [PATCH 0/2] interconnect: qcom: Remove IP0 resource Bjorn Andersson
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=d80ece40-fdd7-f304-3989-47ae152d5ac9@linaro.org \
--to=elder@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.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=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).