From: Johan Hovold <johan@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/3] USB-Serial serdev support
Date: Tue, 11 Mar 2025 09:20:20 +0100 [thread overview]
Message-ID: <Z8_yRFZrb6WFp5Y2@hovoldconsulting.com> (raw)
In-Reply-To: <20241028225702.tdtfqzhm335vvuv5@pengutronix.de>
On Mon, Oct 28, 2024 at 11:57:02PM +0100, Marco Felsch wrote:
> On 24-10-01, Greg Kroah-Hartman wrote:
> > On Tue, Oct 01, 2024 at 09:24:53AM +0200, Marco Felsch wrote:
> > > gentle ping as this is series is two months old now.
> >
> > And it was rejected as serdev does not support hotplug which of course,
> > usb-serial does.
>
> I hoped to get some feedback on my answer [1]. Regarding hotplug
> support: serdev _requires_ some sort of firmware like OF (not sure if it
> does work with ACPI too). That said, if serdev finds no firmware a
> fallback is provided to the standard serial handling.
It's devices going away not being supported which is the main concern.
The serdev ttyport implementation does not implement hangup() which is
used for serial port tear down.
> The firmware could either be added directly by the platform OF file or
> via OF-overlays. By making use of overlays we could gain some kind of
> hotplug: Once a usb devices was detected and the driver has an
> overlay, the overlay gets applied and the probe continues, like we do it
> for PCIe devices now [2]. For devices which don't have a registered
> overlay the standard usb-serial setup is done by exposing the serial
> interface to the userspace.
Then it would also be nice to have a way to describe hotplugged devices
on the fly, and overlays could indeed be used for that. But that's a
separate story.
Johan
prev parent reply other threads:[~2025-03-11 8:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:08 [PATCH 0/3] USB-Serial serdev support Marco Felsch
2024-08-07 14:08 ` [PATCH 1/3] serdev: ttyport: make use of tty_kopen_exclusive Marco Felsch
2024-08-08 7:51 ` Jiri Slaby
2024-08-19 10:19 ` Marco Felsch
2024-08-19 10:42 ` Jiri Slaby
2024-08-19 12:23 ` Marco Felsch
2024-08-21 7:25 ` Marco Felsch
2024-08-07 14:08 ` [PATCH 2/3] USB: serial: cosmetic cleanup <space><tab> mix Marco Felsch
2024-08-07 14:08 ` [PATCH 3/3] USB: serial: enable serdev support Marco Felsch
2024-09-09 12:03 ` [PATCH 0/3] USB-Serial " Johan Hovold
2024-09-17 4:49 ` Marco Felsch
2025-03-11 8:12 ` Johan Hovold
2025-03-13 19:40 ` Marco Felsch
2025-08-21 16:40 ` Marco Felsch
2025-10-23 12:32 ` Johan Hovold
2025-10-23 13:48 ` Marco Felsch
2025-10-24 8:21 ` Johan Hovold
2025-10-24 9:27 ` Marco Felsch
2025-10-24 10:32 ` Johan Hovold
2025-10-24 12:40 ` Marco Felsch
2025-10-24 13:26 ` Johan Hovold
2025-10-24 16:22 ` Marco Felsch
2024-10-01 7:24 ` Marco Felsch
2024-10-01 7:29 ` Greg Kroah-Hartman
2024-10-01 7:47 ` Marco Felsch
2024-10-28 22:57 ` Marco Felsch
2025-03-03 11:25 ` Marco Felsch
2025-03-11 8:20 ` Johan Hovold [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=Z8_yRFZrb6WFp5Y2@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh@kernel.org \
/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