linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Milo Kim <woogyom.kim@gmail.com>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>, Milo Kim <milo.kim@ti.com>
Subject: Re: [PATCH 00/10] leds: lp5521,5523: restore device attributes for running LED patterns
Date: Fri, 25 Oct 2013 20:21:50 +0200	[thread overview]
Message-ID: <201310252021.51846@pali> (raw)
In-Reply-To: <CAK5ve-JrQhpwx9ZG1Kyhuxdc=dqfAaA6YBOMkDWYWrefeoeUxw@mail.gmail.com>

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

On Friday 25 October 2013 19:10:07 Bryan Wu wrote:
> On Fri, Oct 25, 2013 at 9:38 AM, Pali Rohár 
<pali.rohar@gmail.com> wrote:
> > On Tuesday 13 August 2013 23:04:14 Bryan Wu wrote:
> >> On Thu, Aug 8, 2013 at 12:59 AM, Milo Kim 
<woogyom.kim@gmail.com> wrote:
> >> > This patch-set resolves the application conflict by
> >> > restoring sysfs files.
> >> > 
> >> > For LP5521
> >> > 
> >> >   engine1/2/3_mode
> >> >   engine1/2/3_load
> >> > 
> >> > For LP5523
> >> > 
> >> >   engine1/2/3_mode
> >> >   engine1/2/3_load
> >> >   engine1/2/3_leds
> >> > 
> >> > Those attributes are accessed when LED pattern is run by
> >> > custom application. Those were removed when LED pattern
> >> > interface was changed to generic firmware interface.
> >> > Please refer to commits below.
> >> > 
> >> >   git commit 9ce7cb170f97f83a78dc948bf7d25690f15e1328
> >> >   (leds-lp5521: use generic firmware interface)
> >> >   
> >> >   git commit db6eaf8388a413a5ee1b4547ce78506b9c6456b0
> >> >   (leds-lp5523: use generic firmware interface)
> >> > 
> >> > Necessary attributes are restored in this patch-set.
> >> > 
> >> > (Other changes)
> >> > New data structure is added for handling values from/to
> >> > an application. Few code fixes for reducing writing I2C
> >> > commands.
> >> > Add LP55xx common macros for code refactoring.
> >> > Documentation updates.
> >> > 
> >> > You can also pull from the location below
> >> > This branch is based on 'for-next' of linux-leds.
> >> > 
> >> >   https://github.com/milokim/lp55xx.git
> >> >   resolve-missing-sysfs
> >> 
> >> Thanks, I've already merged the whole patchset in my -devel
> >> branch [1].
> >> 
> >> Pali, could you please help to test it on your hardware?
> >> Just grab my -devel branch and build then run.
> >> 
> >> Thanks,
> >> -Bryan
> > 
> > Hi, I see that all your patches are part of 3.12-rc5 kernel.
> > 
> > Now I tested this example led program:
> >     # Clearing LED-state to be sure
> >     echo "disabled" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine1_mode echo
> >     "disabled" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine2_mode echo 0
> >     > /sys/class/leds/lp5523:r/brightness
> >     echo 0 > /sys/class/leds/lp5523:g/brightness
> >     echo 0 > /sys/class/leds/lp5523:b/brightness
> >     
> >     # Setting yellow light pattern and running it
> >     echo "load" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine1_mode echo
> >     "000001100" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine1_leds echo
> >     "9d804000427f0d7f7f007f0042000000" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine1_load echo
> >     "load" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine2_mode echo
> >     "000000000" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine2_leds echo
> >     "9d800000" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine2_load echo
> >     "run" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine2_mode echo
> >     "run" >
> >     /sys/class/i2c-adapter/i2c-2/2-0032/engine1_mode echo
> >     20 > /sys/class/leds/lp5523:r/led_current
> >     echo 2 > /sys/class/leds/lp5523:g/led_current
> >     echo 0 > /sys/class/leds/lp5523:b/led_current
> > 
> > All sysfs entries exists and every echo returned 0.
> > 
> > But led does not start blinking that yellow ligh pattern.
> > So it not working on 3.12-rc5 kernel :-(
> 
> OK, great! Do you still remember which kernel version works on
> you system? Milo, do you have time to take a look? I bet it's
> a regression somewhere.
> 
> Thanks,
> -Bryan

I do not know which version. Now I tried pattern example from 
Documentation/leds/leds-lp55xx.txt which using new API.

echo 2 > /sys/class/i2c-adapter/i2c-2/2-0032/select_engine
echo 1 > /sys/class/firmware/lp5523/loading
echo "9d80400004ff05ff437f0000" > /sys/class/firmware/lp5523/data
echo 0 > /sys/class/firmware/lp5523/loading
echo 1 > /sys/class/i2c-adapter/i2c-2/2-0032/run_engine

But it failed at second command. In directory /sys/class/firmware/ 
I have only one file with name timeout. Nothing more, no lp5523 
folder.

Any idea who and when creating that lp5523 folder?

-- 
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-10-25 18:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  7:59 [PATCH 00/10] leds: lp5521,5523: restore device attributes for running LED patterns Milo Kim
2013-08-08  7:59 ` [PATCH 01/10] leds: lp55xx: add common data structure for program Milo Kim
2013-08-13 18:56   ` Bryan Wu
2013-08-18 22:57     ` Kim, Milo
2013-08-08  7:59 ` [PATCH 02/10] leds: lp55xx: add common macros for device attributes Milo Kim
2013-08-13 19:12   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 03/10] leds: lp5521: restore legacy " Milo Kim
2013-08-13 20:40   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 04/10] leds: lp5521: remove unnecessary writing commands Milo Kim
2013-08-13 20:42   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 05/10] leds: lp5523: make separate API for loading engine Milo Kim
2013-08-13 20:54   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 06/10] leds: lp5523: LED MUX configuration on initializing Milo Kim
2013-08-13 20:56   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 07/10] leds: lp5523: restore legacy device attributes Milo Kim
2013-08-13 20:58   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 08/10] leds: lp5523: remove unnecessary writing commands Milo Kim
2013-08-13 20:59   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 09/10] Documentation: leds-lp5521,lp5523: update device attribute information Milo Kim
2013-08-13 21:00   ` Bryan Wu
2013-08-08  7:59 ` [PATCH 10/10] leds: lp5562: use LP55xx common macros for device attributes Milo Kim
2013-08-13 21:00   ` Bryan Wu
2013-08-13 21:04 ` [PATCH 00/10] leds: lp5521,5523: restore device attributes for running LED patterns Bryan Wu
2013-10-25 16:38   ` Pali Rohár
2013-10-25 17:10     ` Bryan Wu
2013-10-25 18:21       ` Pali Rohár [this message]
2013-10-29 23:17         ` Bryan Wu
2013-11-08  5:15         ` Milo Kim
     [not found]           ` <CAK5ve-KQPxc-xWs1rh6KTgGK8VdLOgHqMLT8D90+mYt8P+xaew@mail.gmail.com>
2013-11-19 10:35             ` Pali Rohár
2013-11-19 19:20               ` Bryan Wu
2013-11-19 22:33                 ` Milo Kim

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=201310252021.51846@pali \
    --to=pali.rohar@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=milo.kim@ti.com \
    --cc=woogyom.kim@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).