From: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Alex Elder <elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
bcm-xK7y4jjYLqYh9ZMKESR00Q@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 RESEND 0/5] clk: bcm21664: add common clock support
Date: Fri, 25 Apr 2014 17:09:15 -0700 [thread overview]
Message-ID: <20140426000915.7224.11265@quantum> (raw)
In-Reply-To: <1398115587-32529-1-git-send-email-elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Quoting Alex Elder (2014-04-21 14:26:22)
> This is series has two parts. The first two patches are changes
> to the existing Broadcom Kona family clock code to prepare for the
> addition of support for another SoC, bcm21664.
>
> The remaining three define the binding and code for bcm21664, and
> replace the use of "fake" clocks in the device tree with the real
> ones. This ends up being a fairly straightforward definition of
> the clocks on this SoC; the rest of the clock code is shared with
> other SoCs that use the Kona style clock system.
Hi Alex,
I'm happy to take only the clk patches or I can take the DT stuff as
well if it gets some Acks. Let me know how you want it handled.
Regards,
Mike
>
> This series depends on the following patch, which has been taken
> into the clk-fixes tree:
> clk: bcm281xx: don't use unnamed structs or unions
> https://lkml.org/lkml/2014/4/7/322
>
> In addition, it depends on the version 4 of the following series,
> just (re)posted for review:
> clk: bcm281xx: updates
> https://lkml.org/lkml/2014/4/8/485
>
> The patches in this series--based on the current linus/master branch
> plus the patches mentioned above--are available here:
> http://git.linaro.org/git/landing-teams/working/broadcom/kernel.git
> Branch review/bcm21664-clock-v2
>
> Alex Elder (5):
> clk: bcm281xx: move compatible string definitions
> ARM: dts: revise kona clock binding document
> ARM: dts: define clock binding for bcm21664
> clk: bcm21664: use common clock framework
> ARM: dts: use real clocks for bcm21664
>
> .../devicetree/bindings/clock/bcm-kona-clock.txt | 116 ++++++---
> arch/arm/boot/dts/bcm21664.dtsi | 190 +++++++++-----
> drivers/clk/bcm/Kconfig | 2 +-
> drivers/clk/bcm/Makefile | 1 +
> drivers/clk/bcm/clk-bcm21664.c | 290 +++++++++++++++++++++
> drivers/clk/bcm/clk-bcm281xx.c | 12 -
> include/dt-bindings/clock/bcm21664.h | 62 +++++
> include/dt-bindings/clock/bcm281xx.h | 12 +
> 8 files changed, 565 insertions(+), 120 deletions(-)
> create mode 100644 drivers/clk/bcm/clk-bcm21664.c
> create mode 100644 include/dt-bindings/clock/bcm21664.h
>
> --
> 1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-26 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 21:26 [PATCH v2 RESEND 0/5] clk: bcm21664: add common clock support Alex Elder
2014-04-21 21:26 ` [PATCH v2 RESEND 2/5] ARM: dts: revise kona clock binding document Alex Elder
2014-04-21 21:26 ` [PATCH v2 RESEND 3/5] ARM: dts: define clock binding for bcm21664 Alex Elder
2014-04-21 21:26 ` [PATCH v2 RESEND 4/5] clk: bcm21664: use common clock framework Alex Elder
2014-04-21 21:26 ` [PATCH v2 RESEND 5/5] ARM: dts: use real clocks for bcm21664 Alex Elder
2014-04-26 2:59 ` Matt Porter
[not found] ` <1398115587-32529-1-git-send-email-elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-04-21 21:26 ` [PATCH v2 RESEND 1/5] clk: bcm281xx: move compatible string definitions Alex Elder
2014-04-26 0:09 ` Mike Turquette [this message]
2014-04-26 1:43 ` [PATCH v2 RESEND 0/5] clk: bcm21664: add common clock support Alex Elder
2014-04-26 3:02 ` Matt Porter
2014-04-29 5:48 ` Mike Turquette
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=20140426000915.7224.11265@quantum \
--to=mturquette-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=bcm-xK7y4jjYLqYh9ZMKESR00Q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).