public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ansuel Smith <ansuelsmth@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom_scm: Add compatible for ipq806x
Date: Sun, 17 Apr 2022 17:57:28 +0200	[thread overview]
Message-ID: <625c38ea.1c69fb81.17696.b763@mx.google.com> (raw)
In-Reply-To: <CAA8EJprEYgWTp5KJ1TSGC8EKbuw1XP+jz7D5BaCP0rEsEPVsuQ@mail.gmail.com>

On Wed, Apr 13, 2022 at 10:03:59AM +0300, Dmitry Baryshkov wrote:
> On Wed, 13 Apr 2022 at 05:38, Bjorn Andersson
> <bjorn.andersson@linaro.org> wrote:
> >
> > On Thu 10 Mar 16:07 CST 2022, Ansuel Smith wrote:
> >
> > > Add compatible for ipq806x. Just like ipq4019, ipq806x doesn't require
> > > Core, Iface or Bus clock.
> > >
> > > Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> > > ---
> > >  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 7db8066b19fd..7348c5894821 100644
> > > --- a/drivers/firmware/qcom_scm.c
> > > +++ b/drivers/firmware/qcom_scm.c
> > > @@ -1338,6 +1338,7 @@ static const struct of_device_id qcom_scm_dt_match[] = {
> > >                                                            SCM_HAS_IFACE_CLK |
> > >                                                            SCM_HAS_BUS_CLK)
> > >       },
> > > +     { .compatible = "qcom,scm-ipq806x" },
> >
> > If you in your dt do:
> >
> >         compatible = "qcom,scm-ipq806x", "qcom,scm";
> >
> > Then we don't need to update the driver for each platform, only the DT
> > binding.
> >
> > And if we some day need to quirk something off qcom,scm-ipq806x we have
> > that option.
> 
> I suppose that ipq806x might need SCM_HAS_CORE_CLK. Or, more likely,
> an interconnect vote, once we have interconnect drivers for
> ipq/apq8064 platforms.
> 

From an old source I found that scm core clock comes from dfab_clk
(DAYTONA_FABRIC). I notice there is an interconnect driver for rpm (bw
is handled by rpm on ipq/apq8064) but why this should be related to scm
core clk? To handle the clock voter stuff? (I assume a voter logic is
not supported upstream)

But it does seems an interesting project adding interconnect support for
ipq8064 also considering I have a fab scaling driver present from ages
that I hane no idea how to handle.

> >
> > Thanks,
> > Bjorn
> >
> > >       { .compatible = "qcom,scm-ipq4019" },
> > >       { .compatible = "qcom,scm-mdm9607", .data = (void *)(SCM_HAS_CORE_CLK |
> > >                                                            SCM_HAS_IFACE_CLK |
> > > --
> > > 2.34.1
> > >
> 
> 
> 
> -- 
> With best wishes
> Dmitry

-- 
	Ansuel

      reply	other threads:[~2022-04-17 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 22:07 [PATCH] firmware: qcom_scm: Add compatible for ipq806x Ansuel Smith
2022-04-13  2:38 ` Bjorn Andersson
2022-04-13  7:03   ` Dmitry Baryshkov
2022-04-17 15:57     ` Ansuel Smith [this message]

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=625c38ea.1c69fb81.17696.b763@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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