All of lore.kernel.org
 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>, Jan Kotas <jank@cadence.com>
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 v3 5/7] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board
Date: Wed, 25 Jun 2025 00:42:16 +0000	[thread overview]
Message-ID: <1727c00a-b73d-436e-8ab6-c722c13c59fd@axiado.com> (raw)
In-Reply-To: <0709a0a6-1313-452c-85e7-2926a6a03741@kernel.org>

On 6/23/2025 11:45 PM, Krzysztof Kozlowski wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 23/06/2025 19:28, Harshit Shah wrote:
>> +     memory@0 {
>> +             device_type = "memory";
>> +             /* Cortex-A53 will use following memory map */
>> +             reg = <0x00000000 0x3D000000 0x00000000 0x23000000>,
> Lowercase hex, see DTS coding style.

I missed it. I will update it to lower case.


>
>> +     cpus {
>> +             #address-cells = <2>;
>> +             #size-cells = <0>;
>> +
>> +             cpu0: cpu@0 {
>> +                     device_type = "cpu";
>> +                     compatible = "arm,cortex-a53";
>> +                     reg = <0x0 0x0>;
>> +                     enable-method = "spin-table";
>> +                     cpu-release-addr = <0x0 0x3c0013a0>;
>> +                     d-cache-size = <0x8000>;
>> +                     d-cache-line-size = <64>;
>> +                     d-cache-sets = <128>;
>> +                     i-cache-size = <0x8000>;
>> +                     i-cache-line-size = <64>;
>> +                     i-cache-sets = <256>;
>> +                     next-level-cache = <&l2>;
>> +             };
> Missing blank line between each new node. See DTS coding style.

Noted, I will update between each nodes.


>
>> +             cpu1: cpu@1 {
>> +                     device_type = "cpu";
>> +                     compatible = "arm,cortex-a53";
>> +                     reg = <0x0 0x1>;
>> +                     enable-method = "spin-table";
>> +                     cpu-release-addr = <0x0 0x3c0013a0>;
>> +                     d-cache-size = <0x8000>;
>> +                     d-cache-line-size = <64>;
>> +                     d-cache-sets = <128>;
>> +                     i-cache-size = <0x8000>;
>> +                     i-cache-line-size = <64>;
>> +                     i-cache-sets = <256>;
>> +                     next-level-cache = <&l2>;
>> +             };
>> +             cpu2: cpu@2 {
>> +                     device_type = "cpu";
>> +                     compatible = "arm,cortex-a53";
>> +                     reg = <0x0 0x2>;
>> +                     enable-method = "spin-table";
>> +                     cpu-release-addr = <0x0 0x3c0013a0>;
>> +                     d-cache-size = <0x8000>;
>> +                     d-cache-line-size = <64>;
>> +                     d-cache-sets = <128>;
>> +                     i-cache-size = <0x8000>;
>> +                     i-cache-line-size = <64>;
>> +                     i-cache-sets = <256>;
>> +                     next-level-cache = <&l2>;
>> +             };
>> +             cpu3: cpu@3 {
>> +                     device_type = "cpu";
>> +                     compatible = "arm,cortex-a53";
>> +                     reg = <0x0 0x3>;
>> +                     enable-method = "spin-table";
>> +                     cpu-release-addr = <0x0 0x3c0013a0>;
>> +                     d-cache-size = <0x8000>;
>> +                     d-cache-line-size = <64>;
>> +                     d-cache-sets = <128>;
>> +                     i-cache-size = <0x8000>;
>> +                     i-cache-line-size = <64>;
>> +                     i-cache-sets = <256>;
>> +                     next-level-cache = <&l2>;
>> +             };
>> +             l2: l2-cache0 {
>> +                     compatible = "cache";
>> +                     cache-size = <0x100000>;
>> +                     cache-unified;
>> +                     cache-line-size = <64>;
>> +                     cache-sets = <1024>;
>> +                     cache-level = <2>;
>> +             };
>> +     };
>> +
>> +     clocks {
>> +             clk_xin: clock-200000000 {
>> +                     compatible = "fixed-clock";
>> +                     #clock-cells = <0>;
>> +                     clock-frequency = <200000000>;
>> +                     clock-output-names = "clk_xin";
>> +             };
>> +             refclk: clock-125000000 {
>> +                     compatible = "fixed-clock";
>> +                     #clock-cells = <0>;
>> +                     clock-frequency = <125000000>;
>> +             };
>> +     };
>> +
>> +     soc {
>> +             compatible = "simple-bus";
>> +             ranges;
>> +             #address-cells = <2>;
>> +             #size-cells = <2>;
>> +             interrupt-parent = <&gic500>;
>> +
>> +             gic500: interrupt-controller@80300000 {
>> +                     compatible = "arm,gic-v3";
>> +                     reg = <0x00 0x80300000 0x00 0x10000>,
>> +                               <0x00 0x80380000 0x00 0x80000>;
> Does not look aligned.

Agreed. I will update the alignment.


>
>> +                     ranges;
>> +                     #interrupt-cells = <3>;
>> +                     #address-cells = <2>;
>> +                     #size-cells = <2>;
>> +                     interrupt-controller;
>> +                     #redistributor-regions = <1>;
>> +                     interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
>> +             };
>> +
>> +             /* GPIO Controller banks 0 - 7 */
>> +             gpio0: gpio-controller@80500000 {
>> +                     compatible = "cdns,gpio-r1p02";
>> +                     reg = <0x00 0x80500000 0x00  0x400>;
> Only one space, not double space.

Agreed. There is double space in every GPIO nodes, I will update the same.


Regards,

Harshit.




  reply	other threads:[~2025-06-25  0:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 17:28 [PATCH v3 0/7] Axiado AX3000 SoC and Evaluation Board Support Harshit Shah
2025-06-23 17:28 ` [PATCH v3 1/7] dt-bindings: vendor-prefixes: Add Axiado Corporation Harshit Shah
2025-06-27 20:24   ` Rob Herring (Arm)
2025-06-23 17:28 ` [PATCH v3 2/7] dt-bindings: arm: axiado: add AX3000 EVK compatible strings Harshit Shah
2025-06-24  6:33   ` Krzysztof Kozlowski
2025-06-23 17:28 ` [PATCH v3 3/7] dt-bindings: gpio: gpio-cdns: convert to YAML Harshit Shah
2025-06-24  6:34   ` Krzysztof Kozlowski
2025-06-24 23:54     ` Harshit Shah
2025-06-23 17:28 ` [PATCH v3 4/7] arm64: add Axiado SoC family Harshit Shah
2025-06-24  6:35   ` Krzysztof Kozlowski
2025-06-25  0:03     ` Harshit Shah
2025-06-23 17:28 ` [PATCH v3 5/7] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Harshit Shah
2025-06-24  6:45   ` Krzysztof Kozlowski
2025-06-25  0:42     ` Harshit Shah [this message]
2025-06-25  2:16     ` Harshit Shah
2025-06-25  6:05       ` Krzysztof Kozlowski
2025-06-26  1:31         ` Harshit Shah
2025-06-26  8:50           ` Krzysztof Kozlowski
2025-06-27  0:31             ` Harshit Shah
2025-06-27  0:47             ` Harshit Shah
2025-06-27  5:58               ` Krzysztof Kozlowski
2025-06-27 17:42         ` Harshit Shah
2025-06-27 20:10   ` Harshit Shah
2025-06-23 17:28 ` [PATCH v3 6/7] arm64: defconfig: enable the Axiado family Harshit Shah
2025-06-24  6:45   ` Krzysztof Kozlowski
2025-06-25  0:02     ` Harshit Shah
2025-06-23 17:28 ` [PATCH v3 7/7] MAINTAINERS: Add entry for Axiado Harshit Shah
2025-06-24  6:45   ` Krzysztof Kozlowski
2025-06-24 23:33     ` Harshit Shah
2025-06-25  6:06       ` 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=1727c00a-b73d-436e-8ab6-c722c13c59fd@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=jank@cadence.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.