14 Jan, 2012

1 commit

  • * 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6: (59 commits)
    rtc: max8925: Add function to work as wakeup source
    mfd: Add pm ops to max8925
    mfd: Convert aat2870 to dev_pm_ops
    mfd: Still check other interrupts if we get a wm831x touchscreen IRQ
    mfd: Introduce missing kfree in 88pm860x probe routine
    mfd: Add S5M series configuration
    mfd: Add s5m series irq driver
    mfd: Add S5M core driver
    mfd: Improve mc13xxx dt binding document
    mfd: Fix stmpe section mismatch
    mfd: Fix stmpe build warning
    mfd: Fix STMPE I2c build failure
    mfd: Constify aat2870-core i2c_device_id table
    gpio: Add support for stmpe variant 801
    mfd: Add support for stmpe variant 801
    mfd: Add support for stmpe variant 610
    mfd: Add support for STMPE SPI interface
    mfd: Separate out STMPE controller and interface specific code
    misc: Remove max8997-muic sysfs attributes
    mfd: Remove unused wm831x_irq_data_to_mask_reg()
    ...

    Fix up trivial conflict in drivers/leds/Kconfig due to addition of
    LEDS_MAX8997 and LEDS_TCA6507 next to each other.

    Linus Torvalds
     

11 Jan, 2012

1 commit

  • TI's TCA6507 is the LED driver in the GTA04 Openmoko motherboard. The
    driver provides full support for brightness levels and hardware blinking.

    This driver can drive each of 7 outputs as an LED or a GPIO output,
    and provides hardware-assist blinking.

    [akpm@linux-foundation.org: fix __mod_i2c_device_table alias]
    [akpm@linux-foundation.org: coding-style fixes]
    Signed-off-by: NeilBrown
    Cc: Richard Purdie
    Cc: Randy Dunlap
    Cc: Dan Carpenter
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    NeilBrown
     

09 Jan, 2012

1 commit


24 Nov, 2011

1 commit


01 Nov, 2011

1 commit

  • Add V2 of the LED driver for a single timer channel for the TPU hardware
    block commonly found in Renesas SoCs.

    The driver has been written with optimal Power Management in mind, so to
    save power the LED is driven as a regular GPIO pin in case of maximum
    brightness and power off which allows the TPU hardware to be idle and
    which in turn allows the clocks to be stopped and the power domain to be
    turned off transparently.

    Any other brightness level requires use of the TPU hardware in PWM mode.
    TPU hardware device clocks and power are managed through Runtime PM.
    System suspend and resume is known to be working - during suspend the LED
    is set to off by the generic LED code.

    The TPU hardware timer is equipeed with a 16-bit counter together with an
    up-to-divide-by-64 prescaler which makes the hardware suitable for
    brightness control. Hardware blink is unsupported.

    The LED PWM waveform has been verified with a Fluke 123 Scope meter on a
    sh7372 Mackerel board. Tested with experimental sh7372 A3SP power domain
    patches. Platform device bind/unbind tested ok.

    V2 has been tested on the DS2 LED of the sh73a0-based AG5EVM.

    [axel.lin@gmail.com: include linux/module.h]
    Signed-off-by: Magnus Damm
    Cc: Paul Mundt
    Cc: Richard Purdie
    Cc: Grant Likely
    Signed-off-by: Axel Lin
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Magnus Damm
     

28 Oct, 2011

1 commit


28 Sep, 2011

1 commit

  • There are numerous broken references to Documentation files (in other
    Documentation files, in comments, etc.). These broken references are
    caused by typo's in the references, and by renames or removals of the
    Documentation files. Some broken references are simply odd.

    Fix these broken references, sometimes by dropping the irrelevant text
    they were part of.

    Signed-off-by: Paul Bolle
    Signed-off-by: Jiri Kosina

    Paul Bolle
     

21 Sep, 2011

1 commit

  • This new driver replaces the old PCEngines Alix 2/3 LED driver with a
    new driver that controls the LEDs through the leds-gpio driver. The
    old driver accessed GPIOs directly, which created a conflict and
    prevented also loading the cs5535-gpio driver to read other GPIOs on
    the Alix board. With this new driver, we hook into leds-gpio which in
    turn uses GPIO to control the LEDs and therefore it's possible to
    control both the LEDs and access onboard GPIOs

    Driver is moved to platform/geode as requested by Grant and any other
    geode initialisation modules should move here also

    This driver is inspired by leds-net5501.c by Alessandro Zummo.

    Ideally, leds-net5501.c should also be moved to platform/geode.
    Additionally the driver relies on parts of the patch: 7f131cf3ed ("leds:
    leds-alix2c - take port address from MSR) by Daniel Mack to perform
    detection of the Alix board.

    [akpm@linux-foundation.org: include module.h]

    Signed-off-by: Ed Wildgoose
    Cc: git@wildgooses.com
    Cc: Alessandro Zummo
    Cc: Daniel Mack
    Cc: Ingo Molnar
    Cc: "H. Peter Anvin"
    Cc: Richard Purdie
    Reviewed-by: Grant Likely
    Signed-off-by: Andrew Morton
    Signed-off-by: Thomas Gleixner

    Ed Wildgoose
     

26 Jul, 2011

1 commit

  • We call led_classdev_register/led_classdev_unregister in
    create_netxbig_led/delete_netxbig_led, thus make LEDS_NETXBIG depend on
    LEDS_CLASS.

    This patch fixes below build error if LEDS_CLASS is not configured.

    LD .tmp_vmlinux1
    drivers/built-in.o: In function `create_netxbig_led':
    drivers/leds/leds-netxbig.c:350: undefined reference to `led_classdev_register'
    drivers/leds/leds-netxbig.c:361: undefined reference to `led_classdev_unregister'
    drivers/built-in.o: In function `delete_netxbig_led':
    drivers/leds/leds-netxbig.c:313: undefined reference to `led_classdev_unregister'

    Signed-off-by: Axel Lin
    Cc: Richard Purdie
    Acked-by: Simon Guinot
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Axel Lin
     

23 Jul, 2011

1 commit

  • * 'gpio/next' of git://git.secretlab.ca/git/linux-2.6: (61 commits)
    gpio/mxc/mxs: fix build error introduced by the irq_gc_ack() renaming
    mcp23s08: add i2c support
    mcp23s08: isolate spi specific parts
    mcp23s08: get rid of setup/teardown callbacks
    gpio/tegra: dt: add binding for gpio polarity
    mcp23s08: remove unused work queue
    gpio/da9052: remove a redundant assignment for gpio->da9052
    gpio/mxc: add device tree probe support
    ARM: mxc: use ARCH_NR_GPIOS to define gpio number
    gpio/mxc: get rid of the uses of cpu_is_mx()
    gpio/mxc: add missing initialization of basic_mmio_gpio shadow variables
    gpio: Move mpc5200 gpio driver to drivers/gpio
    GPIO: DA9052 GPIO module v3
    gpio/tegra: Use engineering names in DT compatible property
    of/gpio: Add new method for getting gpios under different property names
    gpio/dt: Refine GPIO device tree binding
    gpio/ml-ioh: fix off-by-one for displaying variable i in dev_err
    gpio/pca953x: Deprecate meaningless device-tree bindings
    gpio/pca953x: Remove dynamic platform data pointer
    gpio/pca953x: Fix IRQ support.
    ...

    Linus Torvalds
     

16 Jun, 2011

3 commits

  • Seems when a config option does not have a dependency of the menuconfig,
    it messes the display of the rest configs, even if it's a hidden one.

    Signed-off-by: Eric Miao
    Cc: Richard Purdie
    Cc: Valdis Kletnieks
    Cc: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Miao
     
  • Commit 4440673a95e6 ("leds: provide helper to register "leds-gpio"
    devices") broke the display of the NEW_LEDS menu as it didn't depend on
    NEW_LEDS and so made "LED drivers" and "LED Triggers" appear at the same
    level as "LED Support" instead of below it as it was before 4440673a.

    Moving LEDS_GPIO_REGISTER out of the menuconfig NEW_LEDS fixes this
    unintended side effect.

    Reported-by: Axel Lin
    Signed-off-by: Uwe Kleine-König
    Cc: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Uwe Kleine-König
     
  • We call led_classdev_unregister/led_classdev_register in
    asic3_led_remove/asic3_led_probe, thus make LEDS_ASIC3 depend on
    LEDS_CLASS.

    This patch fixes below build error if LEDS_CLASS is not configured.

    LD .tmp_vmlinux1
    drivers/built-in.o: In function `asic3_led_remove':
    clkdev.c:(.devexit.text+0x1860): undefined reference to `led_classdev_unregister'
    drivers/built-in.o: In function `asic3_led_probe':
    clkdev.c:(.devinit.text+0xcee8): undefined reference to `led_classdev_register'
    make: *** [.tmp_vmlinux1] Error 1

    Signed-off-by: Axel Lin
    Cc: Paul Parsons
    Cc: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Axel Lin
     

04 Jun, 2011

1 commit


27 May, 2011

1 commit

  • Add LED support for the HTC ASIC3. Underlying support is provided by the mfd/asic3 and leds/leds-asic3 drivers. An example configuration is provided by the pxa/hx4700 platform.

    Signed-off-by: Paul Parsons
    Signed-off-by: Samuel Ortiz

    Paul Parsons
     

25 May, 2011

3 commits

  • This function makes a deep copy of the platform data to allow it to live
    in init memory. For a kernel that supports several machines and so
    includes the definition for several leds-gpio devices this saves quite
    some memory because all but one definition can be free'd after boot.

    As the function is used by arch code it must be builtin and so cannot go
    into leds-gpio.c.

    [akpm@linux-foundation.org: s/CONFIG_LED_REGISTER_GPIO/CONFIG_LEDS_REGISTER_GPIO/]
    Signed-off-by: Uwe Kleine-König
    Cc: Russell King
    Acked-by: Richard Purdie
    Cc: Fabio Estevam
    Cc: Sascha Hauer
    Tested-by: H Hartley Sweeten
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Uwe Kleine-König
     
  • The H1940 machine now uses leds-gpio and leds-h1940 has no users anymore.

    Signed-off-by: Vasily Khoruzhick
    Cc: "Arnaud Patard (Rtp)"
    Cc: Ben Dooks
    Cc: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Vasily Khoruzhick
     
  • Allow unused leds on pca9532 to be used as gpio. The board I am working
    on now has no less than 6 pca9532 chips. One chips is used for only leds,
    one has 14 leds and 2 gpio and the rest of the chips are gpio only.

    There is also one board in mainline which could use this capabilty;
    arch/arm/mach-iop32x/n2100.c
    232 { .type = PCA9532_TYPE_NONE }, /* power OFF gpio */
    233 { .type = PCA9532_TYPE_NONE }, /* reset gpio */

    This patch defines a new pin type, PCA9532_TYPE_GPIO, and registers a
    gpiochip if any pin has this type set. The gpio will registers all chip
    pins but will filter on gpio_request.

    [randy.dunlap@oracle.com: fix build when GPIOLIB is not enabled]
    Signed-off-by: Joachim Eastwood
    Reviewed-by: Wolfram Sang
    Reviewed-by: H Hartley Sweeten
    Cc: Richard Purdie
    Cc: Grant Likely
    Signed-off-by: Randy Dunlap
    Cc: Jan Weitzel
    Cc: Juergen Kilb
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Joachim Eastwood
     

23 Mar, 2011

1 commit

  • Simple backlight driver for National Semiconductor LM3530. Presently only
    manual mode is supported, PWM and ALS support to be added.

    Signed-off-by: Shreshtha Kumar Sahu
    Cc: Linus Walleij
    Cc: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Shreshtha Kumar Sahu
     

03 Dec, 2010

1 commit

  • It's not useful to build LED triggers when there's no LEDs that can be
    triggered by them. Therefore, fix up the dependencies so that this
    cannot happen, and fix a few users that select triggers to depend on
    LEDS_CLASS as well (there is also one user that also selects LEDS_CLASS,
    which is OK).

    Signed-off-by: Johannes Berg
    Reported-by: Randy Dunlap
    Acked-by: Randy Dunlap
    Tested-by: Ingo Molnar
    Cc: Arnd Hannemann
    Cc: Michal Hocko
    Cc: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Johannes Berg
     

12 Nov, 2010

2 commits

  • Provide configuration and compilation support for LP5521 and LP5523

    Signed-off-by: Samu Onkalo
    Cc: Richard Purdie
    Cc: Jean Delvare
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Samu Onkalo
     
  • Currently, blinking LEDs can be awkward because it is not guaranteed that
    all LEDs implement blinking. The trigger that wants it to blink then
    needs to implement its own timer solution.

    Rather than require that, add led_blink_set() API that triggers can use.
    This function will attempt to use hw blinking, but if that fails
    implements a timer for it. To stop blinking again, brightness_set() also
    needs to be wrapped into API that will stop the software blink.

    As a result of this, the timer trigger becomes a very trivial one, and
    hopefully we can finally see triggers using blinking as well because it's
    always easy to use.

    Signed-off-by: Johannes Berg
    Acked-by: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Johannes Berg
     

08 Oct, 2010

1 commit


20 Sep, 2010

1 commit


17 Jul, 2010

1 commit

  • This patch add a LED class driver for the dual-GPIO LEDs found on the
    Network Space v2 board (and parents). This include Internet Space v2,
    Network Space (Max) v2 and d2 Network v2 boards.

    This dual-GPIO LED is wired to a CPLD and can blink in relation with the
    SATA activity. The driver expose this capability through a "sata" sysfs
    attribute.

    Signed-off-by: Simon Guinot
    Signed-off-by: Nicolas Pitre

    Simon Guinot
     

28 May, 2010

1 commit


26 May, 2010

2 commits

  • This add basic led support for Freescale MC13783 PMIC.

    Signed-off-by: Philippe Rétornaz
    Signed-off-by: Richard Purdie

    Philippe Rétornaz
     
  • It is based on the previously submitted code by Alessandro Zummo, but is
    changed to use the new GPIO driver with 2.6.33, and the driver has been
    moved to drivers/leds where it belongs.

    [akpm@linux-foundation.org: coding-style fixes]
    [randy.dunlap@oracle.com: fix net5501 kconfig]
    Signed-off-by: Bjarke Istrup Pedersen
    Signed-off-by: Randy Dunlap
    Signed-off-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Richard Purdie

    Bjarke Istrup Pedersen
     

17 Mar, 2010

3 commits

  • This patch adds an LED driver to support the Dell Activity LED on the
    Dell Latitude 2100 netbook and future products to come. The Activity LED
    is visible externally in the lid so classroom instructors can observe it
    from a distance. The driver uses the sysfs led_class and provides a
    standard LED interface.

    Signed-off by: Bob Rodgers
    Signed-off-by: Louis Davis
    Signed-off-by: Jim Dailey , Developers
    Acked-by: Matthew Garrett
    Acked-by: Dmitry Torokhov
    Signed-off-by: Richard Purdie

    Bob Rodgers
     
  • Remove the need for "depends on LEDS_CLASS" by wrapping the affected
    config options in an if/endif block. Similar for "depends on LEDS_TRIGGERS".

    LEDS_COBALT_RAQ still has a "depends on LEDS_CLASS=y" since it cannot
    be selected to build as a module.

    Signed-off-by: H Hartley Sweeten
    Signed-off-by: Richard Purdie

    H Hartley Sweeten
     
  • The ALIX2 LED driver and the CS5535 GPIO drivers share the same I/O
    range which causes a conflict if they're both enabled. Fix this for now
    by adding Kconfig dependencies. While at it, also drop the EXPERIMENTAL
    flag, as the code has been around for awhile already.

    Note that this is a hack. At some point, a real platform support for
    this board should be added which handles the LEDs via the leds-gpio
    driver.

    Signed-off-by: Daniel Mack
    Signed-off-by: Richard Purdie

    Daniel Mack
     

08 Mar, 2010

1 commit


17 Dec, 2009

1 commit

  • This driver provides an interface for controlling LEDs (or vibrators)
    connected to PMICs for which there is a regulator framework driver.

    This driver can be used, for instance, to control vibrator on all Motorola EZX
    phones using the pcap-regulator driver services.

    Signed-off-by: Antonio Ospite
    Reviewed-by: Mark Brown
    Signed-off-by: Richard Purdie

    Antonio Ospite
     

16 Dec, 2009

3 commits

  • Signed-off-by: Michael Hennerich
    Signed-off-by: Bryan Wu
    Signed-off-by: Mike Frysinger
    Signed-off-by: Richard Purdie

    Michael Hennerich
     
  • The LT3593 is a step-up DC/DC converter designed to drive up to ten
    white LEDs in series. The current flow can be set with a control pin.

    This driver controls any number of such devices connected on generic
    GPIOs and exports the function as as platform_driver.

    The gpio_led platform data struct definition is reused for this purpose.

    Successfully tested on a PXA embedded board.

    Signed-off-by: Daniel Mack
    Signed-off-by: Richard Purdie

    Daniel Mack
     
  • This code is based on a driver that came in the "Open-source
    and GPL components" download here:

    http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Server+Products&ProductLine=Intel%C2%AE+Storage+Systems&ProductProduct=Intel%C2%AE+Entry+Storage+System+SS4200-E&OSVersion=OS+Independent

    It was in a file called nasgpio.c inside of a second zip file
    called SS4200-E_Linux_SIO_Driver-v1.4.zip and is based on this
    updated to use the LED subsystem with the ioctl and hardware
    monitor support removed.

    I don't have any need for brightness
    control, and its code is *completely* separate from the on/off
    controls implemented here. If anyone else wants it, I'd be
    happy to look into adding it, but I don't care enough for now.

    Except for the probe routines, I rewrote most of it. I also
    Note that I don't have any hardware documentation except for
    the original driver.

    Thanks go to Arjan for his help in getting the original source
    for this released and for chasing down some licensing issues.

    Signed-off-by: Dave Hansen
    Signed-off-by: Richard Purdie

    Dave Hansen
     

07 Sep, 2009

2 commits

  • Signed-off-by: Antonio Ospite
    Signed-off-by: Richard Purdie

    Antonio Ospite
     
  • The WM831x devices feature two software controlled status LEDs with
    hardware assisted blinking.

    The device can also autonomously control the LEDs based on a selection
    of sources. This can be configured at boot time using either platform
    data or the chip OTP. A sysfs file in the style of that for triggers
    allowing the control source to be configured at run time. Triggers
    can't be used here since they can't depend on the implementation details
    of a specific LED type.

    Signed-off-by: Mark Brown
    Signed-off-by: Richard Purdie

    Mark Brown
     

24 Jun, 2009

2 commits

  • LEDs driver for National Semiconductor LP3944 Funlight Chip
    http://www.national.com/pf/LP/LP3944.html

    This helper chip can drive up to 8 leds, with two programmable DIM
    modes; it could even be used as a gpio expander but this driver assumes
    it is used as a led controller.

    The DIM modes are used to set _blink_ patterns for leds, the pattern is
    specified supplying two parameters:
    - period: from 0s to 1.6s
    - duty cycle: percentage of the period the led is on, from 0 to 100

    LP3944 can be found on Motorola A910 smartphone, where it drives the rgb
    leds, the camera flash light and the displays backlights.

    Signed-off-by: Antonio Ospite
    Signed-off-by: Richard Purdie

    Antonio Ospite
     
  • Remove an orphan Kconfig entry (LEDS_LP5521)

    Signed-off-by: Richard Purdie

    Richard Purdie