From: Christian Marangi <ansuelsmth@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Ilia Lin <ilia.lin@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>,
Yassine Oudjana <y.oudjana@protonmail.com>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: opp: opp-v2-kryo-cpu: enlarge opp-supported-hw maximum
Date: Sun, 22 Jan 2023 19:04:53 +0100 [thread overview]
Message-ID: <63cd7cda.050a0220.53454.5a1b@mx.google.com> (raw)
In-Reply-To: <CAA8EJpp1c=sC0d_G1eSuOzJbjusW86zHezfwY3JRH=EBp7tNmA@mail.gmail.com>
On Sun, Jan 22, 2023 at 07:59:42PM +0200, Dmitry Baryshkov wrote:
> On Sun, 22 Jan 2023 at 19:46, Christian Marangi <ansuelsmth@gmail.com> wrote:
> >
> > Enlarge opp-supported-hw maximum value. In recent SoC we started
> > matching more bit and we currently match mask of 112. The old maximum of
> > 7 was good for old SoC that didn't had complex id, but now this is
> > limiting and we need to enlarge it to support more variants.
> >
> > Document all the various mask that can be used and limit them to only
> > reasonable values instead of using a generic maximum limit.
> >
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> > ---
> > .../bindings/opp/opp-v2-kryo-cpu.yaml | 20 +++++++++++++++++--
> > 1 file changed, 18 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml b/Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml
> > index b4947b326773..908cb0d7695a 100644
> > --- a/Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml
> > +++ b/Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml
> > @@ -50,12 +50,28 @@ patternProperties:
> > opp-supported-hw:
> > description: |
> > A single 32 bit bitmap value, representing compatible HW.
> > - Bitmap:
> > + Bitmap for MSM8996 format:
> > 0: MSM8996, speedbin 0
> > 1: MSM8996, speedbin 1
> > 2: MSM8996, speedbin 2
> > 3-31: unused
> > - maximum: 0x7
> > +
> > + Bitmap for MSM8996 later revision format:
> > + 0: MSM8996, speedbin 0
> > + 1: MSM8996, speedbin 1
> > + 2: MSM8996, speedbin 2
> > + 3: always set
>
> This is used for speedbin 3
>
Is it right that 4 bit speedbin is only introduced later? Cause looking
at the current opp-supported-hw for MSM8996SG and MSM8996 originally
(and based on what this Documentation say) there were only 3 bit and
then they started using a 4th bit. Just asking if it's ok to keep the
bitmap split or i should just merge it.
> > + 4-31: unused
> > +
> > + Bitmap for MSM8996SG format (speedbin shifted of 4 left):
> > + 0-3: unused
> > + 4: MSM8996SG, speedbin 0
> > + 5: MSM8996SG, speedbin 1
> > + 6: MSM8996SG, speedbin 2
> > + 7-31: unused
> > + enum: [0x1, 0x2, 0x3, 0x4, 0x7,
> > + 0x9, 0xd, 0xe, 0xf,
> > + 0x10, 0x20, 0x30, 0x70]
> >
> > clock-latency-ns: true
> >
> > --
> > 2.38.1
> >
--
Ansuel
next prev parent reply other threads:[~2023-01-22 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 17:45 [PATCH v2 1/2] dt-bindings: cpufreq: qcom-cpufreq-nvmem: make cpr bindings optional Christian Marangi
2023-01-22 17:45 ` [PATCH v2 2/2] dt-bindings: opp: opp-v2-kryo-cpu: enlarge opp-supported-hw maximum Christian Marangi
2023-01-22 17:59 ` Dmitry Baryshkov
2023-01-22 18:04 ` Christian Marangi [this message]
2023-01-22 19:15 ` Dmitry Baryshkov
2023-01-22 19:19 ` Christian Marangi
2023-01-23 13:49 ` Rob Herring
2023-01-23 13:49 ` [PATCH v2 1/2] dt-bindings: cpufreq: qcom-cpufreq-nvmem: make cpr bindings optional Rob Herring
2023-01-23 13:52 ` Christian Marangi
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=63cd7cda.050a0220.53454.5a1b@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=y.oudjana@protonmail.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;
as well as URLs for NNTP newsgroup(s).