Re: [PATCH net V4 1/3] net: lan743x: disable WOL upon resume to restore full data path operation

[Andrew Lunn <andrew@lunn.ch>]

On Fri, Jun 14, 2024 at 10:00:58AM +0530, Raju Lakkaraju wrote:
> Hi Russell King,
> 
> The 06/13/2024 08:44, Russell King (Oracle) wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> > 
> > On Wed, Jun 12, 2024 at 10:55:37PM +0530, Raju Lakkaraju wrote:
> > > @@ -3728,6 +3729,30 @@ static int lan743x_pm_resume(struct device *dev)
> > >               return ret;
> > >       }
> > >
> > > +     ret = lan743x_csr_read(adapter, MAC_WK_SRC);
> > > +     netif_info(adapter, drv, adapter->netdev,
> > > +                "Wakeup source : 0x%08X\n", ret);
> > 
> > Does this need to be printed at info level, or is it a debug message?
> 
> Print at info level helps the tester/sqa team to identify the root cause of
> the wake and confirm the test cases.
> In general, tester does not enable debug level messages for testing.
> 
> Still, if we need to change from info to debug, i can change.
> Please let me know.

We are not really writing a kernel for the tester/SQA team, but the
end users. Do the end users find this log message useful? Can they
decode some hex value into something meaningful?

I'm surprised the test case cares what caused the wakeup. So long as
it does wake up, does it really matter what the source was?

	Andrew