From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio: mvebu: Add clk support to prevent lockup
Date: Sun, 3 Feb 2013 20:44:39 -0500 [thread overview]
Message-ID: <20130204014439.GI14746@titan.lakedaemon.net> (raw)
In-Reply-To: <1359887666-17552-1-git-send-email-andrew@lunn.ch>
On Sun, Feb 03, 2013 at 11:34:26AM +0100, Andrew Lunn wrote:
> The kirkwood SoC GPIO cores use the runit clock. Add code to
> clk_prepare_enable() runit, otherwise there is a danger of locking up
> the SoC by accessing the GPIO registers when runit clock is not
> ticking.
>
> Reported-by: Simon Baatz <gmbnomis@gmail.com>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> Since v1:
> ChangeLog: tclk->runit clock
>
> arch/arm/boot/dts/kirkwood.dtsi | 2 ++
> drivers/gpio/gpio-mvebu.c | 7 +++++++
> 2 files changed, 9 insertions(+)
Linus,
I merge-tested this against your gpio/fixes branch since you had a patch
to the same file:
11c0cee gpio: mvebu: Don't free chip label memory
There were no conflicts. If you don't mind, I'd like to take this
through mvebu/fixes -> arm-soc since this is one of four patches to fix
one reported issue. I'd like to keep them in the same branch.
If this causes a headache for you, please let me know and you can take
it.
Otherwise, applied to mvebu/fixes with Simon's Tested-by:
thx,
Jason.
next prev parent reply other threads:[~2013-02-04 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 10:34 [PATCH v2] gpio: mvebu: Add clk support to prevent lockup Andrew Lunn
2013-02-03 19:48 ` Simon Baatz
2013-02-04 1:44 ` Jason Cooper [this message]
2013-02-04 20:45 ` 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=20130204014439.GI14746@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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