1. 23 10月, 2013 1 次提交
  2. 27 8月, 2013 5 次提交
    • M
      leds: lp5523: remove unnecessary writing commands · 2f733cad
      Milo Kim 提交于
      This patch reduces the number of programming commands.
      
      (Count of sending commands)
      Old code: 32 + program size (32 counts for clearing program memory)
      New code: 32
      
      Pattern buffer is initialized to 0 in this function.
      Just update new program data and remaining buffers are filled with 0.
      So it's needless to clear whole area.
      Signed-off-by: NMilo Kim <milo.kim@ti.com>
      Signed-off-by: NBryan Wu <cooloney@gmail.com>
      2f733cad
    • M
      leds: lp5523: restore legacy device attributes · 45e611bf
      Milo Kim 提交于
      git commit db6eaf83
      (leds-lp5523: use generic firmware interface) causes an application conflict.
      This interface should be maintained for compatibility.
      
      Restored device attributes are 'engineN_mode', 'engineN_load' and
      'engineN_leds'. (N = 1, 2 or 3)
      A 'selftest' attribute macro is replaced with LP55xx common macro.
      Those are accessed when a LED pattern is run by an application.
      
      Use a mutex in lp5523_update_program_memory()
      : This function is called when an user-application writes a 'engineN_load' file
      or pattern data is loaded from generic firmware interface.
      So, writing program memory should be protected.
      If an error occurs on accessing this area, just it returns as -EINVAL quickly.
      This error code is exact same as old driver function, lp5523_do_store_load()
      because it should be kept for an user-application compatibility.
      Even the driver is changed, we can use the application without re-compiling
      sources.
      Reported-by: NPali Rohár <pali.rohar@gmail.com>
      Signed-off-by: NMilo Kim <milo.kim@ti.com>
      Signed-off-by: NBryan Wu <cooloney@gmail.com>
      45e611bf
    • M
      leds: lp5523: LED MUX configuration on initializing · 22460438
      Milo Kim 提交于
      LED MUX start and stop address should be updated in the program memory
      on LP5523 initialization.
      LED pattern doesn't work without additional MUX address configuration.
      This handling is done by new function, lp5523_init_program_engine().
      Eventually, it's called during device initialization, lp5523_post_init_device().
      
      This is a conflict after git commit 632418bf
      (leds-lp5523: clean up lp5523_configure()).
      So it should be fixed.
      
      Cc: Pali Rohár <pali.rohar@gmail.com>
      Signed-off-by: NMilo Kim <milo.kim@ti.com>
      Signed-off-by: NBryan Wu <cooloney@gmail.com>
      22460438
    • M
      leds: lp5523: make separate API for loading engine · b9e1730b
      Milo Kim 提交于
      lp5523_load_engine()
        It is called whenever the operation mode is changed to 'load'.
        It is used for simple operation mode change.
        It will be used when engine mode and LED selection is updated in later patch.
      
      lp5523_load_engine_and_select_page()
        Change the operation mode to 'load' and select program page number.
        This is used for programming a LED pattern at a time.
        So load_engine() is replaced with new API, load_engine_and_select_page()
        in lp5523_firmware_loaded().
      Signed-off-by: NMilo Kim <milo.kim@ti.com>
      Signed-off-by: NBryan Wu <cooloney@gmail.com>
      b9e1730b
    • J
      leds: use dev_get_platdata() · 87aae1ea
      Jingoo Han 提交于
      Use the wrapper function for retrieving the platform data instead of
      accessing dev->platform_data directly.
      Signed-off-by: NJingoo Han <jg1.han@samsung.com>
      Signed-off-by: NBryan Wu <cooloney@gmail.com>
      87aae1ea
  3. 21 6月, 2013 2 次提交
  4. 07 2月, 2013 28 次提交
  5. 29 11月, 2012 1 次提交
  6. 27 11月, 2012 3 次提交