From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: imx: shared gate support for i.MX clk_gate2 clock
Date: Wed, 23 Apr 2014 14:57:51 +0800 [thread overview]
Message-ID: <20140423065749.GA2523@dragon> (raw)
In-Reply-To: <20140422025408.GA31659@MrMyself>
On Tue, Apr 22, 2014 at 10:54:11AM +0800, Nicolin Chen wrote:
> Hi all,
>
> On Sat, Apr 19, 2014 at 01:01:29PM +0800, Shawn Guo wrote:
> > We're constantly running into the situation on i.MX that multiple clocks
> > share the single gate. Since we already have i.MX specific gate clock
> > implementation due to 2-bits gate, the series takes Gerhard's approach
> > to add shared gate support for i.MX clk_gate2 clock.
> >
> > Shawn Guo (4):
> > ARM: imx: define struct clk_gate2 on our own
> > ARM: imx: lock is always valid for clk_gate2
> > ARM: imx: add shared gate clock support
> > ARM: imx6q: add the missing esai_ahb clock
>
> I've simply tested these patches on both for-next and 3.10.y baseline
> and it works fine. Hope we can apply them soon.
Thanks for testing, Nicolin. I just applied the series, and will get
it into linux-next for wider testing soon.
Shawn
prev parent reply other threads:[~2014-04-23 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 5:01 [PATCH 0/4] ARM: imx: shared gate support for i.MX clk_gate2 clock Shawn Guo
2014-04-19 5:01 ` [PATCH 1/4] ARM: imx: define struct clk_gate2 on our own Shawn Guo
2014-04-19 5:01 ` [PATCH 2/4] ARM: imx: lock is always valid for clk_gate2 Shawn Guo
2014-04-19 5:01 ` [PATCH 3/4] ARM: imx: add shared gate clock support Shawn Guo
2014-04-19 11:09 ` Nicolin Chen
2014-04-19 5:01 ` [PATCH 4/4] ARM: imx6q: add the missing esai_ahb clock Shawn Guo
2014-04-22 2:54 ` [PATCH 0/4] ARM: imx: shared gate support for i.MX clk_gate2 clock Nicolin Chen
2014-04-23 6:57 ` Shawn Guo [this message]
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=20140423065749.GA2523@dragon \
--to=shawn.guo@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.