public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	patches@lists.linux.dev, linux-clk@vger.kernel.org,
	Amit Pundir <amit.pundir@linaro.org>,
	Taniya Das <quic_tdas@quicinc.com>
Subject: Re: [PATCH v3 1/2] clk: qcom: dispcc-sc7180: Only park display clks at init
Date: Mon, 2 Sep 2024 09:15:53 +0200	[thread overview]
Message-ID: <ZtVmKWTBtJiA53U0@hovoldconsulting.com> (raw)
In-Reply-To: <CAE-0n53rNuyXcVcqTBSgbNzuJzCBkaHE21dPNkMTrs=BCTkmPg@mail.gmail.com>

On Fri, Aug 30, 2024 at 03:29:22PM -0700, Stephen Boyd wrote:
> Quoting Stephen Boyd (2024-08-29 09:34:05)

> > It sounds like it's better to make the default always park at
> > registration time and special case the one or two places where that
> > isn't possible, i.e. USB because it has special rate requirements. So I
> > should just go back to v1 then and pile on the QUP patches.
> 
> I've done this now and I'll push out clk-fixes with the QUP patches.

I assumed you'd fix up all the other SoCs affected by this, but I only
saw fixes for sm8550, sm8650 and x1e80100 in your fixes branch.

Just sent a corresponding fix for sc8280xp, which I've confirmed also
needs this for QUP:

	https://lore.kernel.org/lkml/20240902070830.8535-1-johan+linaro@kernel.org/

But what about the sm8550 USB issue? Don't the other platforms also need
a corresponding fix (e.g. for when booting from USB)?

Johan

  reply	other threads:[~2024-09-02  7:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 17:17 [PATCH v3 0/2] clk: qcom: gcc-sm8550: Fix shared clk parking breakage Stephen Boyd
2024-08-28 17:17 ` [PATCH v3 1/2] clk: qcom: dispcc-sc7180: Only park display clks at init Stephen Boyd
2024-08-29 13:58   ` Johan Hovold
2024-08-29 15:32   ` Neil Armstrong
2024-08-29 16:34     ` Stephen Boyd
2024-08-30 22:29       ` Stephen Boyd
2024-09-02  7:15         ` Johan Hovold [this message]
2024-09-03 19:55           ` Stephen Boyd
2024-09-04  7:37             ` Johan Hovold
2024-08-28 17:17 ` [PATCH v3 2/2] clk: qcom: gcc-sm8550: Don't use shared clk_ops for QUPs Stephen Boyd
2024-08-29 14:02   ` Johan Hovold

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=ZtVmKWTBtJiA53U0@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=patches@lists.linux.dev \
    --cc=quic_tdas@quicinc.com \
    --cc=sboyd@kernel.org \
    --cc=swboyd@chromium.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