From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mvebu-gpio: Disable blinking when enabling a GPIO for output
Date: Sun, 28 Oct 2012 17:37:44 +0100 [thread overview]
Message-ID: <201210281737.44335.michael@walle.cc> (raw)
In-Reply-To: <1351427004-32110-1-git-send-email-jm@lentin.co.uk>
Am Sonntag 28 Oktober 2012, 13:23:24 schrieb Jamie Lentin:
> The plat-orion GPIO driver would disable any pin blinking whenever
> using a pin for output. Do the same here, as a blinking LED will
> continue to blink regardless of what the GPIO pin level is.
>
> Signed-off-by: Jamie Lentin <jm@lentin.co.uk>
> ---
> The power LED on the DNS-320/DNS-325 is left blinking by the bootloader,
> the LED turning steady indicates it's booted. The blinking needs to be
> disabled before setting the GPIO pin level has any effect.
>
> Apart from the custom init code running too soon, I think everything is
> working now.
>
> I haven't tested this on any other boards, so not sure if it's sensible
> beyond the kirkwood/orion world.
>
> drivers/gpio/gpio-mvebu.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
> index cf7afb9..be65c04 100644
> --- a/drivers/gpio/gpio-mvebu.c
> +++ b/drivers/gpio/gpio-mvebu.c
> @@ -92,6 +92,11 @@ static inline void __iomem *mvebu_gpioreg_out(struct
> mvebu_gpio_chip *mvchip) return mvchip->membase + GPIO_OUT_OFF;
> }
>
> +static inline void __iomem *mvebu_gpioreg_blink(struct mvebu_gpio_chip
> *mvchip) +{
> + return mvchip->membase + GPIO_BLINK_EN_OFF;
> +}
> +
> static inline void __iomem *mvebu_gpioreg_io_conf(struct mvebu_gpio_chip
> *mvchip) {
> return mvchip->membase + GPIO_IO_CONF_OFF;
> @@ -206,6 +211,23 @@ static int mvebu_gpio_get(struct gpio_chip *chip,
> unsigned pin) return (u >> pin) & 1;
> }
>
> +static void mvebu_gpio_blink(struct gpio_chip *chip, unsigned pin, int
> value) +{
> + struct mvebu_gpio_chip *mvchip =
> + container_of(chip, struct mvebu_gpio_chip, chip);
> + unsigned long flags;
> + u32 u;
> +
> + spin_lock_irqsave(&mvchip->lock, flags);
> + u = readl_relaxed(mvebu_gpioreg_blink(mvchip));
> + if (value)
> + u |= 1 << pin;
> + else
> + u &= ~(1 << pin);
> + writel_relaxed(u, mvebu_gpioreg_blink(mvchip));
> + spin_unlock_irqrestore(&mvchip->lock, flags);
> +}
> +
> static int mvebu_gpio_direction_input(struct gpio_chip *chip, unsigned
> pin) {
> struct mvebu_gpio_chip *mvchip =
> @@ -244,6 +266,7 @@ static int mvebu_gpio_direction_output(struct gpio_chip
> *chip, unsigned pin, if (ret)
> return ret;
>
> + mvebu_gpio_blink(chip, pin, 0);
> mvebu_gpio_set(chip, pin, value);
>
> spin_lock_irqsave(&mvchip->lock, flags);
Tested-by: Michael Walle <michael@walle.cc>
--
Michael
next prev parent reply other threads:[~2012-10-28 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 12:23 [PATCH] mvebu-gpio: Disable blinking when enabling a GPIO for output Jamie Lentin
2012-10-28 16:37 ` Michael Walle [this message]
2012-10-30 22:16 ` Linus Walleij
2012-10-30 22:27 ` Thomas Petazzoni
2012-10-30 22:26 ` Thomas Petazzoni
2012-10-30 23:41 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201210281737.44335.michael@walle.cc \
--to=michael@walle.cc \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).