From: Shawn Guo <shawn.guo@linaro.org>
To: Vincent Knecht <vincent.knecht@mailoo.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sivaprakash Murugesan <sivaprak@codeaurora.org>,
Benjamin Li <benl@squareup.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add MSM8939 APCS/A53PLL clock support
Date: Fri, 9 Jul 2021 10:13:35 +0800 [thread overview]
Message-ID: <20210709021334.GB11342@dragon> (raw)
In-Reply-To: <c780e9df1b2f1eef6af1c9a10662f5a1952a1fae.camel@mailoo.org>
On Wed, Jul 07, 2021 at 11:34:19PM +0200, Vincent Knecht wrote:
> Le dimanche 04 juillet 2021 à 10:40 +0800, Shawn Guo a écrit :
> > This series adds MSM8939 APCS/A53PLL clock support. Most outstanding
> > thing about MSM8939 is that it integrates 3 APCS instances, for Cluster0
> > (little cores), Cluster1 (big cores) and CCI (Cache Coherent Interconnect)
> > respectively.
> >
> > Changes for v2:
> > - Reword the commit log of first patch as suggested by Stephen.
> > - Drop 'clock-output-names' bindings and use @unit-address to get unique
> > a53pll/mux clock names.
> > - Use 'operating-points-v2' bindings to pass frequency table via OPP, so
> > that we can use one single compatible for all 3 MSM8939 a53pll.
> >
> > Shawn Guo (4):
> > clk: qcom: apcs-msm8916: Flag a53mux instead of a53pll as critical
> > clk: qcom: a53pll/mux: Use unique clock name
> > dt-bindings: clock: Update qcom,a53pll bindings for MSM8939 support
> > clk: qcom: a53-pll: Add MSM8939 a53pll support
> >
> > .../bindings/clock/qcom,a53pll.yaml | 3 +
> > drivers/clk/qcom/a53-pll.c | 68 ++++++++++++++++++-
> > drivers/clk/qcom/apcs-msm8916.c | 10 ++-
> > 3 files changed, 76 insertions(+), 5 deletions(-)
>
> Hello,
>
> would you have a msm8939 dtsi/dts reference file working with all recent
> contributions for this SoC ?
Yes, the dts will be posted once it's ready for public review.
Shawn
> We the msm8939-focused PostmarketOS gang would be happy to boot our devices
> and test patches but we're not able to boot anything more recent that 5.9...
next prev parent reply other threads:[~2021-07-09 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 2:40 [PATCH v2 0/4] Add MSM8939 APCS/A53PLL clock support Shawn Guo
2021-07-04 2:40 ` [PATCH v2 1/4] clk: qcom: apcs-msm8916: Flag a53mux instead of a53pll as critical Shawn Guo
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 2/4] clk: qcom: a53pll/mux: Use unique clock name Shawn Guo
2021-07-10 5:17 ` Bjorn Andersson
2021-07-10 7:34 ` Shawn Guo
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 3/4] dt-bindings: clock: Update qcom,a53pll bindings for MSM8939 support Shawn Guo
2021-07-12 14:58 ` Rob Herring
2021-08-06 1:53 ` Stephen Boyd
2021-07-04 2:40 ` [PATCH v2 4/4] clk: qcom: a53-pll: Add MSM8939 a53pll support Shawn Guo
2021-08-06 1:53 ` Stephen Boyd
2021-07-07 21:34 ` [PATCH v2 0/4] Add MSM8939 APCS/A53PLL clock support Vincent Knecht
2021-07-09 2:13 ` Shawn Guo [this message]
2021-08-04 8:47 ` Shawn Guo
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=20210709021334.GB11342@dragon \
--to=shawn.guo@linaro.org \
--cc=benl@squareup.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@codeaurora.org \
--cc=vincent.knecht@mailoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.