History log of /drivers/gpio/gpio-pca953x.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
404ba2b8f611bea3228daf031f03901d0c34ecd7 21-Nov-2011 Mark Brown <broonie@opensource.wolfsonmicro.com> gpio: pca953x: Staticise pca953x_get_altdata()

It's not used outside of the driver so doesn't need to be exported, and
sparse notices this and complains about it.

Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
/drivers/gpio/gpio-pca953x.c
80f01ca1fce2d5045b98f01989017767339b8700 15-Nov-2011 Linus Torvalds <torvalds@linux-foundation.org> Merge branch 'gpio/merge' of git://git.secretlab.ca/git/linux-2.6

* 'gpio/merge' of git://git.secretlab.ca/git/linux-2.6:
gpio: pca953x: propagate the errno from the chip_init functions
gpio: pca953x: remove unneeded check for chip type
gpio/omap: check return value from irq_alloc_generic_chip
gpio/omap: replace MOD_REG_BIT macro with static inline
7ea2aa2046a15af1c048115e7c05f1ba1566899d 14-Oct-2011 Wolfram Sang <w.sang@pengutronix.de> gpio: pca953x: propagate the errno from the chip_init functions

Initializing the chips may return with an error, but this error gets
dropped in probe(). Propagate this further to the driver core. Also,
simplify returning the error in one of the init functions.

Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
f0eb824beee3f596b9799e667a6fdac3116e9f7d 14-Oct-2011 Wolfram Sang <w.sang@pengutronix.de> gpio: pca953x: remove unneeded check for chip type

We can assume our own device_id table is correct, so remove checking if
the chip type is valid. (The check was bogus anyway: If it found an
invalid entry, it returned with 0!) This is in preparation for further
cleanups.

Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
25fcf2b7f1f65d2cc12182ced3ccd47576970be4 11-Oct-2011 Hartmut Knaack <knaack.h@gmx.de> gpio-pca953x: fix gpio_base

gpio_base was set to 0 if no system platform data or open firmware
platform data was provided. This led to conflicts, if any other gpiochip
with a gpiobase of 0 was instantiated already. Setting it to -1 will
automatically use the first one available.

Signed-off-by: Hartmut Knaack <knaack.h@gmx.de>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
a57339b4b5daf23b4cec450b37906d5f8b5fa722 14-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Deprecate meaningless device-tree bindings

The property 'polarity' is handled by the GPIO core, and the 'gpio-base'
should be assigned automatically. It is meaningless in the device-tree,
since GPIO's are identified by the "chip-name"/offset pair.
This way, the whole pca953x_get_alt_pdata() can hopefully soon go away.
We still need to check whether we really want GPIO-interrupt functionality
by simply looking if the I2C node has an interrupts property defined, since
this property is not used for anything else.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
c6dcf592437e5919cb03af5dcfe369702e6a4a7c 14-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Remove dynamic platform data pointer

In the case that we obtain device-tree data to fill in platform_data, the new
platform data struct was dynamically allocated, but the pointer to it was not
used everywhere it should. It seems easier to fix this issue by removing the
dynamic allocation altogether since its data is only used during driver
probing.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
c609c05db10dcb020f6869186e548a0596a78896 14-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Fix IRQ support.

It seems that in the normal case, IRQ_NOREQUEST needs to be explicitly
cleared, otherwise claiming the interrupt fails.
In the case of sparse interrupts, the descriptor needs to be allocated
first.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
6dd599f8af0166805951f4421a78ba716d78321a 08-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Fix warning of enabled interrupts in handler

When using nested threaded irqs, use handle_nested_irq(). This function
does not call the chip handler, so no handler is set.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
17e8b42c17c3e9735ea03c4e6b67cedf5de170f4 08-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Interrupt pin is active-low

The interrupt pin of the PCA953x is active low, and on the rising edge
no interrupt should be produced.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
910c8fb6b4b8c9e0be576b6a78f4cccf228a4bfd 08-Jun-2011 David Jander <david@protonic.nl> gpio/pca953x: Fix IRQ support.

It seems that in the normal case, IRQ_NOREQUEST needs to be explicitly
cleared, otherwise claiming the interrupt fails.
In the case of sparse interrupts, the descriptor needs to be allocated
first.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c
c103de240439dfee24ac50eb99c8be3a30d13323 05-Jun-2011 Grant Likely <grant.likely@secretlab.ca> gpio: reorganize drivers

Sort the gpio makefile and enforce the naming convention gpio-*.c for
gpio drivers.

v2: cleaned up filenames in Kconfig and comment blocks
v3: fixup use of BASIC_MMIO to GENERIC_GPIO for mxc

Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
/drivers/gpio/gpio-pca953x.c