From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ralf Baechle <ralf@linux-mips.org>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
Wim Van Sebroeck <wim@iguana.be>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-clk@vger.kernel.org, linux-mips@linux-mips.org,
linux-watchdog@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v2 0/2] MIPS: TXx9: Common Clock Framework Conversion
Date: Sun, 11 Sep 2016 10:59:56 +0200 [thread overview]
Message-ID: <1473584398-12942-1-git-send-email-geert@linux-m68k.org> (raw)
Hi Ralf, Nemoto-san, Wim,
This patch series converts the Toshiba TXx9 platforms from their own
custom minimal clock implementation to the Common Clock Framework.
- Patch 1 adds missing clock (un)prepare calls to the TXx9 watchdog
driver,
- Patch 2 replaces the custom clock implementation by a CCF-based one,
providing a minimal set of clocks.
This has been tested with the watchdog on RBTX4927.
Changes since v1:
- Dropped "spi: spi-txx9: Add missing clock (un)prepare calls for
CCF", which has been accepted in spi/for-next,
- Protect the TX4938_REV_PCODE() check by #ifdef CONFIG_CPU_TX49XX,
- Use new clk_hw-centric clock registration API,
- Add Reviewed-by.
Dependencies:
- Patch 1 can be applied independently,
- Patch 2 depends on patch 1 and on "spi: spi-txx9: Add missing clock
(un)prepare calls for CCF" in spi/for-next,
- The error path in patch 2 depends on "clkdev: Detect errors in
clk_hw_register_clkdev() for mass registration", but this is less
critical.
Wim: Can you please appply patch 1 directly, so we can get at least the
hard dependencies in v4.9?
Thanks!
Geert Uytterhoeven (2):
watchdog: txx9wdt: Add missing clock (un)prepare calls for CCF
MIPS: TXx9: Convert to Common Clock Framework
arch/mips/txx9/Kconfig | 2 +-
arch/mips/txx9/generic/setup.c | 70 +++++++++++++++++++++---------------------
drivers/watchdog/txx9wdt.c | 6 ++--
3 files changed, 39 insertions(+), 39 deletions(-)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2016-09-11 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 8:59 Geert Uytterhoeven [this message]
2016-09-11 8:59 ` [PATCH v2 1/2] watchdog: txx9wdt: Add missing clock (un)prepare calls for CCF Geert Uytterhoeven
2016-10-08 14:13 ` Wim Van Sebroeck
2016-09-11 8:59 ` [PATCH v2 2/2] MIPS: TXx9: Convert to Common Clock Framework Geert Uytterhoeven
2016-09-12 22:32 ` Stephen Boyd
2016-09-13 15:00 ` Atsushi Nemoto
2016-09-11 14:22 ` [PATCH v2 0/2] MIPS: TXx9: Common Clock Framework Conversion Guenter Roeck
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=1473584398-12942-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-clk@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ralf@linux-mips.org \
--cc=wim@iguana.be \
/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).