devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Maxime Ripard <maxime@cerno.tech>
Cc: Samuel Holland <samuel@sholland.org>,
	Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@lists.linux.dev,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: (subset) [PATCH v3 5/6] clk: sunxi-ng: Add support for the sun6i RTC clocks
Date: Thu, 17 Feb 2022 16:33:37 -0800	[thread overview]
Message-ID: <20220218003338.DBFE5C340E9@smtp.kernel.org> (raw)
In-Reply-To: <YghBkp/sUHdqSn4G@piout.net>

Quoting Alexandre Belloni (2022-02-12 15:24:02)
> On 11/02/2022 13:43:12+0100, Maxime Ripard wrote:
> > Hi Samuel,
> > 
> > On Mon, Feb 07, 2022 at 05:54:02PM -0600, Samuel Holland wrote:
> > > On 2/7/22 3:00 AM, Maxime Ripard wrote:
> > > > On Wed, 2 Feb 2022 20:17:35 -0600, Samuel Holland wrote:
> > > >> The RTC power domain in sun6i and newer SoCs manages the 16 MHz RC
> > > >> oscillator (called "IOSC" or "osc16M") and the optional 32 kHz crystal
> > > >> oscillator (called "LOSC" or "osc32k"). Starting with the H6, this power
> > > >> domain also handles the 24 MHz DCXO (called variously "HOSC", "dcxo24M",
> > > >> or "osc24M") as well. The H6 also adds a calibration circuit for IOSC.
> > > >>
> > > >> Later SoCs introduce further variations on the design:
> > > >>  - H616 adds an additional mux for the 32 kHz fanout source.
> > > >>  - R329 adds an additional mux for the RTC timekeeping clock, a clock
> > > >>    for the SPI bus between power domains inside the RTC, and removes the
> > > >>    IOSC calibration functionality.
> > > >>
> > > >> [...]
> > > > 
> > > > Applied to local tree (sunxi/clk-for-5.18).
> > > 
> > > Part of the build failures were because this patch depends on patch 3. Is that
> > > okay, or should I update this patch to be independent?
> > 
> > We don't have anything queued up yet, so I think the easiest would be to
> > merge this through the RTC tree. So nothing to do on your side yet, we
> > just need Alex to answer :)
> > 
> 
> I can take the whole series but I think I would need acks from Stephen
> 

For the clk patches

Acked-by: Stephen Boyd <sboyd@kernel.org>

  reply	other threads:[~2022-02-18  0:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  2:17 [PATCH v3 0/6] clk: sunxi-ng: Add a RTC CCU driver Samuel Holland
2022-02-03  2:17 ` [PATCH v3 1/6] dt-bindings: rtc: sun6i: Clean up repetition Samuel Holland
2022-02-07  8:46   ` Maxime Ripard
2022-02-03  2:17 ` [PATCH v3 2/6] dt-bindings: rtc: sun6i: Add H616, R329, and D1 support Samuel Holland
2022-02-07  8:55   ` Maxime Ripard
2022-02-07 21:45   ` Rob Herring
2022-02-03  2:17 ` [PATCH v3 3/6] rtc: sun6i: Enable the bus clock when provided Samuel Holland
2022-02-07  8:56   ` Maxime Ripard
2022-02-03  2:17 ` [PATCH v3 4/6] clk: sunxi-ng: mux: Allow muxes to have keys Samuel Holland
2022-02-07  9:00   ` (subset) " Maxime Ripard
2022-02-03  2:17 ` [PATCH v3 5/6] clk: sunxi-ng: Add support for the sun6i RTC clocks Samuel Holland
2022-02-07  9:00   ` (subset) " Maxime Ripard
2022-02-07 23:54     ` Samuel Holland
2022-02-11 12:43       ` Maxime Ripard
2022-02-12 23:24         ` Alexandre Belloni
2022-02-18  0:33           ` Stephen Boyd [this message]
2022-02-03  2:17 ` [PATCH v3 6/6] [DO NOT MERGE] clk: sunxi-ng: sun6i-rtc: Add support for H6 Samuel Holland
2022-02-15 22:16 ` [PATCH v3 0/6] clk: sunxi-ng: Add a RTC CCU driver Alexandre Belloni
2022-03-12 11:29 ` Alexandre Belloni

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=20220218003338.DBFE5C340E9@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=maxime@cerno.tech \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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).