[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB7PR04MB46180EE59D373F9634DD936AE6440@DB7PR04MB4618.eurprd04.prod.outlook.com>
Date: Wed, 27 Nov 2019 09:58:03 +0000
From: Joakim Zhang <qiangqing.zhang@....com>
To: Sean Nyekjaer <sean@...nix.com>,
"mkl@...gutronix.de" <mkl@...gutronix.de>,
"linux-can@...r.kernel.org" <linux-can@...r.kernel.org>
CC: dl-linux-imx <linux-imx@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH V2 0/4] can: flexcan: fixes for stop mode
> -----Original Message-----
> From: Sean Nyekjaer <sean@...nix.com>
> Sent: 2019年11月27日 17:52
> To: Joakim Zhang <qiangqing.zhang@....com>; mkl@...gutronix.de;
> linux-can@...r.kernel.org
> Cc: dl-linux-imx <linux-imx@....com>; netdev@...r.kernel.org
> Subject: Re: [PATCH V2 0/4] can: flexcan: fixes for stop mode
>
>
>
> On 27/11/2019 10.48, Joakim Zhang wrote:
> > One more should confirm with you, you inserted a flexcan.ko after stop
> > mode activated without fix patch firstly, and then inserted a
> > flexcan.ko with fix patch. If yes, this could cause unbalanced
> pm_runtime_enabled. The reason is that firstly inserted the flexcan.ko would
> enable device runtime pm, and then you inserted flexcan.ko enable device
> runtime pm again.
> >
> > Could you please insert flexcan.ko with fix patch directly after stop mode
> activated?
> >
> Hi,
>
> If I insert flexcan.ko with fix patch directly after stop mode activated, the
> unbalanced msg is not shown...
> I guess we are good then :)
Great, Thanks a lot!
Could you give your Test-by tag for this patch set? And then Marc could review this patch set.
Best Regards,
Joakim Zhang
> /Sean
Powered by blists - more mailing lists