[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de5f6ecd-e3c9-4a14-a9ba-12614f19f191@gmail.com>
Date: Tue, 19 Nov 2024 03:50:44 +0200
From: Sergey Ryazanov <ryazanov.s.a@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: wojackbb@...il.com, netdev@...r.kernel.org,
chandrashekar.devegowda@...el.com, chiranjeevi.rapolu@...ux.intel.com,
haijun.liu@...iatek.com, m.chetan.kumar@...ux.intel.com,
ricardo.martinez@...ux.intel.com, loic.poulain@...aro.org,
johannes@...solutions.net, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, linux-arm-kernel@...ts.infradead.org,
angelogioacchino.delregno@...labora.com, linux-mediatek@...ts.infradead.org,
matthias.bgg@...il.com
Subject: Re: [net-next,v2] [PATCH net-next v2] net: wwan: t7xx: Change
PM_AUTOSUSPEND_MS to 5000
On 19.11.2024 03:44, Jakub Kicinski wrote:
> On Tue, 19 Nov 2024 03:01:47 +0200 Sergey Ryazanov wrote:
>>> He's decreasing the sleep timer from 20 to 5 sec, both of which
>>> are very high for networking, anyway. You appear to be questioning
>>> autosuspend itself but it seems to have been added 2 years ago already.
>>>
>>> What am I missing?
>>
>> Some possible funny side-effect of sleeping with this chipset. Like
>> loosing network connection and dropping TCP sessions. I hope that 20
>> seconds was putted on purpose.
>>
>> Suddenly, I don't have this modem at hand and want to be sure that we
>> are not going to receive a stream of bug reports.
>
> Power saving is always tricky, but they say they tested. I think we
> should give it a go, worst case - it will be an easy revert.
Make sense. Then let's merge it.
Reviewed-by: Sergey Ryazanov <ryazanov.s.a@...il.com>
Powered by blists - more mailing lists