[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191217081718.23807-1-u.kleine-koenig@pengutronix.de>
Date: Tue, 17 Dec 2019 09:17:15 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>
Cc: linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
linux-serial@...r.kernel.org, kernel@...gutronix.de
Subject: [PATCH v2 0/3] tty/leds: implement a trigger for ttys
Hello,
back in November last year I sent my last approach to implement an led
trigger for UARTs (Message-Id:
20181106213739.29628-1-u.kleine-koenig@...gutronix.de). This was parked
on my todo list since then somewhere far from the top.
This is a new approach. Similar to the netdev trigger the tty trigger
introduced here periodically checks the statistics related to a given
tty and if that changed the LED is flashed once.
I had to introduce two functions in the tty layer to be able to get my
hands on the needed data in the first two patches, the third patch then
adds the trigger.
Best regards
Uwe
Uwe Kleine-König (3):
tty: new helper function tty_kopen_shared
tty: new helper function tty_get_icount()
leds: trigger: implement a tty trigger
drivers/leds/trigger/Kconfig | 7 ++
drivers/leds/trigger/Makefile | 1 +
drivers/leds/trigger/ledtrig-tty.c | 146 +++++++++++++++++++++++++++++
drivers/tty/tty_io.c | 47 ++++++++-
include/linux/tty.h | 3 +
5 files changed, 200 insertions(+), 4 deletions(-)
create mode 100644 drivers/leds/trigger/ledtrig-tty.c
--
2.24.0
Powered by blists - more mailing lists