devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yassine Oudjana <yassine.oudjana@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Yassine Oudjana <yassine.oudjana@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Ilia Lin <ilia.lin@kernel.org>, Viresh Kumar <vireshk@kernel.org>,
	Nishanth Menon <nm@ti.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Loic Poulain <loic.poulain@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/9] Add support for MSM8996 Pro
Date: Sat, 16 Apr 2022 06:44:31 +0400	[thread overview]
Message-ID: <20220416024431.82110-1-y.oudjana@protonmail.com> (raw)
In-Reply-To: <20220412191750.0C00DC385A1@smtp.kernel.org>

From: Yassine Oudjana <yassine.oudjana@gmail.com>

On Tue, 12 Apr 2022 12:17:48 -0700, Stephen Boyd wrote:
> Quoting Yassine Oudjana (2022-04-08 21:01:27)
> > MSM8996 Pro (also known as MSM8996SG) is a newer revision of MSM8996
> > with different CPU/CBF/GPU frequencies and CPR parameters. Its CBF clock
> > also has a different divisor.
> >
> > This series handles the difference in the CBF clock and adds a new DTSI for
> > MSM8996 Pro with CPU and GPU OPPs. It also removes reading msm-id from SMEM
> > in qcom-cpufreq-nvmem as it becomes no longer necessary with the introduction.
> > of a separate device tree. Separating MSM8996 and MSM8996 Pro will help with
> > implementing CBF scaling and CPR; as they have different CPR parameters
> > and CPU:CBF OPP mapping which is difficult to implement in the same cluster
> > OPP tables.
>
> Some of the patches are encrypted? Please resend.

Sorry about that, I had some issues with the SMTP bridge I use with Protonmail
and had to use the web client, which apparently did something funny.

I'll resend through a different provider with git send-email.


       reply	other threads:[~2022-04-16  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220412191750.0C00DC385A1@smtp.kernel.org>
2022-04-16  2:44 ` Yassine Oudjana [this message]
2022-04-09  4:01 [PATCH v2 0/9] Add support for MSM8996 Pro Yassine Oudjana

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=20220416024431.82110-1-y.oudjana@protonmail.com \
    --to=yassine.oudjana@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=ilia.lin@kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=nm@ti.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).