[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d38cf11-114a-4997-a0fc-4627402468f8@sapience.com>
Date: Wed, 30 Aug 2023 17:09:07 -0400
From: Genes Lists <lists@...ience.com>
To: Ricky WU <ricky_wu@...ltek.com>, Keith Busch <kbusch@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"hch@....de" <hch@....de>, "arnd@...db.de" <arnd@...db.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: Re: Possible nvme regression in 6.4.11
...
> I think maybe it is a system power saving issue....
> In the past if the BIOS(config space) not set L1-substate, our driver will keep drive low CLKREQ# when HOST want to enter power saving state that make whole system not enter the power saving state.
> But this patch we release the CLKREQ# to HOST, make whole system can enter power saving state success when the HOST want to enter the power saving state, but I don't know why your system can not wake out success from power saving stat on the platform
>
> Ricky
>
Hi
Thanks for continuing to look into this. Can you share your thoughts
on best way to proceed going forward - do you plan to revert or
something else?
thanks
gene
Powered by blists - more mailing lists