1. 16 1月, 2013 2 次提交
  2. 18 12月, 2012 1 次提交
    • K
      drivers/video/backlight/lp855x_bl.c: use generic PWM functions · 8cc9764c
      Kim, Milo 提交于
      The LP855x family devices support the PWM input for the backlight control.
       Period of the PWM is configurable in the platform side.  Platform
      specific functions are unnecessary anymore because generic PWM functions
      are used inside the driver.
      
      (PWM input mode)
      To set the brightness, new lp855x_pwm_ctrl() is used.
      If a PWM device is not allocated, devm_pwm_get() is called.
      The PWM consumer name is from the chip name such as 'lp8550' and 'lp8556'.
      To get the brightness value, no additional handling is required.
      Just the value of 'props.brightness' is returned.
      
      If the PWM driver is not ready while initializing the LP855x driver, it's
      OK.  The PWM device can be retrieved later, when the brightness value is
      changed.
      
      Documentation is updated with an example.
      
      [akpm@linux-foundation.org: coding-style simplification, per Thierry]
      Signed-off-by: NMilo(Woogyom) Kim <milo.kim@ti.com>
      Cc: Thierry Reding <thierry.reding@avionic-design.de>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Bryan Wu <bryan.wu@canonical.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8cc9764c
  3. 15 12月, 2012 2 次提交
  4. 10 12月, 2012 1 次提交
  5. 07 12月, 2012 4 次提交
  6. 06 12月, 2012 2 次提交
  7. 04 12月, 2012 2 次提交
    • O
      iommu/omap: Adapt to runtime pm · ebf7cda0
      Omar Ramirez Luna 提交于
      Use runtime PM functionality interfaced with hwmod enable/idle
      functions, to replace direct clock operations and sysconfig
      handling.
      
      Due to reset sequence, pm_runtime_[get|put]_sync must be used, to
      avoid possible operations with the module under reset. Because of
      this and given that the driver uses spin_locks to protect their
      critical sections, we must use pm_runtime_irq_safe in order for the
      runtime ops to be happy, otherwise might_sleep_if checks in runtime
      framework will complain.
      
      The remaining pm_runtime out of iommu_enable and iommu_disable
      corresponds to paths that can be accessed through debugfs, some of
      them doesn't work if the module is not enabled first, but in future
      if the mmu is idled withouth freeing, these are needed to debug.
      Signed-off-by: NOmar Ramirez Luna <omar.luna@linaro.org>
      Tested-by: NOhad Ben-Cohen <ohad@wizery.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NJoerg Roedel <joro@8bytes.org>
      ebf7cda0
    • O
      iommu/omap: Migrate to hwmod framework · 72b15b6a
      Omar Ramirez Luna 提交于
      Use hwmod data and device attributes to build and register an
      omap device for iommu driver.
      
       - Update the naming convention in isp module.
       - Remove unneeded check for number of resources, as this is now
         handled by omap_device and prevents driver from loading.
       - Now unused, remove platform device and resource data, handling
         of sysconfig register for softreset purposes, use default
         latency structure.
       - Use hwmod API for reset handling.
      Signed-off-by: NOmar Ramirez Luna <omar.luna@linaro.org>
      Tested-by: NOhad Ben-Cohen <ohad@wizery.com>
      Signed-off-by: NJoerg Roedel <joro@8bytes.org>
      72b15b6a
  8. 30 11月, 2012 1 次提交
  9. 29 11月, 2012 1 次提交
  10. 22 11月, 2012 1 次提交
  11. 21 11月, 2012 2 次提交
  12. 20 11月, 2012 11 次提交
  13. 19 11月, 2012 1 次提交
  14. 17 11月, 2012 1 次提交
  15. 16 11月, 2012 2 次提交
  16. 15 11月, 2012 3 次提交
  17. 14 11月, 2012 1 次提交
  18. 12 11月, 2012 1 次提交
  19. 08 11月, 2012 1 次提交