From: Bjorn Helgaas <helgaas@kernel.org>
To: ricky_wu@realtek.com
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, yuehaibing@huawei.com,
ulf.hansson@linaro.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] misc: rtsx: modify rts522a init flow
Date: Tue, 2 Feb 2021 06:27:38 -0600 [thread overview]
Message-ID: <20210202122738.GA87016@bjorn-Precision-5520> (raw)
In-Reply-To: <20210202105641.29330-1-ricky_wu@realtek.com>
The subject line could be more descriptive. All patches modify
something, so the only real information it contains is "rts522a" and
"init". Maybe it could say something about powering off OCP (whatever
that is) when no memory card is present.
On Tue, Feb 02, 2021 at 06:56:41PM +0800, ricky_wu@realtek.com wrote:
> From: Ricky Wu <ricky_wu@realtek.com>
>
> Power down OCP for power consumption
> when card is not exist at init_hw()
I assume "card is not exist" means "no SD/MMC card is present".
Why do you only do this for 5227? "card_exist" seems to be a generic
concept (it's in struct rtsx_pcr and set by the generic
rtsx_pci_init_hw()). Could/should this be done for other card readers
as well?
> Cc: stable@vger.kernel.org
Per https://www.kernel.org/doc/html/v5.10/process/stable-kernel-rules.html
(option 1) this is sufficient. You should not include
stable@kernel.org in the cc: list above.
> Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
> ---
> drivers/misc/cardreader/rts5227.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/misc/cardreader/rts5227.c b/drivers/misc/cardreader/rts5227.c
> index 8859011672cb..8200af22b529 100644
> --- a/drivers/misc/cardreader/rts5227.c
> +++ b/drivers/misc/cardreader/rts5227.c
> @@ -398,6 +398,11 @@ static int rts522a_extra_init_hw(struct rtsx_pcr *pcr)
> {
> rts5227_extra_init_hw(pcr);
>
> + /* Power down OCP for power consumption */
> + if (!pcr->card_exist)
> + rtsx_pci_write_register(pcr, FPDCTL, OC_POWER_DOWN,
> + OC_POWER_DOWN);
> +
> rtsx_pci_write_register(pcr, FUNC_FORCE_CTL, FUNC_FORCE_UPME_XMT_DBG,
> FUNC_FORCE_UPME_XMT_DBG);
> rtsx_pci_write_register(pcr, PCLK_CTL, 0x04, 0x04);
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-02-02 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 10:56 ricky_wu
2021-02-02 12:27 ` Bjorn Helgaas [this message]
2021-02-03 3:13 ` 吳昊澄 Ricky
2021-02-03 12:48 ` Bjorn Helgaas
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=20210202122738.GA87016@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yuehaibing@huawei.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®