[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023092032-blurred-upload-30bd@gregkh>
Date: Wed, 20 Sep 2023 11:21:13 +0200
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Ricky WU <ricky_wu@...ltek.com>
Cc: "arnd@...db.de" <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"paul.grandperrin@...il.com" <paul.grandperrin@...il.com>,
Jade Lovelace <lists@...e.fyi>
Subject: Re: [PATCH] misc: rtsx: Fix some platforms can not boot and move the
l1ss judgment to probe
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@...ltek.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
Powered by blists - more mailing lists