From: Rudraksha Gupta <guptarud@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Elliot Berman <quic_eberman@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Andrew Halaney <ahalaney@redhat.com>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH] firmware: qcom: scm: Allow devicetree-less probe
Date: Sat, 21 Sep 2024 00:45:19 -0700 [thread overview]
Message-ID: <547C76B7-8E41-44C3-8433-374B4E6BC341@gmail.com> (raw)
In-Reply-To: <fqdmcct5b5sxv3rpxiksmzpjbpcwmyuwpb5epjnhgpzxh344pp@pxggownwv44n>
> Which devicetrees? I assume that this mostly concerns arm32 machines,
> but I don't see if you have tested this on any of them. Also on some of
> those machines SCM require additional clocks, I don't see that being
> handled in the patch.
>
> If we are to manually instantiate SCM node, I'd prefer for it to be
> explicit, e.g. MSM8x60, create SCM device, using this-and-that clock.
I believe the consensus was that we will be using your one liner fix instead of this. If I misunderstood, please let me know and I will happily test this patch.
next prev parent reply other threads:[~2024-09-21 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 18:01 Elliot Berman
2024-09-20 18:41 ` Wasim Nazir
2024-09-20 19:09 ` Elliot Berman
2024-09-20 19:45 ` Stephan Gerhold
2024-09-20 20:23 ` Elliot Berman
2024-09-21 7:21 ` Dmitry Baryshkov
2024-09-21 7:45 ` Rudraksha Gupta [this message]
2024-09-21 15:12 ` Dmitry Baryshkov
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=547C76B7-8E41-44C3-8433-374B4E6BC341@gmail.com \
--to=guptarud@gmail.com \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_eberman@quicinc.com \
--cc=regressions@leemhuis.info \
/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
all inboxes | Powered by JetHome®