From: Chris Clayton <chris2553@googlemail.com>
To: "吳昊澄 Ricky" <ricky_wu@realtek.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"philquadra@gmail.com" <philquadra@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes
Date: Sat, 22 Aug 2020 08:24:07 +0100 [thread overview]
Message-ID: <29b12ecc-6e5c-8c1a-942b-ad23a95d020a@googlemail.com> (raw)
In-Reply-To: <20da8b4b-8426-9568-c0f1-4d1c2006c53f@googlemail.com>
Hi Ricky.
On 05/08/2020 13:48, Chris Clayton wrote:
> Hi Ricky
<snip>
>>
>> Ah, OK. I'll prepare the patch and send it to you once I've tested it.
>>
>
> Please see the patch included below. As you suggested, it removes the code that does the OC power down on card readers
> that are not members of your A series. The patch is against a fresh pull of Linus's tree this morning
> (v5.8-2768-g4da9f3302615).
>
> I've tested the resultant kernel on my Intel NUC6CAYH box (which contains an NUC66AYB board) and the rts5229 works fine.
> I've also tested it on my laptop which also has a card reader supported by the rtsx_pci driver (an RTL8411B) and that
> also works fine.
>
> As I mentioned yesterday, I think it's a candidate for the 5.4 ans 5.7 stable series.
>
> Thanks for your patience!
>
> Chris
>
> Signed-off-by: Chris Clayton <chris2553@googlemail.com>
>
> --- a/drivers/misc/cardreader/rtsx_pcr.c 2020-08-05 07:10:21.752072515 +0100
> +++ b/drivers/misc/cardreader/rtsx_pcr.c 2020-08-05 07:11:05.568074278 +0100
> @@ -1172,10 +1172,6 @@ void rtsx_pci_init_ocp(struct rtsx_pcr *
> rtsx_pci_write_register(pcr, REG_OCPGLITCH,
> SD_OCP_GLITCH_MASK, pcr->hw_param.ocp_glitch);
> rtsx_pci_enable_ocp(pcr);
> - } else {
> - /* OC power down */
> - rtsx_pci_write_register(pcr, FPDCTL, OC_POWER_DOWN,
> - OC_POWER_DOWN);
> }
> }
> }
>
>
Is there some problem with my patch? If you are too busy to deal with it, perhaps I can submit directly it to Greg/Arnd.
Thanks
Chris
prev parent reply other threads:[~2020-08-22 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 19:48 Chris Clayton
2020-08-02 19:58 ` Chris Clayton
2020-08-03 3:01 ` 吳昊澄 Ricky
2020-08-03 5:27 ` Chris Clayton
2020-08-04 2:44 ` 吳昊澄 Ricky
2020-08-04 7:48 ` gregkh
2020-08-04 8:08 ` 吳昊澄 Ricky
2020-08-04 8:13 ` gregkh
2020-08-04 8:50 ` Chris Clayton
2020-08-04 10:46 ` 吳昊澄 Ricky
2020-08-04 11:51 ` Chris Clayton
2020-08-05 2:35 ` 吳昊澄 Ricky
2020-08-05 5:51 ` Chris Clayton
2020-08-05 12:48 ` Chris Clayton
2020-08-22 7:24 ` Chris Clayton [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=29b12ecc-6e5c-8c1a-942b-ad23a95d020a@googlemail.com \
--to=chris2553@googlemail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philquadra@gmail.com \
--cc=rdunlap@infradead.org \
--cc=ricky_wu@realtek.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®