From: Pavel Machek <pavel@ucw.cz>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Richard Purdie" <rpurdie@rpsys.net>,
"Jacek Anaszewski" <j.anaszewski@samsung.com>,
"Felipe Balbi" <balbi@kernel.org>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Peter Chen" <hzpeterchen@gmail.com>,
linux-usb@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
"Jonathan Corbet" <corbet@lwn.net>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Stephan Linz" <linz@li-pro.net>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:LED SUBSYSTEM" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH V4] leds: trigger: Introduce an USB port trigger
Date: Mon, 10 Oct 2016 16:25:05 +0200 [thread overview]
Message-ID: <20161010142505.GA26643@amd> (raw)
In-Reply-To: <20160825080546.27182-1-zajec5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hi!
> This commit adds a new trigger responsible for turning on LED when USB
> device gets connected to the specified USB port. This can can useful for
> various home routers that have USB port(s) and a proper LED telling user
> a device is connected.
>
> The trigger gets its documentation file but basically it just requires
> specifying USB port in a Linux format (e.g. echo 1-1 > new_port).
>
> During work on this trigger there was a plan to add DT bindings for it,
> but there wasn't an agreement on the format yet. This can be worked on
> later, a sysfs interface is needed anyway for platforms not using DT.
>
> Another planned feature is support for LED reacting to the USB activity.
> This can be implemented with another sysfs file for setting mode. The
> default mode wouldn't change so there won't be ABI breakage and such
> feature can be safely implemented later.
Actually... USB device plugs/unplugs are pretty rare events... Can we
just do this in userspace using udevd?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-10-10 14:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 8:03 [PATCH V4] leds: trigger: Introduce an USB port trigger Rafał Miłecki
2016-08-25 12:49 ` Greg KH
2016-08-26 15:38 ` Rafał Miłecki
2016-08-30 12:05 ` Greg KH
2016-08-30 20:28 ` Rafał Miłecki
2016-08-30 20:54 ` Alan Stern
2016-08-30 21:14 ` Rafał Miłecki
2016-08-31 18:23 ` Alan Stern
2016-08-31 19:00 ` Rafał Miłecki
2016-09-01 5:25 ` Rafał Miłecki
2016-09-01 7:26 ` Jacek Anaszewski
2016-09-01 14:36 ` Alan Stern
2016-09-02 6:54 ` Jacek Anaszewski
[not found] ` <caccb909-bf51-8f67-cd57-de407e576afc-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-09-02 14:33 ` Alan Stern
2016-09-03 15:06 ` Jacek Anaszewski
2016-09-03 15:17 ` Alan Stern
2016-09-03 19:12 ` Jacek Anaszewski
2016-09-04 0:24 ` Alan Stern
2016-09-05 9:28 ` Rafał Miłecki
2016-10-10 14:25 ` Pavel Machek
2016-10-10 14:25 ` 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=20161010142505.GA26643@amd \
--to=pavel@ucw.cz \
--cc=balbi@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=corbet@lwn.net \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hzpeterchen@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linz@li-pro.net \
--cc=rafal@milecki.pl \
--cc=rpurdie@rpsys.net \
--cc=zajec5@gmail.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 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).