From: Tony Lindgren <tony@atomide.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Dhruva Gole" <d-gole@ti.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Johan Hovold" <johan@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-omap@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v11 1/1] serial: core: Start managing serial controllers to enable runtime PM
Date: Sun, 14 May 2023 08:41:22 +0300 [thread overview]
Message-ID: <20230514054122.GH14287@atomide.com> (raw)
In-Reply-To: <2023051332-pretended-spoiler-61fc@gregkh>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> [230513 11:10]:
> On Thu, May 11, 2023 at 09:53:51AM +0300, Tony Lindgren wrote:
> > We want to enable runtime PM for serial port device drivers in a generic
> > way. To do this, we want to have the serial core layer manage the
> > registered physical serial controller devices.
> >
> > To do this, let's set up a struct bus and struct device for the serial
> > core controller as suggested by Greg and Jiri. The serial core controller
> > devices are children of the physical serial port device. The serial core
> > controller device is needed to support multiple different kind of ports
> > connected to single physical serial port device.
> >
> > Let's also set up a struct device for the serial core port. The serial
> > core port instances are children of the serial core controller device.
> >
> > With the serial core port device we can now flush pending TX on the
> > runtime PM resume as suggested by Johan.
>
> Much better, thanks!
>
> One thing jumps out at me though, you are passing around "raw" struct
> device pointers as the serial port structure, why?
>
> Shouldn't:
>
> > @@ -563,7 +564,8 @@ struct uart_port {
> > unsigned int minor;
> > resource_size_t mapbase; /* for ioremap */
> > resource_size_t mapsize;
> > - struct device *dev; /* parent device */
> > + struct device *dev; /* serial port physical parent device */
> > + struct device *port_dev; /* serial core port device */
>
> port_dev here be something like "struct serial_port" (or some better
> name)? That way you enforce the type being passed around to the serial
> code in this change which will help catch any type mistakes.
>
> Yes, this structure can just be a "wrapper" around 'struct device' but
> at least it's a unique type.
Good idea thanks, will change.
> Or am I missing why this was done this way?
No reason to keep it as struct device.
Regards,
Tony
prev parent reply other threads:[~2023-05-14 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 6:53 [PATCH v11 1/1] serial: core: Start managing serial controllers to enable runtime PM Tony Lindgren
2023-05-13 11:07 ` Greg Kroah-Hartman
2023-05-14 5:41 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230514054122.GH14287@atomide.com \
--to=tony@atomide.com \
--cc=andriy.shevchenko@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).