From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Pavel Machek" <pavel@denx.de>,
"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"Dan Murphy" <dmurphy@ti.com>, "Jiri Slaby" <jslaby@suse.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v5 3/3] leds: trigger: implement a tty trigger
Date: Tue, 7 Jan 2020 10:34:31 +0100 [thread overview]
Message-ID: <20200107093431.GA21375@amd> (raw)
In-Reply-To: <20200106185918.GB597279@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 3029 bytes --]
Hi!
> > > > +static ssize_t dev_store(struct device *dev,
> > > > + struct device_attribute *attr, const char *buf,
> > > > + size_t size)
> > > > +{
> > > > + struct ledtrig_tty_data *trigger_data = led_trigger_get_drvdata(dev);
> > > > + struct tty_struct *tty;
> > > > + unsigned major, minor;
> > > > + int ret;
> > > > +
> > > > + if (size == 0 || (size == 1 && buf[0] == '\n')) {
> > > > + tty = NULL;
> > > > + } else {
> > > > + ret = sscanf(buf, "%u:%u", &major, &minor);
> > > > + if (ret < 2)
> > > > + return -EINVAL;
> > >
> > > If user writes 1:2:badparsingofdata into the file, it will pass, right?
> >
> > Yes, and it will have the same effect as writing 1:2. I wonder if this
> > is bad.
It is.
> > > > +static void ledtrig_tty_work(struct work_struct *work)
> > > > +{
> > > > + struct ledtrig_tty_data *trigger_data =
> > > > + container_of(work, struct ledtrig_tty_data, dwork.work);
> > > > + struct serial_icounter_struct icount;
> > > > + int ret;
> > > > +
> > > > + if (!trigger_data->tty) {
> > > > + led_set_brightness(trigger_data->led_cdev, LED_OFF);
> > > > + return;
> > > > + }
> > > > +
> > > > + ret = tty_get_icount(trigger_data->tty, &icount);
> > > > + if (ret)
> > > > + return;
> > > > +
> > > > + if (icount.rx != trigger_data->rx ||
> > > > + icount.tx != trigger_data->tx) {
> > > > + unsigned long delay_on = 100, delay_off = 100;
> > > > +
> > > > + led_blink_set_oneshot(trigger_data->led_cdev,
> > > > + &delay_on, &delay_off, 0);
> > > > +
> > > > + trigger_data->rx = icount.rx;
> > > > + trigger_data->tx = icount.tx;
> > > > + }
> > >
> > > Since you are polling this, anyway, can you just manipulate brightness
> > > directly instead of using _oneshot()? _oneshot() will likely invoke
> > > another set of workqueues.
> >
> > I copied that from the netdev trigger. I failed to find a suitable
> > helper function, did I miss that or does it need creating?
You don't need helper function. You are periodically checking the
statistics, anyway, so use it to turn the LED on/off directly, without
oneshot helper, which uses another workqueue internally.
> > > LED triggers were meant to operate directly from the events, not based
> > > on statistics like this.
> >
> > Ditto; just copied from the netdev trigger. I tried to find a suitable
> > place to add a trigger in the core, but this is hard without having to
> > modify all drivers; additionally this is in thier hot path. So I
> > considered using statistics a good idea. Greg also liked it and someone
> > before us for the network trigger, too ...
>
> This still looks ok to me, any objections to me merging it in my tty
> tree?
Yes.
I guess using statistics is kind-off acceptable, but the stuff I quote
above is not.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2020-01-07 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 9:39 [PATCH v5 0/3] tty/leds: implement a trigger for ttys Uwe Kleine-König
2019-12-19 9:39 ` [PATCH v5 1/3] tty: rename tty_kopen() and add new function tty_kopen_shared() Uwe Kleine-König
2019-12-19 9:39 ` [PATCH v5 2/3] tty: new helper function tty_get_icount() Uwe Kleine-König
2019-12-19 9:39 ` [PATCH v5 3/3] leds: trigger: implement a tty trigger Uwe Kleine-König
2019-12-21 18:40 ` Pavel Machek
2019-12-23 10:08 ` Uwe Kleine-König
2020-01-06 18:59 ` Greg Kroah-Hartman
2020-01-07 7:29 ` Uwe Kleine-König
2020-01-07 7:44 ` Greg Kroah-Hartman
2020-01-07 9:34 ` Pavel Machek [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=20200107093431.GA21375@amd \
--to=pavel@denx.de \
--cc=dmurphy@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jslaby@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).