From: Samuel Holland <email@example.com> To: Andre Przywara <firstname.lastname@example.org>, Maxime Ripard <email@example.com> Cc: Chen-Yu Tsai <firstname.lastname@example.org>, Jernej Skrabec <email@example.com>, Rob Herring <firstname.lastname@example.org>, Icenowy Zheng <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, Ondrej Jirman <firstname.lastname@example.org>, email@example.com, Alessandro Zummo <firstname.lastname@example.org>, Alexandre Belloni <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH v8 02/11] dt-bindings: rtc: sun6i: Add H616 compatible string Date: Thu, 19 Aug 2021 22:57:14 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 8/18/21 4:04 AM, Andre Przywara wrote: > On Tue, 17 Aug 2021 09:38:10 +0200 > Maxime Ripard <email@example.com> wrote: > > Hi Maxime, > >> On Mon, Aug 02, 2021 at 01:39:38AM +0100, Andre Przywara wrote: >>> On Mon, 26 Jul 2021 16:41:37 +0200 >>> Maxime Ripard <firstname.lastname@example.org> wrote: >>> >>>> Hi, >>>> >>>> On Fri, Jul 23, 2021 at 04:38:29PM +0100, Andre Przywara wrote: >>>>> Add the obvious compatible name to the existing RTC binding. >>>>> The actual RTC part of the device uses a different day/month/year >>>>> storage scheme, so it's not compatible with the previous devices. >>>>> Also the clock part is quite different, as there is no external 32K LOSC >>>>> oscillator input. >>>>> >>>>> Signed-off-by: Andre Przywara <email@example.com> >>>>> >>>>> --- >>>>> .../bindings/rtc/allwinner,sun6i-a31-rtc.yaml | 14 ++++++++++++++ >>>>> 1 file changed, 14 insertions(+) >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/rtc/allwinner,sun6i-a31-rtc.yaml b/Documentation/devicetree/bindings/rtc/allwinner,sun6i-a31-rtc.yaml >>>>> index beeb90e55727..d8a6500e5840 100644 >>>>> --- a/Documentation/devicetree/bindings/rtc/allwinner,sun6i-a31-rtc.yaml >>>>> +++ b/Documentation/devicetree/bindings/rtc/allwinner,sun6i-a31-rtc.yaml >>>>> @@ -26,6 +26,7 @@ properties: >>>>> - const: allwinner,sun50i-a64-rtc >>>>> - const: allwinner,sun8i-h3-rtc >>>>> - const: allwinner,sun50i-h6-rtc >>>>> + - const: allwinner,sun50i-h616-rtc >>>>> >>>>> reg: >>>>> maxItems: 1 >>>>> @@ -104,6 +105,19 @@ allOf: >>>>> minItems: 3 >>>>> maxItems: 3 >>>>> >>>>> + - if: >>>>> + properties: >>>>> + compatible: >>>>> + contains: >>>>> + const: allwinner,sun50i-h616-rtc >>>>> + >>>>> + then: >>>>> + properties: >>>>> + clock-output-names: >>>>> + minItems: 3 >>>>> + maxItems: 3 >>>> >>>> You don't need both of them when they are equal >>>> >>>>> + clocks: false >>>>> + >>>> >>>> It's not entirely clear to me what those clocks are about though. If we >>>> look at the clock output in the user manual, it looks like there's only >>>> two clocks that are actually being output: the 32k "fanout" clock and >>>> the losc. What are the 3 you're talking about?] >>> >>> I see three: the raw SYSTEM "CLK32K_LOSC", the RTC input + debounce >>> clock (/32), and the multiplexed PAD. >> >> But the input and debounce clock is only for the RTC itself right? So it >> should be local to the driver and doesn't need to be made available to >> the other drivers > > I understood "debounce" as being the clock used for the pinctrl > debouncer. What would it debounce otherwise? Do you think that this > "debounce circuit" is something internal to the RTC and is totally > irrelevant for us? I'm pretty sure this is the debounce for the NMI and the SoC reset signal, not the pinctrl. The pinctrl debounce clock pretty clearly references 32 kHz. > But in general I looked at how many *different* clocks this diagram > describes, and I count: one unaltered ("SYSTEM"), one "div by > 32" (RTC/debounce), and one multiplexed. My aim was to avoid > DT binding changes when we later discover we do need one of them for > something (as happened in the past). So three seemed to be the safe > choice here, to avoid surprises. In the worst case we just will never > reference one of them. Plus RC16M/IOSC (and depending on how you look at it, DCXO24M/HOSC). >> Either way, what this list is must be documented. > > You mean to overwrite the "description" stanza for clock-output-names? > And can this be done in the per-SoC parts in the later part of the > binding, keeping the existing description? > > Cheers, > Andre > >> >>>> Also, it looks like the 32k fanout clock needs at least the hosc or >>>> pll-periph in input, so we probably don't want to ask for no parent >>>> clock? Do you suggest we fix this for the existing bindings? >>> Well, we never seem to reference the HOSC this way, this was always >>> somewhat explicit. And yes, there is PLL-PERIPH as an input, but we >>> don't support this yet. So I went with 0 input clocks *for now*: the >>> driver can then ignore all clocks, so any clock referenced in the DT >>> later won't cause any harm. This will all be addressed by Samuel's RTC >>> clock patch, which will also touch the H6, IIRC. And it looks like we >>> will need to touch the binding anyway then, but can then just *extend* >>> this. >> >> You mentioned that series several times already and never provided an >> explanation for what it was supposed to be doing except fixing >> everything. What's the general plan for that series? This is my fault for not sending anything yet. Since the initial version of the driver had the RTC providing HOSC, it depended on converting the existing A100, H6, and H616 CCU drivers to use .fw_name for parents, since those drivers hardcode two different global names for HOSC. And I had no opportunit to do that yet. However, I should really send something that 100% matches the current binding for SoCs where that exists (i.e. osc24M is a fixed clock), and doing so is a smaller job. On the other hand, having osc24M as an RTC *output* neatly sidesteps the fact that it has been missing from the input list :) (But on the other-other hand, A50 gets even more fun, as the HOSC crystal may not be 24MHz anymore. So the RTC has to choose one of three possible HOSC->LOSC dividers based on the HOSC frequency. But there is no register for HOSC frequency. So in this case it is convenient to have HOSC as a separate fixed clock input.) The basic idea of my patch is that using the CCU library code lets us cleanly have slightly different clock trees for each of the RTC variants that Allwinner comes up with. The secondary goal is to add support for osc32k calibration. An early version of the patch is here, and I will send something as soon as I have made the modifications described above. But I know you were skeptical about moving the clock part out of the RTC driver. So if you NACK that, somebody will have to add all of the variants to the RTC driver. Regards, Samuel : https://github.com/smaeul/linux/commit/9510ca9e95cb.patch
next prev parent reply other threads:[~2021-08-20 3:57 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-23 15:38 [PATCH v8 00/11] arm64: sunxi: Initial Allwinner H616 SoC support Andre Przywara 2021-07-23 15:38 ` [PATCH v8 01/11] dt-bindings: mfd: axp20x: Add AXP305 compatible (plus optional IRQ) Andre Przywara 2021-08-16 12:39 ` Lee Jones 2021-07-23 15:38 ` [PATCH v8 02/11] dt-bindings: rtc: sun6i: Add H616 compatible string Andre Przywara 2021-07-23 22:34 ` Rob Herring 2021-07-26 14:41 ` Maxime Ripard 2021-08-02 0:39 ` Andre Przywara 2021-08-17 7:38 ` Maxime Ripard 2021-08-17 8:13 ` Alexandre Belloni 2021-08-19 7:56 ` Maxime Ripard 2021-08-18 9:04 ` Andre Przywara 2021-08-20 3:57 ` Samuel Holland [this message] 2021-09-01 7:21 ` Maxime Ripard 2021-07-23 15:38 ` [PATCH v8 03/11] rtc: sun6i: Fix time overflow handling Andre Przywara 2021-07-25 5:44 ` Jernej Škrabec 2021-07-23 15:38 ` [PATCH v8 04/11] rtc: sun6i: Add support for linear day storage Andre Przywara 2021-07-25 5:51 ` Jernej Škrabec 2021-07-23 15:38 ` [PATCH v8 05/11] rtc: sun6i: Add support for broken-down alarm registers Andre Przywara 2021-07-25 6:11 ` Jernej Škrabec 2021-08-02 0:39 ` Andre Przywara 2021-07-23 15:38 ` [PATCH v8 06/11] rtc: sun6i: Add support for RTCs without external LOSCs Andre Przywara 2021-07-25 6:18 ` Jernej Škrabec 2021-07-23 15:38 ` [PATCH v8 07/11] rtc: sun6i: Add Allwinner H616 support Andre Przywara 2021-07-25 6:19 ` Jernej Škrabec 2021-07-23 15:38 ` [PATCH v8 08/11] arm64: dts: allwinner: Add Allwinner H616 .dtsi file Andre Przywara 2021-07-23 15:38 ` [PATCH v8 09/11] dt-bindings: arm: sunxi: Add two H616 board compatible strings Andre Przywara 2021-07-23 15:38 ` [PATCH v8 10/11] arm64: dts: allwinner: h616: Add OrangePi Zero 2 board support Andre Przywara 2021-07-23 15:38 ` [PATCH v8 11/11] arm64: dts: allwinner: h616: Add X96 Mate TV box support Andre Przywara 2021-07-25 16:41 ` [PATCH v8 00/11] arm64: sunxi: Initial Allwinner H616 SoC support Icenowy Zheng 2021-07-26 14:52 ` Maxime Ripard 2021-08-02 0:38 ` Andre Przywara 2021-08-17 7:30 ` 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v8 02/11] dt-bindings: rtc: sun6i: Add H616 compatible string' \ /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
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).