mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: zhangqing <zhangqing@rock-chips.com>
To: "Stephen Boyd" <sboyd@kernel.org>, heiko <heiko@sntech.de>,
	mturquette <mturquette@baylibre.com>,
	杨凯 <kever.yang@rock-chips.com>
Cc: linux-clk <linux-clk@vger.kernel.org>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	huangtao <huangtao@rock-chips.com>,
	张学广 <sugar.zhang@rock-chips.com>
Subject: Re: [PATCH v1] clk: gate: export clk_gate_endisable
Date: Thu, 8 Aug 2024 09:09:53 +0800	[thread overview]
Message-ID: <e407b8ba-e72a-4b53-af8e-7dbb58420b07@rock-chips.com> (raw)
In-Reply-To: <d673b1539ad5d4abfff29900461f9209.sboyd@kernel.org>

Hi,

在 2024/8/8 4:57, Stephen Boyd 写道:
> Quoting zhangqing@rock-chips.com (2024-08-06 18:28:34)
>> Hi,
>>
>> Some modules, which need to do workaround, need to disabled the clock directly,
>> independent of the reference count.
> We don't want clk consumers going behind the clk provider and turning it
> off and on. You'll need to figure out some other way to do this. Are
> there really other consumers besides the one changing the pin to a gpio?
> If there's only one user then it seems like clk_disable() should work?
Well, then I use other ways to workaround module problems.

-- 
张晴
瑞芯微电子股份有限公司
Rockchip Electronics Co.,Ltd
地址:福建省福州市铜盘路软件大道89号软件园A区21号楼
Add:No.21 Building, A District, No.89 Software Boulevard Fuzhou, Fujian 350003, P.R.China
Tel:+86-0591-83991906-8601
邮编:350003
E-mail:elaine.zhang@rock-chips.com
****************************************************************************
保密提示:本邮件及其附件含有机密信息,仅发送给本邮件所指特定收件人。若非该特定收件人,请勿复制、使用或披露本邮件的任何内容。若误收本邮件,请从系统中永久性删除本邮件及所有附件,并以回复邮件或其他方式即刻告知发件人。福州瑞芯微电子有限公司拥有本邮件信息的著作权及解释权,禁止任何未经授权许可的侵权行为。

IMPORTANT NOTICE: This email is from Fuzhou Rockchip Electronics Co., Ltd .The contents of this email and any attachments may contain information that is privileged, confidential and/or exempt from disclosure under applicable law and relevant NDA. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information is STRICTLY PROHIBITED. Please immediately contact the sender as soon as possible and destroy the material in its entirety in any format. Thank you.

****************************************************************************


      reply	other threads:[~2024-08-08  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  7:38 Elaine Zhang
2024-08-06 17:52 ` Stephen Boyd
     [not found]   ` <2024080709283455745026@rock-chips.com>
2024-08-07 20:57     ` Stephen Boyd
2024-08-08  1:09       ` zhangqing [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=e407b8ba-e72a-4b53-af8e-7dbb58420b07@rock-chips.com \
    --to=zhangqing@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=sugar.zhang@rock-chips.com \
    /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®