[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231006072738.GI34982@atomide.com>
Date: Fri, 6 Oct 2023 10:27:38 +0300
From: Tony Lindgren <tony@...mide.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, Dhruva Gole <d-gole@...com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
John Ogness <john.ogness@...utronix.de>,
Johan Hovold <johan@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Vignesh Raghavendra <vigneshr@...com>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
Maximilian Luz <luzmaximilian@...il.com>
Subject: Re: [PATCH] serial: core: Fix checks for tx runtime PM state
* Andy Shevchenko <andriy.shevchenko@...ux.intel.com> [231005 12:01]:
> On Thu, Oct 05, 2023 at 10:56:42AM +0300, Tony Lindgren wrote:
> > The serdev device and the serial core controller devices are siblings of
> > the serial port hardware device. The runtime PM usage count from serdev
>
> I'm a bit lost in terminology here.
> AFAIU there are:
> 1) children of the serial physical device;
> 2) siblings (to each other).
>
> But may be I mistakenly deciphered the diagram from the previous discussion.
You're right, so how about:
The serdev device and the serial core controller devices are children of
the serial port hardware device. The runtime PM usage count from serdev
device does not propagate to the serial core device siblings, it only
propagates to the parent.
Regards,
Tony
Powered by blists - more mailing lists