[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvwmS790goxNhO33p63MAic_bV8dpY+iMVFhuCUrxCWcbw@mail.gmail.com>
Date: Fri, 3 Jan 2014 10:33:51 +0100
From: Richard Weinberger <richard.weinberger@...il.com>
To: Bryan Wu <cooloney@...il.com>
Cc: David Lang <david@...g.hm>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Joe Xue <lgxue@...mail.com>,
"rpurdie@...ys.net" <rpurdie@...ys.net>,
"rob@...dley.net" <rob@...dley.net>,
"milo.kim@...com" <milo.kim@...com>, "pavel@....cz" <pavel@....cz>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] Add LED pattern trigger
On Fri, Jan 3, 2014 at 1:14 AM, Bryan Wu <cooloney@...il.com> wrote:
> IMHO, firstly we should take this trigger into kernel, most time it
> works as a module. But we need to define a good interface between
> kernel and user space.
Put it in first place into the kernel such that it becomes ABI and
nobody is allowed
to remove it later?
Better design a sane interface such that such complex LED operations
can be achieved
in userspace using an helper library.
--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists