From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"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-serial@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] serial: core: Start managing serial controllers to enable runtime PM
Date: Thu, 24 Nov 2022 18:06:32 +0200 [thread overview]
Message-ID: <Y3+WiArMrBPTwdaq@smile.fi.intel.com> (raw)
In-Reply-To: <Y3+PoxJNJm0Pe+Xm@atomide.com>
On Thu, Nov 24, 2022 at 05:37:07PM +0200, Tony Lindgren wrote:
> * Jiri Slaby <jirislaby@kernel.org> [221124 06:53]:
> > On 27. 06. 22, 15:48, Tony Lindgren wrote:
...
> > And you are objecting that mostly (or in all cases?), there will never be
> > "serial controller 2"?
>
> I'm was not aware of the need for multiple serial port controllers
> connected to a single hardware controller struct device. Is there an
> example for that somewhere?
I would be on the safest side here by assuming that's possible
(QEMU and FPGA are the first that comes to my mind of such possibilities).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-24 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:24 [PATCH v2 1/1] serial: core: Start managing serial controllers to enable runtime PM Tony Lindgren
2022-06-15 9:17 ` Andy Shevchenko
2022-06-16 8:23 ` Tony Lindgren
2022-06-16 8:51 ` Tony Lindgren
2022-06-27 12:16 ` Greg Kroah-Hartman
2022-06-27 13:48 ` Tony Lindgren
2022-11-24 6:53 ` Jiri Slaby
2022-11-24 15:37 ` Tony Lindgren
2022-11-24 16:06 ` Andy Shevchenko [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=Y3+WiArMrBPTwdaq@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=bigeasy@linutronix.de \
--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=tony@atomide.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.