- 24 Jun, 2013 4 commits
-
-
Patrice Chotard authored
- allow to get output GPIO value - as there is no GPIO0 on ABX500, use correct offset with abx500_gpio_get_bit() Signed-off-by:
Patrice Chotard <patrice.chotard@st.com> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org>
-
Patrice Chotard authored
- Update abx500_pin_config_set() in order to take in account PIN_CONFIG_BIAS_DISABLE state to disable pull up or pull down. - Rework error path. Signed-off-by:
-
Patrice Chotard authored
We use the same way to define pin muxing and pin configuration than for nomadik. So pickup code from pinctrl_nomadik.c to be able to implement pin multiplexing and pin configuration using the device tree. Pin configuration uses generic parsing code. Signed-off-by:
Gabriel Fernandez <gabriel.fernandez@st.com> Signed-off-by:
-
Laurent Pinchart authored
Fix a compilation error caused by pinconf_generic_parse_dt_config() not being defined on !CONFIG_OF platforms by guarding the whole DT node parsing code with #ifdef CONFIG_OF. Defining a pinconf_generic_parse_dt_config() on !CONFIG_OF would have been possible as well, but would have resulted in a larger code size on !CONFIG_OF platforms (such as arch/sh). Signed-off-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Reviewed-by:
Simon Horman <horms+renesas@verge.net.au> Signed-off-by:
-
- 18 Jun, 2013 10 commits
-
-
Mathias Nyman authored
Add support for gpio on Intel BayTrail platforms. BayTrail supports 3 banks of gpios called SCORE, NCORE ans SUS with 102, 28 and 44 gpio pins. Supports gpio interrupts and ACPI gpio events Pins may be muxed to alternate function instead of gpio by firmware. This driver does not touch the pin muxing and expect firmare to set pin muxing and pullup/down properties properly. Signed-off-by:
Mathias Nyman <mathias.nyman@linux.intel.com> Signed-off-by:
-
James Hogan authored
The kerneldoc comment for struct pinconf_ops was missing pin_config_dbg_parse_modify, and instead described pin_config_group_dbg_set (which is presumably an old name for the same function). Rename it in the kerneldoc comment so they match. Signed-off-by:
James Hogan <james.hogan@imgtec.com> Signed-off-by:
-
Sachin Kamat authored
Symbols referenced only in this file are made static. Signed-off-by:
Sachin Kamat <sachin.kamat@linaro.org> Cc: Patrice Chotard <patrice.chotard@st.com> Signed-off-by:
-
Sachin Kamat authored
'spear310_o2p' is referenced only in this file. Signed-off-by:
Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by:
-
Sachin Kamat authored
Some symbols referenced only in this file are made static. Signed-off-by:
-
Sachin Kamat authored
'bcm2835_gpio_pins' is used only in this file. Signed-off-by:
-
Laurent Pinchart authored
Signed-off-by:
Heiko Stuebner <heiko@sntech.de> Signed-off-by:
-
Laurent Pinchart authored
Support device instantiation through the device tree. The compatible property is used to select the SoC pinmux information. Set the gpio_chip device field to the PFC device to enable automatic GPIO OF support. Cc: devicetree-discuss@lists.ozlabs.org Signed-off-by:
-
Laurent Pinchart authored
Platform data isn't used, support can thus be removed. Signed-off-by:
-
Wei Yongjun authored
Add the missing unlock before return from function pinctrl_find_gpio_range_from_pin() in the error handling case. Introduced by commit 2ff3477efd7086544b9e298fc63afab0645921b4. (pinctrl: add pin list based GPIO ranges) Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Signed-off-by:
-
- 17 Jun, 2013 16 commits
-
-
Doug Anderson authored
A level-triggered interrupt should be acked after the interrupt line becomes inactive and before it is unmasked, or else another interrupt will be immediately triggered. Acking before or after calling the handler is not enough. Signed-off-by:
Luigi Semenzato <semenzato@chromium.org> Signed-off-by:
Doug Anderson <dianders@chromium.org> Acked-by:
Tomasz Figa <t.figa@samsung.com> Signed-off-by:
-
Doug Anderson authored
It's convenient if get_maintainer suggests sending samsung/exynos pinctrl changes to linux-samsung-soc and to Tomasz and Thomas. Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Acked-by:
Olof Johansson <olof@lixom.net> Acked-by:
Kukjin Kim <kgene.kim@samsung.com> Signed-off-by:
-
Arnd Bergmann authored
The three functions pinctrl_pm_select_default_state, pinctrl_pm_select_sleep_state, and pinctrl_pm_select_idle_state are used in drivers that can be loadable modules, and should be exported. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Heiko Stübner authored
Change the rockchip pinctrl driver to handle the arguments to the pull pinconfig options correctly. So only accept non-0 values for the pull options as the rockchip pin-controller can only turn pulls on and off (this via BIAS_DISABLE). Signed-off-by:
-
Hebbar Gururaja authored
Make pinctrl-single able to handle suspend/resume events and change hogged pins states accordingly. Signed-off-by:
Hebbar Gururaja <gururaja.hebbar@ti.com> Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Fabio Baltieri authored
Removes the warnings: drivers/spi/spi-pl022.c: In function 'pl022_suspend_resources': drivers/spi/spi-pl022.c:2322:24: warning: unused variable 'pins_state' [-Wunused-variable] drivers/spi/spi-pl022.c:2321:6: warning: unused variable 'ret' [-Wunused-variable] drivers/spi/spi-pl022.c: In function 'pl022_resume_resources': drivers/spi/spi-pl022.c:2334:6: warning: unused variable 'ret' [-Wunused-variable] introduced in: f1c9cf07 spi: pl022: use pinctrl PM helpers Signed-off-by:
Fabio Baltieri <fabio.baltieri@linaro.org> Acked-by:
Mark Brown <broonie@linaro.org> Signed-off-by:
-
Maxime Ripard authored
Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by:
-
Maxime Ripard authored
It will allow us to have a cleaner separation between the data needed by the driver to work, and the core logic of the driver in itself, and will allow having too much noise in the core driver in the future. Signed-off-by:
-
Linus Walleij authored
It is counter-intuitive to have "0" mean disable in a boolean manner for electronic properties of pins such as pull-up and pull-down. Therefore, define that a pull-up/pull-down argument of 0 to such a generic option means that the pin is short-circuited to VDD or GROUND. Pull disablement shall be done using PIN_CONFIG_BIAS_DISABLE. Cc: James Hogan <james.hogan@imgtec.com> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by Heiko Stuebner <heiko@sntech.de> Acked-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Heiko Stübner authored
Allocating the temorary array in pinconf_generic_parse_dt_config on stack might cause problems later on, when the number of options grows over time. Therefore also allocate this array dynamically to be on the safe side. Suggested-by:
-
Heiko Stübner authored
This adds a shortcut when no valid pinconf properties are found in the parsed dt node, to set the values immediately and return. Suggested-by:
-
Heiko Stübner authored
The bias-pull-* options use values > 0 to indicate that the pull should be activated and optionally also indicate the strength of the pull. Therefore use an default value of 1 for these options. Split the low-power-mode option into low-power-enable and -disable. Update the documentation to describe the param arguments better. Reported-by:
-
Christian Ruppert authored
The comment introduced with the recently added pinctrl_gpio_range.pins element was wrong. This corrects it. Thanks to Patrice Chotard for pointing this out. Signed-off-by:
Christian Ruppert <christian.ruppert@abilis.com> Signed-off-by:
-
Linus Walleij authored
This updates the GPIO range documentation with the API changes for sparse/random/arbitrary pin-to-GPIO mappings. Reviewed-by:
Rob Landley <rob@landley.net> Signed-off-by:
-
Linus Walleij authored
The stubs for the !PINCTRL case were placed in the wrong part of the file, causing breakage in linux-next when compiling SH without pinctrl. Fix it up by moving the stubs to the right place. Signed-off-by: -
Christian Ruppert authored
Traditionally, GPIO ranges are based on consecutive ranges of both GPIO and pin numbers. This patch allows for GPIO ranges with arbitrary lists of pin numbers. Signed-off-by:
-
- 16 Jun, 2013 10 commits
-
-
Doug Anderson authored
This patch does nothing but reorder the functions to improve the readability of a future patch. Signed-off-by:
-
Doug Anderson authored
The patch: 19846950 pinctrl: samsung: Protect bank registers with a spinlock ...added spinlocks to protect many accesses. However, the irq_mask and irq_unmask functions still do an unprotected read/modify/write. Add the spinlock there. Signed-off-by:
-
Patrice Chotard authored
pinctrl-abx500.c: In function 'abx500_gpio_dbg_show_one': pinctrl-abx500.c:534:14: warning: 'pud' may be used uninitialized in this function [-Wuninitialized] Signed-off-by:
-
Heiko Stübner authored
This driver adds support the Cortex-A9 based SoCs from Rockchip, so at least the RK2928, RK3066 (a and b) and RK3188. Earlier Rockchip SoCs seem to use similar mechanics for gpio handling so should be supportable with relative small changes. Pull handling on the rk3188 is currently a stub, due to it being a bit different to the earlier SoCs. Pinmuxing as well as gpio (and interrupt-) handling tested on a rk3066a based machine. Signed-off-by:
-
Heiko Stübner authored
pinconf_generic_parse_dt_config() takes a node as input and generates an array of generic pinconfig values from the properties of this node. As I couldn't find a mechanism to count the number of properties of a node the function uses internally an array to accept one of parameter and copies the real present options to a smaller variable at its end. Signed-off-by:
-
Mugunthan V N authored
This utilize the new pinctrl core PM helpers to transition the driver to "default" and "sleep" states. Signed-off-by:
Mugunthan V N <mugunthanvnm@ti.com> Acked-by:
David S. Miller <davem@davemloft.net> Signed-off-by:
-
Mugunthan V N authored
This utilize the new pinctrl core PM helpers to transition the driver to "default" and "sleep" states. Signed-off-by:
-
Linus Walleij authored
This utilize the new pinctrl core PM helpers to transition the driver to "sleep" and "idle" states, cutting away some boilerplate code. Cc: Hebbar Gururaja <gururaja.hebbar@ti.com> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: Kevin Hilman <khilman@linaro.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Stephen Warren <swarren@wwwdotorg.org> Cc: Wolfram Sang <wsa@the-dreams.de> Acked-by:
Mark Brown <broonie@kernel.org> Signed-off-by:
-
Maxime Ripard authored
The A10 and A13 has a few pins that can be muxed into a particular function that can be used as an interrupt source. Add the available pins for such functions to the A10 and A13 description array. Signed-off-by:
-
Maxime Ripard authored
The port controller IP found in the Allwinner A10 and A13 can use few of the pins it manage as an interrupt source, called external interrupts in the datasheet. The number of these external interrupts are SoCs specific, but the current upper limit is 32. In order to work, the external interrupts' pins have to be muxed to a specific function to generate an interrupt. This patch adds the irqchip and the needed logic to use the PIO controller as an interrupt controller. Signed-off-by:
-
