[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220901131016.74a9a730@kernel.org>
Date: Thu, 1 Sep 2022 13:10:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>,
Florian Fainelli <f.fainelli@...il.com>
Cc: wei.fang@....com, davem@...emloft.net, edumazet@...gle.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] net: fec: add pm_qos support on imx6q platform
On Thu, 01 Sep 2022 09:17:37 +0200 Paolo Abeni wrote:
> On Tue, 2022-08-30 at 15:01 +0800, wei.fang@....com wrote:
> > From: Wei Fang <wei.fang@....com>
> >
> > There is a very low probability that tx timeout will occur during
> > suspend and resume stress test on imx6q platform. So we add pm_qos
> > support to prevent system from entering low level idles which may
> > affect the transmission of tx.
> >
> > Signed-off-by: Wei Fang <wei.fang@....com>
>
> Since this IMHO causes a significal behavior change I suggest to target
> the net-next tree, does that fit you?
>
> Additionally, it would be great if you could provide in the changelog
> the references to the relevant platform documentation and (even rough)
> power consumption delta estimates.
It's a tricky one, we don't want older kernels to potentially hang
either.
IIRC Florian did some WoL extensions for BRCM, maybe he has the right
experience.
Florian, what would you recommend? net or net-next?
Powered by blists - more mailing lists