[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A874F61F95741C4A9BA573A70FE3998F82E85CC4@DQHE06.ent.ti.com>
Date: Mon, 5 Aug 2013 07:26:46 +0000
From: "Kim, Milo" <Milo.Kim@...com>
To: Pali Rohár <pali.rohar@...il.com>
CC: Bryan Wu <cooloney@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pavel Machek <pavel@....cz>,
Aaro Koskinen <aaro.koskinen@....fi>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: leds-lp5523: Broken commit
db6eaf8388a413a5ee1b4547ce78506b9c6456b0
> Hello,
>
> git commit "leds-lp5523: use generic firmware interface"
> db6eaf8388a413a5ee1b4547ce78506b9c6456b0 introduced in kernel
> 3.10 changed user space API for modifing lp5523 led patterns via /sys.
>
> Before this commit there were sysfs attributes engineX_mode, engineX_load and
> engineX_leds (for every engine X).
>
> Now (after commit) there are sysfs attributes: select_engine, loading and
> data (see: 10c06d178df11b0b2b746321a80ea14241997127
> for description). Old sysfs attributes were removed.
>
> So commit db6eaf8388a413a5ee1b4547ce78506b9c6456b0 totally broke all existing
> userspace applications which use lp5523 leds.
>
> This also broke application MCE which is used on Nokia N900 phone for
> changing LED patterns in lp5523 led.
First of all, I'm really sorry for this conflict.
>
> I think that kernel api which is used by userspace applications (like
> attributes in /sys) should not be changed in way that totally broke existing
> applications.
>
> Can you fix this api problem? (maybe adding old sysfs attributes which would
> call new api function...)
I'll recover old sysfs attributes and implement them by using new functions.
Additionally, I'll do same works in LP5521 driver also.
Best Regards,
Milo
Powered by blists - more mailing lists