From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] support Hisilicon SoC
Date: Sat, 15 Jun 2013 21:08:23 -0700 [thread overview]
Message-ID: <20130616040823.7541.14694@quantum> (raw)
In-Reply-To: <20130613195801.GA21765@quad.lixom.net>
Quoting Olof Johansson (2013-06-13 12:58:01)
> On Thu, Jun 13, 2013 at 06:29:47PM +0200, Heiko St?bner wrote:
> > Am Mittwoch, 12. Juni 2013, 22:01:42 schrieb Olof Johansson:
> > > On Sat, Jun 08, 2013 at 10:47:16PM +0800, Haojian Zhuang wrote:
> > > > Changelog:
> > > > v4:
> > > > 1. Add clk gate with HIWORD mask for Rockchip.
> > > > 2. Update comments and code of HIWORD flags for mux/divider.
> > > > 3. Append a mux without HIWORD mask in Hisilicon 3620.
> > > > 4. Fix the pinmux setting in Hi4511.
> > > >
> > > > v3:
> > > > 1. Use clk_register_mux_table().
> > > >
> > > > v2:
> > > > 1. Reuse mux & divider driver. So append CLK_MUX_HIWORD_MASK &
> > > > CLK_DIVIDER_HIWORD_MASK for Hi3620 SoC.
> > > > 2. Fix system timer running too fast because wrong divider is choosen.
> > > > 3. Remove .init_irq in DT machine descriptor.
> > >
> > > Hi,
> > >
> > > I had some comments on the last two patches. I also haven't seen any acks
> > > from Mike on any of the clock changes, which would be needed before we can
> > > pick them up. He might want to merge them into his tree as well, if so
> > > we'll have to setup a shared branch.
> >
> > Also, if anything unexpected happens to the main hisilicon support, could you
> > or Mike pick up the HIWORD_MASK patches anyway (if they are acceptable),
> > because they're needed for the Rockchip stuff too.
>
> Ok, that definitely means a topic branch would be a good idea. Mike, can you
> collect these branches on a topic that we can just pull in as a dependency
> then, please? Assuming you're happy with them, of course.
Do you mean s/branches/patches/ ?
I've pulled patches #1-#3 into clk-next, but I'd like a couple of rounds
through linux-next before I state that a given commit is stable. So
maybe early next week (it's still Saturday for me) I'll push out a
clk-for-3.11 branch that will have the hiword patches in them and the
sha1's will not change.
Regards,
Mike
>
> Thanks!
>
> -Olof
next prev parent reply other threads:[~2013-06-16 4:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 14:47 [PATCH v4 0/7] support Hisilicon SoC Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 1/7] clk: mux: add CLK_MUX_HIWORD_MASK Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 2/7] clk: divider: add CLK_DIVIDER_HIWORD_MASK flag Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 3/7] clk: gate: add CLK_GATE_HIWORD_MASK Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 4/7] clk: hi3xxx: add clock support Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 5/7] ARM: debug: support debug ll on hisilicon soc Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 6/7] ARM: hi3xxx: add board support with device tree Haojian Zhuang
2013-06-12 19:54 ` Olof Johansson
2013-06-17 1:06 ` Haojian Zhuang
2013-06-08 14:47 ` [PATCH v4 7/7] ARM: hi3xxx: enable hi4511 " Haojian Zhuang
2013-06-12 20:00 ` Olof Johansson
2013-06-17 1:21 ` Haojian Zhuang
2013-06-18 7:38 ` Linus Walleij
2013-06-12 20:01 ` [PATCH v4 0/7] support Hisilicon SoC Olof Johansson
2013-06-13 16:29 ` Heiko Stübner
2013-06-13 19:58 ` Olof Johansson
2013-06-16 4:08 ` Mike Turquette [this message]
2013-06-16 4:32 ` Olof Johansson
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=20130616040823.7541.14694@quantum \
--to=mturquette@linaro.org \
--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).