devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	NXP S32 Linux Team <s32@nxp.com>,
	Bogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com>,
	Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
Subject: Re: [PATCH 1/4] dt-bindings: rtc: add schema for NXP S32G2/S32G3 SoCs
Date: Tue, 17 Sep 2024 10:21:32 +0300	[thread overview]
Message-ID: <c51a8065-2052-4a4e-b871-c0bd8d834548@oss.nxp.com> (raw)
In-Reply-To: <202409121403232ab1295b@mail.local>

On 9/12/2024 5:03 PM, Alexandre Belloni wrote:
> On 12/09/2024 15:36:46+0300, Ciprian Marian Costea wrote:
>>> Then should this mux be registered in the CCF so you can use the usual
>>> clock node properties?
>>
>> Hello Alexandre,
>>
>> In hardware, these clock muxes and divisors are part of the RTC module
>> itself and not external. Therefore, I would say no.
> 
> This is irrelevant, if this is a clock mux, it must be in the CCF, just
> as when the RTC has a clock output.
> 
> 

I understand your point, but taking into account the fact that FIRC 
clock should be used in most scenarios, would it be acceptable to not 
export this 'clksel' property in the devicetree bindings and simply use 
the FIRC clock by default in the RTC driver ?

At least for this patchset, in order to ease the review process. If 
configurable clock source support would want to be enabled and exported 
via bindings for this S32G2/S32G3 RTC driver, then CCF registration for 
this clk mux could be added in future patches.

  reply	other threads:[~2024-09-17  7:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  7:00 [PATCH 0/4] add NXP RTC driver support for S32G2/S32G3 SoCs Ciprian Costea
2024-09-11  7:00 ` [PATCH 1/4] dt-bindings: rtc: add schema for NXP " Ciprian Costea
2024-09-11 18:21   ` Conor Dooley
2024-09-12 10:50     ` Ciprian Marian Costea
2024-09-12 11:27       ` Conor Dooley
2024-09-12 13:02         ` Ciprian Marian Costea
2024-09-12 12:26       ` Alexandre Belloni
2024-09-12 12:36         ` Ciprian Marian Costea
2024-09-12 14:03           ` Alexandre Belloni
2024-09-17  7:21             ` Ciprian Marian Costea [this message]
2024-09-17 12:37               ` Conor Dooley
2024-09-17 13:01               ` Alexandre Belloni
2024-09-11 18:22   ` Conor Dooley
2024-09-12 10:55     ` Ciprian Marian Costea
2024-09-12 11:13       ` Conor Dooley
2024-09-12 12:00         ` Ciprian Marian Costea
2024-09-12 12:12           ` Conor Dooley
2024-09-12 12:16             ` Ciprian Marian Costea
2024-09-11  7:00 ` [PATCH 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-09-12  4:41   ` kernel test robot
2024-09-13 11:58   ` kernel test robot
2024-09-17 17:40   ` Krzysztof Kozlowski
2024-09-18  7:51     ` Ciprian Marian Costea
2024-09-18 10:26   ` Alexandre Belloni
2024-09-18 15:08     ` Ciprian Marian Costea
2024-09-11  7:00 ` [PATCH 3/4] arm64: defconfig: add S32G RTC module support Ciprian Costea
2024-09-17 17:36   ` Krzysztof Kozlowski
2024-09-18  8:02     ` Ciprian Marian Costea
2024-09-18  8:10       ` Krzysztof Kozlowski
2024-09-11  7:00 ` [PATCH 4/4] MAINTAINERS: add MAINTAINER for S32G2/S32G3 RTC driver Ciprian Costea
2024-09-17 17:37   ` Krzysztof Kozlowski
2024-09-18  8:13     ` Ciprian Marian Costea
2024-09-18 10:36       ` Krzysztof Kozlowski

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=c51a8065-2052-4a4e-b871-c0bd8d834548@oss.nxp.com \
    --to=ciprianmarian.costea@oss.nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bogdan-gabriel.roman@nxp.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ghennadi.procopciuc@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s32@nxp.com \
    --cc=will@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).