public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Milo Kim (Woogyom) <milo.kim@ti.com>
Cc: Bryan Wu <cooloney@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>, Aaro Koskinen <aaro.koskinen@iki.fi>,
	linux-kernel@vger.kernel.org
Subject: leds-lp5523: Broken commit db6eaf8388a413a5ee1b4547ce78506b9c6456b0
Date: Sun, 4 Aug 2013 11:46:03 +0200	[thread overview]
Message-ID: <201308041146.03970@pali> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 1070 bytes --]

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.

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...)

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2013-08-05  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04  9:46 Pali Rohár [this message]
2013-08-05  7:26 ` leds-lp5523: Broken commit db6eaf8388a413a5ee1b4547ce78506b9c6456b0 Kim, Milo
2013-08-05  7:31   ` Pali Rohár
2013-08-05 22:55     ` Bryan Wu

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=201308041146.03970@pali \
    --to=pali.rohar@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=cooloney@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milo.kim@ti.com \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    /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