linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: r40: Allow setting parent rate for external clock outputs
Date: Wed, 18 Dec 2019 23:07:01 +0100	[thread overview]
Message-ID: <20191218220701.43zdbknygwwun466@gilmour.lan> (raw)
In-Reply-To: <20191218030431.14578-1-wens@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On Wed, Dec 18, 2019 at 11:04:31AM +0800, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai <wens@csie.org>
>
> One of the uses of the external clock outputs is to provide a stable
> 32768 Hz clock signal to WiFi and Bluetooth chips. On the R40, the RTC
> has an internal RC oscillator that is muxed with the external crystal.
>
> Allow setting the parent rate for the external clock outputs so that
> requests for 32768 Hz get passed to the RTC's clock driver to mux in
> the external crystal if it isn't already muxed correctly.
>
> Fixes: cd030a78f7aa ("clk: sunxi-ng: support R40 SoC")
> Fixes: 01a7ea763fc4 ("clk: sunxi-ng: r40: Force LOSC parent to RTC LOSC output")
> Cc: <stable@kernel.org>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>

Applied, thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2019-12-18 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18  3:04 [PATCH] clk: sunxi-ng: r40: Allow setting parent rate for external clock outputs Chen-Yu Tsai
2019-12-18 22:07 ` Maxime Ripard [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=20191218220701.43zdbknygwwun466@gilmour.lan \
    --to=mripard@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=stable@kernel.org \
    --cc=wens@csie.org \
    --cc=wens@kernel.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).