27 Oct, 2015

2 commits


20 Oct, 2015

1 commit


29 Oct, 2014

1 commit


26 Sep, 2014

1 commit

  • To unify how we connect cascaded IRQ chips to parent IRQs, if
    NULL us passed as handler to the gpiochip_set_chained_irqchip()
    function, assume the chips is nested rather than chained, and
    we still get the parent set up correctly by way of this function
    call.

    Alter the drivers for tc3589x and stmpe to use this to set up
    their chained handlers as a demonstration of the usage.

    Signed-off-by: Linus Walleij

    Linus Walleij
     

29 Aug, 2014

1 commit

  • The current prototype of gpiochip_request_own_desc() requires to obtain
    a pointer to a descriptor. This is in contradiction to all other GPIO
    request schemes, and imposes an extra step of obtaining a descriptor to
    drivers. Most drivers actually cannot even perform that step since the
    function that does it (gpichip_get_desc()) is gpiolib-private.

    Change gpiochip_request_own_desc() to return a descriptor from a
    (chip, hwnum) tuple and update users of this function (currently
    gpiolib-acpi only).

    Signed-off-by: Alexandre Courbot
    Tested-by: Mika Westerberg
    Signed-off-by: Linus Walleij

    Alexandre Courbot
     

24 Jul, 2014

1 commit

  • Both functions were introduced to let gpio drivers request their own
    gpio pins. Without exporting the functions, this can however only be
    used by gpio drivers built into the kernel.

    Secondary impact is that the functions can not currently be used by
    platform initialization code associated with the gpio-pca953x driver.
    This code permits auto-export of gpio pins through platform data, but
    if this functionality is used, the module can no longer be unloaded due
    to the problem solved with the introduction of gpiochip_request_own_desc
    and gpiochip_free_own_desc.

    Export both function so they can be used from modules and from
    platform initialization code.

    Reviewed-by: Alexandre Courbot
    Reviewed-by: Mika Westerberg
    Signed-off-by: Guenter Roeck
    Signed-off-by: Linus Walleij

    Guenter Roeck
     

23 Jul, 2014

1 commit

  • gpio_lock/unlock_as_irq() are working with (chip, offset) arguments and
    are thus not using the old integer namespace. Therefore, there is no
    reason to have gpiod variants of these functions working with
    descriptors, especially since the (chip, offset) tuple is more suitable
    to the users of these functions (GPIO drivers, whereas GPIO descriptors
    are targeted at GPIO consumers).

    Signed-off-by: Alexandre Courbot
    Signed-off-by: Linus Walleij

    Alexandre Courbot
     

29 Apr, 2014

1 commit


03 Feb, 2014

1 commit


25 Nov, 2013

1 commit

  • gpiolib now exports a new descriptor-based interface which deprecates
    the older integer-based one. This patch documents this new interface and
    also takes the opportunity to brush-up the GPIO documentation a little
    bit.

    The new descriptor-based interface follows the same consumer/driver
    model as many other kernel subsystems (e.g. clock, regulator), so its
    documentation has similarly been splitted into different files.

    The content of the former documentation has been reused whenever it
    made sense; however, some of its content did not apply to the new
    interface anymore and have this been removed. Likewise, new sections
    like the mapping of GPIOs to devices have been written from scratch.

    The deprecated legacy-based documentation is still available, untouched,
    under Documentation/gpio/gpio-legacy.txt.

    Signed-off-by: Alexandre Courbot
    Signed-off-by: Linus Walleij

    Alexandre Courbot