From: Viresh Kumar <viresh.kumar@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] OPP: Disallow "opp-hz" property without a corresponding clk
Date: Mon, 21 Nov 2022 14:00:36 +0530 [thread overview]
Message-ID: <20221121083036.ppwfprrheuf7xl7c@vireshk-i7> (raw)
In-Reply-To: <Y3sryFh84eK/sWKF@hovoldconsulting.com>
On 21-11-22, 08:42, Johan Hovold wrote:
> Ok, I was expected the devicetree update to through Bjorn's tree as I
> imagine there may be conflicts otherwise.
Dropped the DT patch now.
Mani, I believe the first patch in this series is still required.
Without that, when the cpufreq driver calls dev_pm_opp_set_opp(), the
OPP core may end up calling clk_set_rate(), which shouldn't be done in
case of Qcom SoCs.
I am not sure though, how it will work with sc8280xp. Can you please
check ?
--
viresh
next prev parent reply other threads:[~2022-11-21 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 6:57 [PATCH 0/2] OPP: Disallow "opp-hz" property without a corresponding clk Viresh Kumar
2022-11-21 6:57 ` [PATCH 1/2] cpufreq: qcom-cpufreq-hw: Register config_clks helper Viresh Kumar
2022-11-21 6:57 ` [PATCH 2/2] OPP: Disallow "opp-hz" property without a corresponding clk Viresh Kumar
2022-11-21 7:22 ` Johan Hovold
2022-11-21 7:38 ` Viresh Kumar
2022-11-21 7:42 ` Johan Hovold
2022-11-21 8:30 ` Viresh Kumar [this message]
2022-11-22 13:26 ` Manivannan Sadhasivam
2022-11-24 4:23 ` Viresh Kumar
2022-11-24 5:24 ` Manivannan Sadhasivam
2022-11-21 7:44 ` Manivannan Sadhasivam
2022-11-21 7:39 ` Manivannan Sadhasivam
2023-01-25 4:21 ` Viresh Kumar
2023-02-16 6:47 ` Manivannan Sadhasivam
2023-10-11 5:48 ` Viresh Kumar
2023-11-15 6:32 ` Viresh Kumar
2023-11-15 7:55 ` Manivannan Sadhasivam
2023-11-15 8:43 ` Dmitry Baryshkov
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=20221121083036.ppwfprrheuf7xl7c@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andersson@kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vincent.guittot@linaro.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 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.