From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Brian Norris <briannorris@chromium.org>,
Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>,
Sumit Garg <sumit.garg@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
cros-qcom-dts-watchers@chromium.org,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sc7280: Drop aggre{1,2}_noc QOS clocks on Herobrine
Date: Tue, 3 Mar 2026 12:41:44 +0100 [thread overview]
Message-ID: <0b95b756-eb56-4b45-9c43-21379f1bdb58@oss.qualcomm.com> (raw)
In-Reply-To: <aaYBrQlaSSf4aWpz@google.com>
On 3/2/26 10:31 PM, Brian Norris wrote:
> Hi Konrad,
>
> On Tue, Feb 17, 2026 at 11:46:19AM +0100, Konrad Dybcio wrote:
>> On 1/9/26 1:33 AM, Brian Norris wrote:
>>> Hi Konrad,
>>>
>>> On Fri, Sep 12, 2025 at 12:37:29PM -0700, Brian Norris wrote:
>>>> On Fri, Sep 12, 2025 at 03:10:16PM +0200, Konrad Dybcio wrote:
>>>>> As I attempt to find a board that would boot with your sw stack,
>>>>> could I ask you to check if commenting any of the three writes in
>>>>>
>>>>> drivers/interconnect/qcom/icc-rpmh.c : qcom_icc_set_qos()
>>>>>
>>>>> specifically causes the crash?
>>>>>
>>>>> FWIW they're supposed to be independent so you don't have to test
>>>>> all possible combinations
>>>>
>>>> It seems as if any one of them will cause the crash. I had to comment
>>>> out all 3 to avoid crashing.
>>>
>>> I'm curious if you had any follow-up here. Are you still looking for an
>>> alternative to this patch?
>>
>> Sorry Brian, it seems like all the "ready to grab" firmware image links
>> for this platform are dead where I would normally look, which prevented
>> me from being able to poke at this..
>
> I'll say, I'm not really surprised. The firmware here is probably not in
> any maintained nor widely used state.
>
>> Would there happen to be another place where I can grab them from,
>> perhaps some CrOS CI?
>
> I don't really know of one right now. I expect the CI is not active.
>
> To speak practically here: there are likely no real users of this
> development board, and if I'm the only one actively trying to use it
> with upstream Linux as a development vehicle, I can simply carry this
> change locally. It's probably not worth a lot of people bending over
> backward for it, unless I'm wrong and there are more people using it. I
> was just hopeful that I could reduce some friction for myself, and the
> limited (possibly zero) population who might also run into problems
> here.
>
> Unless you really want to move forward, I'll move this from my mental
> back burner to cold storage :)
I'd really like to get to the bottom of this, especially since TF-A
support for this SoC lives on.. +Jorge & Sumit who are working on this
maybe you can repro/find the culprit
Konrad
next prev parent reply other threads:[~2026-03-03 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 22:55 [PATCH v2 1/2] dt-bindings: interconnect: qcom: make sc7280 aggre{1,2}-noc clocks optional Brian Norris
2025-08-25 22:55 ` [PATCH v2 2/2] arm64: dts: qcom: sc7280: Drop aggre{1,2}_noc QOS clocks on Herobrine Brian Norris
2025-09-02 12:02 ` Konrad Dybcio
2025-09-11 19:00 ` Brian Norris
2025-09-12 13:10 ` Konrad Dybcio
2025-09-12 19:37 ` Brian Norris
2026-01-09 0:33 ` Brian Norris
2026-02-17 10:46 ` Konrad Dybcio
2026-03-02 21:31 ` Brian Norris
2026-03-03 11:41 ` Konrad Dybcio [this message]
2025-08-29 16:19 ` [PATCH v2 1/2] dt-bindings: interconnect: qcom: make sc7280 aggre{1,2}-noc clocks optional Rob Herring (Arm)
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=0b95b756-eb56-4b45-9c43-21379f1bdb58@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=briannorris@chromium.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=djakov@kernel.org \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_okukatla@quicinc.com \
--cc=robh@kernel.org \
--cc=sumit.garg@oss.qualcomm.com \
/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