From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, agross@kernel.org,
marijn.suijten@somainline.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom_scm: Add SM6375 compatible
Date: Tue, 21 Mar 2023 20:36:00 -0700 [thread overview]
Message-ID: <20230322033600.mkfeldd7oftpm32d@ripper> (raw)
In-Reply-To: <ca7a9708-8909-d663-d02f-240f8087aa9a@linaro.org>
On Tue, Mar 07, 2023 at 02:13:53PM +0100, Konrad Dybcio wrote:
>
>
> On 7.03.2023 02:22, Konrad Dybcio wrote:
> > While it was introduced in bindings, requiring a core clock, and added
> > into the DT, this compatible was apparently forgotten about on the driver
> > side of things. Fix it.
> >
> > Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> > ---
> > drivers/firmware/qcom_scm.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c
> > index 916a0c2fc903..2e8961c84b68 100644
> > --- a/drivers/firmware/qcom_scm.c
> > +++ b/drivers/firmware/qcom_scm.c
> > @@ -1494,6 +1494,7 @@ static const struct of_device_id qcom_scm_dt_match[] = {
> > },
> > { .compatible = "qcom,scm-msm8994" },
> > { .compatible = "qcom,scm-msm8996" },
> > + { .compatible = "qcom,scm-sm6375", .data = (void *)SCM_HAS_CORE_CLK },
> On a second thought, maybe the qcom,scm compatible could optionally consume
> all three clocks with schema guarding how many should be used, to prevent
> having to add nonsensical compatibles?
>
I've picked the patch, but your suggestion is not a bad idea. Back when
this scheme was decided there was no binding validation...
Regards,
Bjorn
> Konrad
> > { .compatible = "qcom,scm" },
> > {}
> > };
next prev parent reply other threads:[~2023-03-22 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 1:22 [PATCH] firmware: qcom_scm: Add SM6375 compatible Konrad Dybcio
2023-03-07 13:13 ` Konrad Dybcio
2023-03-22 3:36 ` Bjorn Andersson [this message]
2023-03-22 14:45 ` 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=20230322033600.mkfeldd7oftpm32d@ripper \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.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