From: Stephen Boyd <sboyd@codeaurora.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
Wim Van Sebroeck <wim@iguana.be>,
Guenter Roeck <linux@roeck-us.net>,
linux-clk@vger.kernel.org, linux-mips@linux-mips.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 2/2] MIPS: TXx9: Convert to Common Clock Framework
Date: Mon, 12 Sep 2016 15:32:57 -0700 [thread overview]
Message-ID: <20160912223257.GJ7243@codeaurora.org> (raw)
In-Reply-To: <1473584398-12942-3-git-send-email-geert@linux-m68k.org>
On 09/11, Geert Uytterhoeven wrote:
> Replace the custom minimal clock implementation for Toshiba TXx9 by a
> basic implementation using the Common Clock Framework.
>
> The only clocks that are provided are those needed by TXx9-specific
> drivers ("imbus" and "spi" (TX4938 only)), and their common parent
> clock "gbus". Other clocks can be added when needed.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-09-12 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 8:59 [PATCH v2 0/2] MIPS: TXx9: Common Clock Framework Conversion Geert Uytterhoeven
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 [this message]
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=20160912223257.GJ7243@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=geert@linux-m68k.org \
--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).