Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] rtc: sun6i: Fix the RTC accuracy
Date: Tue, 24 Jan 2017 18:49:35 +0100	[thread overview]
Message-ID: <20170124174935.att4s7mqfbyxkxqk@piout.net> (raw)
In-Reply-To: <cover.6bd4d4760c24d09845ad09c212fcd487d78da5ad.1485168100.git-series.maxime.ripard@free-electrons.com>

Hi,

On 23/01/2017 at 11:41:45 +0100, Maxime Ripard wrote :
> Hi,
> 
> The RTC used in the A31 and later SoC has an accuracy issue, which is
> already significant even after a couple of hours.
> 
> This is due to the fact that the oscillator used by default is an internal
> and very inaccurate one.
> 
> A first attempt at fixing that by switching to the external oscillator was
> done in the patch "rtc: sun6i: Switch to the external oscillator". However,
> it turned out to be problematic since it was tracked properly in the clock
> framework, which might lead to some clocks being disabled, even though
> their devices were not notified.
> 
> This is a second attempt, this time by making it part of the CCF. It
> turned out to be a bit more complicated than one would expect since the mux
> found inside the RTC also controls one of the input of the main clock unit.
> Therefore, it needs to be probed before the main clock unit driver.
> 
> Let me know what you think,
> Maxime
> 
> Changes from v1:
>   - Force the muxing to the external oscillator even for old DT
>   - Make the patches a bit more stable friendly
>   - Change the bindings to have a cell of 1, to account for the external
>     output of the oscillator
>   - Split the driver remove() removal into a separate patch and switched to
>     devm
>   - Reordered the patches
> 
> Maxime Ripard (7):
>   rtc: sun6i: Disable the build as a module
>   rtc: sun6i: Add some locking
>   rtc: sun6i: Switch to the external oscillator
>   rtc: sun6i: Expose the 32kHz oscillator
>   rtc: sun6i: Switch to devm_rtc_device_register
>   ARM: sun8i: a23/a33: Enable the real LOSC and use it
>   ARM: sun8i: a23/a33: Add the oscillators accuracy
> 

I've applied 1/7 to 5/7. Thanks!

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-01-24 17:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 10:41 [PATCH v2 0/7] rtc: sun6i: Fix the RTC accuracy Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 1/7] rtc: sun6i: Disable the build as a module Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 2/7] rtc: sun6i: Add some locking Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 3/7] rtc: sun6i: Switch to the external oscillator Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 4/7] rtc: sun6i: Expose the 32kHz oscillator Maxime Ripard
2017-01-23 21:00   ` Rob Herring
2017-01-23 10:41 ` [PATCH v2 5/7] rtc: sun6i: Switch to devm_rtc_device_register Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 6/7] ARM: sun8i: a23/a33: Enable the real LOSC and use it Maxime Ripard
2017-01-23 10:41 ` [PATCH v2 7/7] ARM: sun8i: a23/a33: Add the oscillators accuracy Maxime Ripard
2017-01-24 17:49 ` Alexandre Belloni [this message]
2017-01-25 15:36   ` [PATCH v2 0/7] rtc: sun6i: Fix the RTC accuracy Maxime Ripard

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=20170124174935.att4s7mqfbyxkxqk@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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