Re: [PATCH] OMAP3: GPIO: Added dynamic control logic for pad wakeups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tero Kristo <tero.kristo@xxxxxxxxx> writes:

> From: Tero Kristo <tero.kristo@xxxxxxxxx>
>
> Pad wakeups are now enabled if the corresponding GPIO interrupt is enabled.
>
> Applies on top of PM branch.
>
> Signed-off-by: Tero Kristo <tero.kristo@xxxxxxxxx>
> Signed-off-by: Jouni Hogander <jouni.hogander@xxxxxxxxx>

I just discovered this one in patchwork... sorry for the delay.

Changes in wakeup state should not be directly correlated to interrupt
enabled GPIOs.  Rather, this should only be done for GPIOs that are
explicitly wakeup enabled (via enable_irq_wake(), which in turn
calls gpio_wake_enable()).

A couple other minor comments below...

> ---
>  arch/arm/plat-omap/gpio.c |   22 +++++++++++++++++++++-
>  1 files changed, 21 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
> index e242112..fa79db2 100644
> --- a/arch/arm/plat-omap/gpio.c
> +++ b/arch/arm/plat-omap/gpio.c
> @@ -267,6 +267,7 @@ static struct gpio_bank gpio_bank_34xx[6] = {
>  #define OMAP34XX_PAD_SAFE_MODE 0x7
>  #define OMAP34XX_PAD_IN_PU_GPIO 0x11c
>  #define OMAP34XX_PAD_IN_PD_GPIO 0x10c
> +#define OMAP34XX_PAD_WAKE_EN (1 << 14)

Can use BIT(14) here

>  struct omap3_gpio_regs {
>  	u32 sysconfig;
> @@ -713,6 +714,8 @@ static inline void set_24xx_gpio_triggering(struct gpio_bank *bank, int gpio,
>  {
>  	void __iomem *base = bank->base;
>  	u32 gpio_bit = 1 << gpio;
> +	struct gpio_pad *pad;
> +	int gpio_num;
>  	u32 val;
>  
>  	if (cpu_is_omap44xx()) {
> @@ -750,6 +753,23 @@ static inline void set_24xx_gpio_triggering(struct gpio_bank *bank, int gpio,
>  			 * GPIO wakeup request can only be generated on edge
>  			 * transitions
>  			 */

The comment above needs to stay with the original code.

> +			pad = gpio_pads;
> +
> +			gpio_num = bank->virtual_irq_start - IH_GPIO_BASE +
> +				gpio;
> +			/* Find the pad corresponding the GPIO */
> +			while (pad->gpio >= 0 && pad->gpio != gpio_num)
> +				pad++;
> +			/* Enable / disable pad wakeup */
> +			if (pad->gpio == gpio_num) {
> +				val = omap_ctrl_readw(pad->offset);
> +				if (trigger & IRQ_TYPE_EDGE_BOTH)
> +					val |= OMAP34XX_PAD_WAKE_EN;
> +				else
> +					val &= ~(u16)OMAP34XX_PAD_WAKE_EN;
> +				omap_ctrl_writew(val, pad->offset);
> +			}
> +
>  			if (trigger & IRQ_TYPE_EDGE_BOTH)
>  				__raw_writel(1 << gpio, bank->base
>  					+ OMAP24XX_GPIO_SETWKUENA);
> @@ -1654,7 +1674,7 @@ static int __init omap3_gpio_pads_init(void)
>  	gpio_pads[gpio_amt].gpio = -1;
>  	return 0;
>  }
> -late_initcall(omap3_gpio_pads_init);
> +early_initcall(omap3_gpio_pads_init);

This change isn't explained in the changelog and appears unrelated to
this patch.


Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux