mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Shah <hshah@axiado.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"soc@lists.linux.dev" <soc@lists.linux.dev>
Subject: Re: [PATCH v2 4/6] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board
Date: Fri, 20 Jun 2025 21:18:47 +0000	[thread overview]
Message-ID: <bdc4408c-6fe4-48cd-bb40-3a17aed79cb6@axiado.com> (raw)
In-Reply-To: <9012cc61-b499-4213-9753-54cf4d24c822@kernel.org>

On 6/19/2025 11:08 PM, Krzysztof Kozlowski wrote:
>>>> +
>>>> +             spi_clk: spi_clk {
>>>> +                     compatible = "fixed-clock";
>>>> +                     #clock-cells = <0>;
>>>> +                     clock-frequency = <25000000>;
>>>> +             };
>>>> +
>>>> +             apb_pclk: apb_pclk {
>>> No underscores in node names, but all these look incorrect - don't you
>>> have clock controller?
>> Noted, we will remove the "_" from the nodes. We do have clock
>> controller however that is being accessed by other CPU before Linux will
>> come-up.
> What does it mean? Is the clock controller not available at all for
> Linux or any other OS?

Apologies for the confusion. Yes, clock controller is available however 
it is only accessible by another CPU which boots up before Linux comes up.

This another CPU is setting up the various output clocks (& PLLs) before 
the Linux comes up.

So, that's the reason haven not added the clock controller in this DTS 
but only will add fixed clocks.

>
>> So, the purpose of this clock nodes is to calculate the frequencies for
>> other peripherals. (We will update the nodes with clock-<freq>)
> You do not calculate any frequencies here... You created nodes for fixed
> clocks but I question here whether these are fixed clocks.
>
> Where are these clocks located exactly?

Yes, those clocks are fixed clocks, as it is being controlled by other 
CPU and coming to A53 as fixed clocks.

I will take care of the format in the next revision.

>
>
> Best regards,
> Krzysztof



  reply	other threads:[~2025-06-20 21:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  4:31 [PATCH v2 0/6] Axiado AX3000 SoC and Evaluation Board Support Harshit Shah
2025-06-16  4:31 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Axiado Corporation Harshit Shah
2025-06-16  4:31 ` [PATCH v2 2/6] dt-bindings: arm: axiado: add AX3000 EVK compatible strings Harshit Shah
2025-06-16  6:05   ` Krzysztof Kozlowski
2025-06-16 21:13     ` Harshit Shah
2025-06-17  6:08       ` Krzysztof Kozlowski
2025-06-16  4:31 ` [PATCH v2 3/6] dt-bindings: gpio: gpio-cdns: convert to YAML Harshit Shah
2025-06-16  6:05   ` Krzysztof Kozlowski
2025-06-18 21:09     ` Harshit Shah
2025-06-16  4:31 ` [PATCH v2 4/6] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Harshit Shah
2025-06-16  6:09   ` Krzysztof Kozlowski
2025-06-19 22:41     ` Harshit Shah
2025-06-20  6:08       ` Krzysztof Kozlowski
2025-06-20 21:18         ` Harshit Shah [this message]
2025-06-22  9:49           ` Krzysztof Kozlowski
2025-06-23  5:56             ` Harshit Shah
2025-06-23  6:04               ` Krzysztof Kozlowski
2025-06-16  6:10   ` Krzysztof Kozlowski
2025-06-19 23:52     ` Harshit Shah
2025-06-16 13:57   ` Rob Herring
2025-06-19 23:09     ` Harshit Shah
2025-06-16  4:31 ` [PATCH v2 5/6] arm64: add support for ARCH_AXIADO Harshit Shah
2025-06-16  4:31 ` [PATCH v2 6/6] MAINTAINERS: Add entry for AXIADO Harshit Shah

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=bdc4408c-6fe4-48cd-bb40-3a17aed79cb6@axiado.com \
    --to=hshah@axiado.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=soc@lists.linux.dev \
    --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

all inboxes | Powered by JetHome®