- 09 May, 2014 11 commits
-
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Reviewed-by:
Javier Martinez Canillas <javier@dowhile0.org> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org>
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
Jason Cooper <jason@lakedaemon.net> Reviewed-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Jingoo Han authored
The site-specific OOM messages are unnecessary, because they duplicate the MM subsystem generic OOM message. Signed-off-by:
-
Arnd Bergmann authored
Commit 4df42de9d3e "gpio: omap: add a GPIO_OMAP option instead of using ARCH_OMAP" made it possible to build OMAP kernels without the GPIO driver, which at least on OMAP2 and OMAP3 causes build errors because of functions used by the platform power management code: arch/arm/mach-omap2/built-in.o: In function `omap_sram_idle': arch/arm/mach-omap2/pm24xx.c:129: undefined reference to `omap2_gpio_prepare_for_idle' arch/arm/mach-omap2/pm24xx.c:129: undefined reference to `omap2_gpio_resume_after_idle' We presumably always want the GPIO driver on OMAP, so this adds a slightly broader dependency and only allows disabling the driver only when no OMAP2PLUS platform is selected. However, it seems entirely reasonable to include the driver in build tests on other platforms, so we should also allow building it for COMPILE_TEST builds and select the required GENERIC_IRQ_CHIP that may not already be enabled on other platforms. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Javier Martinez Canillas <javier.martinez@collabora.co.uk> Signed-off-by:
-
- 03 May, 2014 4 commits
-
-
Javier Martinez Canillas authored
Using the BIT() macro instead of shifting bits makes the code less error prone and also more readable. Signed-off-by:
Alexandre Courbot <acourbot@nvidia.com> Signed-off-by:
-
Javier Martinez Canillas authored
Using the BIT() macro instead of shifting bits makes the code less error prone and also more readable. Signed-off-by:
-
Javier Martinez Canillas authored
Using the BIT() macro instead of shifting bits makes the code less error prone and also more readable. Signed-off-by:
-
Javier Martinez Canillas authored
Using the BIT() macro instead of shifting bits makes the code less error prone and also more readable. Signed-off-by:
-
- 02 May, 2014 2 commits
-
-
Thierry Reding authored
Add the GPIO-related device-managed functions to the list of functions in Documentation/driver-model/devres.txt. Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
-
Thierry Reding authored
The function is called gpiod_get(), not gpio_get(). Fix the kernel-doc comment to match the name. Signed-off-by:
-
- 28 Apr, 2014 23 commits
-
-
Thierry Reding authored
Many bindings use the -gpio suffix in property names. Support this in addition to the -gpios suffix when requesting GPIOs using the new descriptor-based API. Signed-off-by:
-
Yegor Yefremov authored
This patch implements gpio_chip's get_direction() routine, that lets other drivers get particular GPIOs direction using struct gpio_desc. Signed-off-by:
Yegor Yefremov <yegorslists@googlemail.com> Acked-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Tested-by:
Tony Lindgren <tony@atomide.com> Reviewed-by:
Kevin Hilman <khilman@linaro.org> Signed-off-by:
-
Thierry Reding authored
of_find_gpio() is always called under an IS_ENABLED(CONFIG_OF), so the dummy implementation provided for !OF configurations is not needed. Signed-off-by:
-
Linus Walleij authored
Some GPIO irqchip drivers exploit the irqdomain mapping function to set up the IRQ default type in the hardware, make sure that if we pass IRQ_TYPE_NONE, no hardware setup whatsoever takes place (this should be the norm) until later when the IRQ gets utilized. Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Cc: linux-omap <linux-omap@vger.kernel.org> Tested-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Tested-by:
Nishanth Menon <nm@ti.com> Acked-by:
-
Axel Lin authored
This saves a few unwind code. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
Florian Fainelli <florian@openwrt.org> Signed-off-by:
-
Geert Uytterhoeven authored
This is just enough to automatically enable the functional clock, if present. Clock management during suspend/resume is still to be added. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Cc: linux-gpio@vger.kernel.org Acked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Axel Lin authored
Make the module alias match the platform device name, so gpio-kempld module should now autoload correctly. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Signed-off-by:
-
Geert Uytterhoeven authored
Signed-off-by:
-
Axel Lin authored
Signed-off-by:
-
Axel Lin authored
Signed-off-by:
-
Axel Lin authored
The memory for ts is allocated by devm_kzalloc now, so the kfree is not required. Signed-off-by:
Juergen Beisert <jbe@pengutronix.de> Reviewed-by:
-
Alexander Shiyan authored
This patch converts GE I/O FPGA GPIO driver to platform driver. Signed-off-by:
Alexander Shiyan <shc_work@mail.ru> Signed-off-by:
-
Linus Walleij authored
As demonstrated by commit 390d82e3 "gpiolib: ACPI: remove gpio_to_desc() usage" gpio_to_desc() must die. Replace one of its usage by the newly-introduced gpiochip_get_desc() function. Reviewed-by:
-
Axel Lin authored
Read gpio output value from ZEVIO_GPIO_OUTPUT. The spin_lock is required to ensure the direction is not changed before reading input/ouput value. Signed-off-by:
-
Linus Walleij authored
Another feature that is duplicated in a number of GPIO irqchips is that these cascades IRQs are assigned their own lock class so as to avoid warnings about lockdep recursions. Do this also in the generic GPIO irqchip helpers for smooth transition to this core infrastructure. Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: -
Daniel Krueger authored
According to the datasheet, writing to the level register has no effect when GPIO is programmed as input. Actually the the level register is read-only when configured as input. Thus presetting the output level before switching to output is _NOT_ possible. Any writes are lost! Hence we set the level after configuring the GPIO as output. But we cannot prevent a short low pulse if direction is set to high and an external pull-up is connected. Signed-off-by:
Daniel Krueger <daniel.krueger@systec-electronic.com> Signed-off-by:
Alexander Stein <alexander.stein@systec-electronic.com> Signed-off-by:
-
Axel Lin authored
This is a DT-only driver and it will be built only when CONFIG_OF is set. So it's pointless to use of_match_ptr. Signed-off-by:
-
Sebastian Andrzej Siewior authored
The driver calls irq_alloc_domain_generic_chips() which creates a gc and adds it to gc_list. The driver later then calls irq_setup_generic_chip() which also initializes the gc and adds it to the gc_list() and this corrupts the list. Enable LIST_DEBUG and you see the kernel complain. This isn't required, irq_alloc_domain_generic_chips() did the init. Signed-off-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Tested-by:
Alan Tull <delicious.quinoa@gmail.com> Signed-off-by:
-
Javier Martinez Canillas authored
I've been maintaining this driver by fixing all issues found while migrating OMAP2+ towards Device Tree based booting and keeping it up-to-date by using the latest infraestructure that is provided by the GPIO subsystem. It would be nice if people know that I care about this driver and put me in copy when sending patches for it. Signed-off-by:
-
Javier Martinez Canillas authored
Converts the GPIO OMAP driver to register its chained irq handler and irqchip using the helpers in the gpiolib core. Signed-off-by:
-
Javier Martinez Canillas authored
The ARCH_OMAP config option was used to built the GPIO OMAP driver but this is not consistent with the rest of the GPIO drivers that have their own Kconfig option. Also, this make it harder to add dependencies or reverse dependencies (i.e: select) since that would mean touching the sub-arch config option. So is better to add a boolean Kconfig option for this driver that defaults to true if ARCH_OMAP is enabled. Signed-off-by:
-
Javier Martinez Canillas authored
The gpiochip_add() function can fail if the chip cannot be registered so the return value has to be checked and the error propagated in case it happens. Signed-off-by:
-
Javier Martinez Canillas authored
The GPIO OMAP driver supports different OMAP SoC families and not all of them have the needed support to use the linear IRQ domain mapping like OMAP1 that use the legacy domain mapping. But this special check is not necessary since the simple IRQ domain mapping is able to handle both cases. Having a zero IRQ offset will be interpreted as a linear domain case while a non-zero value will be interpreted as a legacy domain case. Signed-off-by:
-
