- 09 May, 2014 20 commits
-
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org>
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
Andreas Larsson <andreas@gaisler.com> 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:
Javier Martinez Canillas <javier@dowhile0.org> 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:
Viresh Kumar <viresh.kumar@linaro.org> 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:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> 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:
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 14 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:
-
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:
-
