From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: imx: add rx and tx led trigger
Date: Wed, 06 Jul 2016 17:22:40 +0200 [thread overview]
Message-ID: <5565521.Lr5FKj2vNK@wuerfel> (raw)
In-Reply-To: <20160704155009.GJ16643@pengutronix.de>
On Monday, July 4, 2016 5:50:09 PM CEST Uwe Kleine-K?nig wrote:
> On Mon, Jul 04, 2016 at 05:43:03PM +0200, Arnd Bergmann wrote:
> > On Monday, July 4, 2016 5:34:12 PM CEST Uwe Kleine-K?nig wrote:
> > > Add support for two led triggers per UART instance that blink on
> > > transmission and reception of data respectively.
> > >
> > > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> > > ---
> > > drivers/tty/serial/imx.c | 57 ++++++++++++++++++++++++++++++++++++++++++++++++
> > > 1 file changed, 57 insertions(+)
> >
> > What is specific to this driver here? Could this be done in the
> > core tty code instead?
>
> The core doesn't notice when the driver starts to push out characters.
>
> I also have a patch in my queue that adds support for rts delaying in
> rs485 mode. While the delay between start_tx being called and the first
> char leaving the hardware might not be big enough to care in rs232 mode,
> with a big delay_rts_before_send it might matter.
Right, that makes sense. It still seems odd to have this just in one
driver, and your changelog above doesn't really explain what the
blinkenlights are actually good for.
I'm sure you had something useful in mind, can you elaborate?
If this is something we may want to do on other platforms as well,
we should perhaps not hardwire the name of the imx tty device in
the led trigger name.
Arnd
next prev parent reply other threads:[~2016-07-06 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 15:34 [PATCH] serial: imx: add rx and tx led trigger Uwe Kleine-König
2016-07-04 15:43 ` Arnd Bergmann
2016-07-04 15:50 ` Uwe Kleine-König
2016-07-06 15:22 ` Arnd Bergmann [this message]
2016-07-06 17:30 ` Uwe Kleine-König
2016-07-06 20:09 ` Arnd Bergmann
2016-07-07 6:28 ` Uwe Kleine-König
2016-07-07 8:27 ` Arnd Bergmann
2016-07-07 8:33 ` Uwe Kleine-König
2016-07-07 8:43 ` Arnd Bergmann
2016-08-31 14:00 ` Greg KH
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=5565521.Lr5FKj2vNK@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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