From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Ricky WU <ricky_wu@realtek.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paul.grandperrin@gmail.com" <paul.grandperrin@gmail.com>,
Jade Lovelace <lists@jade.fyi>
Subject: Re: [PATCH] misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe
Date: Wed, 20 Sep 2023 11:21:13 +0200 [thread overview]
Message-ID: <2023092032-blurred-upload-30bd@gregkh> (raw)
In-Reply-To: <37b1afb997f14946a8784c73d1f9a4f5@realtek.com>
On Wed, Sep 20, 2023 at 09:11:19AM +0000, Ricky WU wrote:
> commit 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg")
> some readers no longer force #CLKREQ to low
> when the system need to enter ASPM.
> But some platform maybe not implement complete ASPM?
> it causes some platforms can not boot
>
> Like in the past only the platform support L1ss we release the #CLKREQ.
> Move the judgment (L1ss) to probe,
> we think read config space one time when the driver start is enough
>
> Fixes: 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg")
> Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
What about all of the people that reported this issue? Have they been
able to test it? At least a reported-by line should be added, right?
And I'd like someone to test it to verify it fixes the issue before
applying it...
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-20 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:11 [PATCH] misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe Ricky WU
2023-09-20 9:21 ` gregkh [this message]
2023-09-20 12:47 ` Paul Grandperrin
2023-09-20 13:06 ` Greg KH
2023-09-24 21:05 ` Jade Lovelace
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=2023092032-blurred-upload-30bd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@jade.fyi \
--cc=paul.grandperrin@gmail.com \
--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