An error occurred fetching the project authors.
- 11 Apr, 2013 1 commit
-
-
Alexander Shiyan authored
Memory for basic-mmio-gpio driver is allocated by the driver using it, whether it's the generic GPIO driver itself or another driver. In either case, the owner shall allocate and free the struct bgpio_chip it is using, preferably using a managed resource. Signed-off-by:
Alexander Shiyan <shc_work@mail.ru> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org>
-
- 10 Apr, 2013 8 commits
-
-
Rafael J. Wysocki authored
Commit 0d1c28a4 (gpiolib-acpi: Add ACPI5 event model support to gpio.) that added support for ACPI events signalled through GPIO interrupts covered only GPIO pins whose numbers are less than or equal to 255. However, there may be GPIO pins with numbers greater than 255 and the ACPI spec (ACPI 5.0, Section 5.6.5.1) requires the _EVT method to be used for handling events corresponding to those pins. Moreover, according to the spec, _EVT is the default mechanism for handling all ACPI events signalled through GPIO interrupts, so if the _Exx/_Lxx method is not present for the given pin, _EVT should be used instead. If present, though, _Exx/_Lxx take precedence over _EVT which shouldn't be executed in that case (ACPI 5.0, Section 5.6.5.3). Modify acpi_gpiochip_request_interrupts() to follow the spec as described above and add acpi_gpiochip_free_interrupts() needed to free interrupts associated with _EVT. Signed-off-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by:
Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by:
-
Axel Lin authored
The valid bank should be 0 ... ARRAY_SIZE(lpc32xx_gpiochip) - 1. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Signed-off-by:
-
Lars Poeschel authored
This converts the mcp23s08 driver to be able to be used with device tree. There is a "spi-present-mask" device tree property, that allows to use multiple of this spi chips on the same chipselect. v4: - removed the ability to specify the pullup from device tree - updated binding doc v3: - removed mcp,chips device tree property in favour of a mcp,spi-present-mask and a flag for the pullup of every gpio - seperated the match table. Now there is one for i2c and one for spi - do the of reading stuff on stack of the probe function - no devm any more v2: - squashed booth patches together - fixed build warning, when CONFIG_OF is not defined - use of_match_ptr macro for of_match_table Signed-off-by:Lars Poeschel <poeschel@lemonage.de> Signed-off-by:
-
Jon Hunter authored
When booting with device-tree the function pointer for detecting context loss is not populated. Ideally, the pm_runtime framework should be enhanced to allow a means for reporting context/state loss and we could avoid populating such function pointers altogether. In the interim until a generic non-device specific solution is in place, force a restore of the gpio bank when enabling the gpio controller. Adds a new device-tree property for the OMAP GPIO controller to indicate if the GPIO controller is located in a power-domain that never loses power and hence will always maintain its logic state. Signed-off-by:
Jon Hunter <jon-hunter@ti.com> Acked-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Reviewed-by:
Kevin Hilman <khilman@linaro.org> Signed-off-by:
-
Jon Hunter authored
The OMAP GPIO interrupt service routine is checking each bit in the GPIO interrupt status register to see which bits are set. It is not efficient to check every bit especially if only a few bits are set. Therefore, instead of checking every bit use the __ffs() function, which returns the location of the first set bit, to find all the set bits. This optimisation was suggested-by and developed in collaboration with Felipe Balbi. Signed-off-by:
Felipe Balbi <balbi@ti.com> Acked-by:
-
Tarun Kanti DebBarma authored
68942edb (gpio/omap: fix wakeups on level-triggered GPIOs) already restores the fallingdetect and risingdetect contexts in *_runtime_resume(). These registers were modified in *_runtime_suspend() to include even those configured as level-triggered since only edge-triggered gpios can generate wakeup events. Therefore, the old context restores of the same registers present later in the code is not needed any more. Remove them. Signed-off-by:
Tarun Kanti DebBarma <tarun.kanti@ti.com> Signed-off-by:
-
Jon Hunter authored
Currently the IRQ domain is not freed once allocated, in the case where omap_gpio_probe() fails. Therefore, ensure we free the domain if the probe does fail. Furthermore, the local variable "ret" is not needed and so remove this. Signed-off-by:
-
Andreas Larsson authored
There is no general support for 64-bit big endian accesses, so that is left unsupported. Signed-off-by:
Andreas Larsson <andreas@gaisler.com> Acked-by:
Anton Vorontsov <anton@enomsg.org> Signed-off-by:
-
- 27 Mar, 2013 30 commits
-
-
Axel Lin authored
The of_device_id table is supposed to be zero-terminated. Signed-off-by:
Grant Likely <grant.likely@secretlab.ca> Acked-by:
Kukjin Kim <kgene.kim@samsung.com> Signed-off-by:
-
Simon Guinot authored
This patch adds a dedicated dbg_show function to the gpio-mvebu driver. In addition to the generic gpiolib informations, this function displays informations related with the specific Marvell registers (blink enable, data in polarity, interrupt masks and cause). Signed-off-by:
Simon Guinot <simon.guinot@sequanux.org> Signed-off-by:
-
Christophe Leroy authored
The bit_per_word can be set in the OF Device tree, so no need to force it as with the platform_data when using OF Platform Signed-off-by:
Patrick Vasseur <patrick.vasseur@c-s.fr> Signed-off-by:
Christophe Leroy <christophe.leroy@c-s.fr> Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-tps65910.c:136: ERROR: space required before the open parenthesis '(' Signed-off-by:Laurent Navet <laurent.navet@gmail.com> Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-timberdale.c:171: ERROR: else should follow close brace '}' Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-tc3589x.c:285: ERROR: code indent should use tabs where possible gpio/gpio-tc3589x.c:286: ERROR: code indent should use tabs where possible gpio/gpio-tc3589x.c:287: ERROR: code indent should use tabs where possible gpio/gpio-tc3589x.c:347: ERROR: code indent should use tabs where possible Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-stp-xway.c:220: ERROR: trailing whitespace Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-sch.c:206: ERROR: switch and case should be at the same indent Also remove blank lines Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-pxa.c:605: ERROR: space required after that ',' (ctx:VxV) gpio/gpio-pxa.c:672: ERROR: space prohibited after that open parenthesis '(' Signed-off-by: -
Laurent Navet authored
Fix : gpio/gpio-pca953x.c:150: ERROR: else should follow close brace '}' Signed-off-by:
-
Laurent Navet authored
Fix : gpio/gpio-omap.c:697: ERROR: space required before the open parenthesis '(' Signed-off-by: -
Laurent Navet authored
Fix : gpio/gpio-mvebu.c:120: ERROR: space required before the open parenthesis '(' gpio/gpio-mvebu.c:136: ERROR: space required before the open parenthesis '(' gpio/gpio-mvebu.c:154: ERROR: space required before the open parenthesis '(' gpio/gpio-mvebu.c:404: ERROR: space required before the open parenthesis '(' gpio/gpio-mvebu.c:476: ERROR: "(foo*)" should be "(foo *)" gpio/gpio-mvebu.c:480: ERROR: "(foo*)" should be "(foo *)" gpio/gpio-mvebu.c:484: ERROR: "(foo*)" should be "(foo *)" gpio/gpio-mvebu.c:512: ERROR: space prohibited after that '!' (ctx:BxW) gpio/gpio-mvebu.c:518: ERROR: space prohibited after that '!' (ctx:BxW) gpio/gpio-mvebu.c:518: ERROR: space required before the open brace '{' gpio/gpio-mvebu.c:563: ERROR: space prohibited after that '!' (ctx:BxW) gpio/gpio-mvebu.c:570: ERROR: trailing whitespace gpio/gpio-mvebu.c:577: ERROR: space required before the open parenthesis '(' gpio/gpio-mvebu.c:635: ERROR: space prohibited after that '!' (ctx:BxW) Signed-off-by: -
Laurent Navet authored
Fix : gpio/gpiolib-of.c:64: ERROR: code indent should use tabs where possible Signed-off-by:
-
Jingoo Han authored
Use the wrapper functions for getting and setting the driver data using spi_device instead of using dev_{get|set}_drvdata with &spi->dev, so we can directly pass a struct spi_device. Signed-off-by:Jingoo Han <jg1.han@samsung.com> Signed-off-by:
-
Jingoo Han authored
Use the wrapper functions for getting and setting the driver data using spi_device instead of using dev_{get|set}_drvdata with &spi->dev, so we can directly pass a struct spi_device. Signed-off-by: -
Jingoo Han authored
dev_err() is more preferred than printk(). Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Jingoo Han authored
Use devm_kzalloc() to make cleanup paths simpler. Signed-off-by:
-
Sachin Kamat authored
Use the newly introduced devm_ioremap_resource() instead of devm_request_and_ioremap() which provides more consistent error handling. devm_ioremap_resource() provides its own error messages; so all explicit error messages can be removed from the failure code paths. Signed-off-by:
Sachin Kamat <sachin.kamat@linaro.org> Reviewed-by:
Thierry Reding <thierry.reding@avionic-design.de> Acked-by:
Tony Prisk <linux@prisktech.co.nz> Signed-off-by:
-
Magnus Damm authored
Update the Emma Mobile GPIO driver to make use of devm functions. This simplifies the error handling and makes the code more compact. Signed-off-by:
Magnus Damm <damm@opensource.se> Signed-off-by:
-
Mathias Nyman authored
Lynxpoint gpio driver uses X86 specific io-ports to control gpios Signed-off-by:
Mathias Nyman <mathias.nyman@linux.intel.com> Reviewed-by:
-
Mika Westerberg authored
It is more readable for humans to use double-bang (!!) to convert the value to pure boolean before it is returned. Signed-off-by:
-
Darren Hart authored
The E6xx (TunnelCreek) CPUs have 9 GPIO lines in the resume well. Update the resume functions to allow for more than 8 GPIO lines, using the core functions as a template. Cc: Grant Likely <grant.likely@secretlab.ca> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
Darren Hart <dvhart@linux.intel.com> Signed-off-by:
-
Nikolay Balandin authored
Signed-off-by:
Nikolay Balandin <nbalandin@dev.rtsoft.ru> Acked-by:
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by:
-
Axel Lin authored
Set it once is enough, and it's done in vprbrd_gpiob_set() which is called by vprbrd_gpiob_direction_output(). Signed-off-by:
-
Jean Delvare authored
Stop checking for pin availability in direction and get functions. These functions can be called repeatedly, so checking every time is bad for performance. Now that requesting GPIO pins is no longer optional, checking for availability at pin request time is enough. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Cc: Peter Tyser <ptyser@xes-inc.com> Cc: Grant Likely <grant.likely@secretlab.ca> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
- 06 Mar, 2013 1 commit
-
-
Magnus Damm authored
Update the Emma Mobile GPIO driver to add DT support. The patch simply adds a two-cell xlate function and updates the probe code to allow configuration via DT using the "ngpios" property plus OF id in the same style as gpio-mvebu.c. The code is also adjusted to use postcore_initcall() to force early setup. Signed-off-by:
-
