From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harshit Shah <hshah@axiado.com>, 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: Fri, 27 Jun 2025 07:58:36 +0200 [thread overview]
Message-ID: <4d4bf02a-4c0a-4051-bed2-8a089d310ad2@kernel.org> (raw)
In-Reply-To: <72ac73e7-a201-4001-a3ca-b13fb78c980b@axiado.com>
On 27/06/2025 02:47, Harshit Shah wrote:
>>> Is this name look good?
>> No, all compatibles for SoC must be SoC specific. Take any recent
>> Qualcomm SM8650 or SM8750 as example.
>>
>> I asked to read writing bindings. Did you read it? It covers exactly
>> this case.
>>
>> Best regards,
>> Krzysztof
>
>
> Extremely sorry for the last reply. It got messed up in formatting,
> re-sending the same.
>
>
> Thank you for the references.
>
> Yes, I missed the point in the writing bindings doc. It says the following:
>
>
> "For sub-blocks/components of bigger device (e.g. SoC blocks) use rather
> device-based compatible (e.g. SoC-based compatible),
>
> instead of custom versioning of that component. For example use
> "vendor,soc1234-i2c" instead of "vendor,i2c-v2"."
>
>
> (Ref:
> https://elixir.bootlin.com/linux/v6.15.3/source/Documentation/devicetree/bindings/writing-bindings.rst#L79)
>
>
> # We need to add the full SoC name instead of versioning. e.g.
> compatible should contain full SoC name ax3000.
Yes.
>
>
> Another example, we have seen is the designware I2C IP is used by MSCC,
> ocelot chipset.
>
> It is showing as below in the following:
> (https://elixir.bootlin.com/linux/v6.16-rc3/source/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml)
>
>
> i2c@100400 {
>
> compatible = "mscc,ocelot-i2c", "snps,designware-i2c";
>
> reg = <0x100400 0x100>, <0x198 0x8>;
>
> pinctrl-0 = <&i2c_pins>;
>
> pinctrl-names = "default";
>
> interrupts = <8>;
>
> clocks = <&ahb_clk>;
>
> };
>
>
> # We will add this compatible in the existing driver
> (drivers/tty/serial/xilinx_uartps.c) &
>
> bindings (Documentation/devicetree/bindings/serial/cdns,uart.yaml) since
> the IP is common.
>
>
> As per the above examples, I see two types of bindings.
>
> 1. compatible = "axiado,ax3000-uart", "cdns,uart-r1p12"
This one. Thank you.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-27 5:58 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
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 [this message]
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=4d4bf02a-4c0a-4051-bed2-8a089d310ad2@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hshah@axiado.com \
--cc=jank@cadence.com \
--cc=krzk+dt@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®