Linux-Clk Archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Marc Gonzalez <mgonzalez@freebox.fr>,
	Bjorn Andersson <andersson@kernel.org>,
	Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: MSM <linux-arm-msm@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Vikash Garodia <quic_vgarodia@quicinc.com>,
	Douglas Anderson <dianders@chromium.org>,
	Pierre-Hugues Husson <phhusson@freebox.fr>,
	Arnaud Vrac <avrac@freebox.fr>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v3] clk: qcom: mmcc-msm8998: fix venus clock issue
Date: Tue, 30 Apr 2024 11:04:27 +0100	[thread overview]
Message-ID: <e2aea885-99d5-4aa3-beb0-4dfb80553d6a@linaro.org> (raw)
In-Reply-To: <b4bd6bb1-b1c3-482c-9140-24c8f9f14bff@linaro.org>

On 30/04/2024 11:00, Konrad Dybcio wrote:
> ??????????
> 
> That's what the kernel is trying to do as part of the cleanup.. Either
> this clock is always-on or held through some hardware vote. Or the status
> bit is wrong.
> 
> Just leave it be.
> 
> Konrad

That's not different to what I just said but, thanks for restating it.

---
bod

      reply	other threads:[~2024-04-30 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 15:07 [PATCH v3] clk: qcom: mmcc-msm8998: fix venus clock issue Marc Gonzalez
2024-04-26 21:00 ` Jeffrey Hugo
2024-04-27 19:34 ` Bjorn Andersson
2024-04-29 13:45   ` Marc Gonzalez
2024-04-29 14:39     ` Bryan O'Donoghue
2024-04-29 14:52       ` Konrad Dybcio
2024-04-29 15:04         ` Bryan O'Donoghue
2024-04-30 10:00           ` Konrad Dybcio
2024-04-30 10:04             ` Bryan O'Donoghue [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=e2aea885-99d5-4aa3-beb0-4dfb80553d6a@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andersson@kernel.org \
    --cc=avrac@freebox.fr \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mgonzalez@freebox.fr \
    --cc=mturquette@baylibre.com \
    --cc=phhusson@freebox.fr \
    --cc=quic_jhugo@quicinc.com \
    --cc=quic_vgarodia@quicinc.com \
    --cc=sboyd@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 read-only IMAP folder(s) and NNTP newsgroup(s).