From: Jie Luo <quic_luoj@quicinc.com>
To: Stephen Boyd <sboyd@kernel.org>, <agross@kernel.org>,
<andersson@kernel.org>, <conor+dt@kernel.org>,
<konrad.dybcio@linaro.org>, <krzysztof.kozlowski+dt@linaro.org>,
<mturquette@baylibre.com>, <p.zabel@pengutronix.de>,
<robh+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_srichara@quicinc.com>
Subject: Re: [PATCH 1/3] clk: Add the flag CLK_ENABLE_MUTEX_LOCK of enabling clock
Date: Wed, 2 Aug 2023 18:33:20 +0800 [thread overview]
Message-ID: <b0ddd1d0-9140-16a7-3cd8-18c9cd4e69f4@quicinc.com> (raw)
In-Reply-To: <02abeb64fb360245791b467b371f1491.sboyd@kernel.org>
On 8/2/2023 3:18 AM, Stephen Boyd wrote:
> Quoting Luo Jie (2023-08-01 01:53:50)
>> Support the clock controller where the HW register is
>> accessed by MDIO bus, the spin lock can't be used because
>> of sleep during the MDIO operation.
>>
>> Add the flag CLK_ENABLE_MUTEX_LOCK to hint clock framework
>> to use mutex lock instead of the spin lock.
>
> Why can't you enable the MDIO bus clk in .prepare()?
thanks Stephen for the suggestion, let me check this and update patchset.
next prev parent reply other threads:[~2023-08-02 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 8:53 [PATCH 0/3] add clock controller of qca8386/qca8084 Luo Jie
2023-08-01 8:53 ` [PATCH 1/3] clk: Add the flag CLK_ENABLE_MUTEX_LOCK of enabling clock Luo Jie
2023-08-01 19:18 ` Stephen Boyd
2023-08-02 10:33 ` Jie Luo [this message]
2023-08-01 8:53 ` [PATCH 2/3] dt-bindings: clock: add qca8386/qca8084 clock and reset definitions Luo Jie
2023-08-01 9:36 ` Rob Herring
2023-08-07 6:52 ` Krzysztof Kozlowski
2023-08-08 5:19 ` Jie Luo
2023-08-08 5:57 ` Krzysztof Kozlowski
2023-08-08 6:31 ` Jie Luo
2023-08-08 6:46 ` Krzysztof Kozlowski
2023-08-08 6:59 ` Jie Luo
2023-08-01 8:53 ` [PATCH 3/3] clk: qcom: add clock controller driver for qca8386/qca8084 Luo Jie
2023-08-01 19:16 ` Randy Dunlap
2023-08-02 10:34 ` Jie Luo
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=b0ddd1d0-9140-16a7-3cd8-18c9cd4e69f4@quicinc.com \
--to=quic_luoj@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.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=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®