All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 26 Jun 2025 10:50:55 +0200	[thread overview]
Message-ID: <3660b275-8513-4017-aba4-5c4432eb5b6b@kernel.org> (raw)
In-Reply-To: <a6e27c0e-0703-4444-b6e7-d4db1340e802@axiado.com>

On 26/06/2025 03:31, Harshit Shah wrote:
> On 6/24/2025 11:05 PM, Krzysztof Kozlowski wrote:
>>>
>>>
>>>>> +                     compatible = "xlnx,zynqmp-uart", "cdns,uart-r1p12";
>>>> NAK, you do not have xlnx here. Look at your SoC: name of vendor is
>>>> axiado. Not xlnx. How is your SoC called? Also zynqmp? You cannot just
>>>> randomly pick any compatibles and stuff them around.
>>>>
>>>> Please carefully read writing bindings from DT directory.
>>>
>>> We are using the "cdns,uart-r1p12" for the UART. However, that alone
>>> can't be added alone in the compatible as per the DT bindings doc.
>> Exactly. See writing bindings... or any guides/talks.
> 
> We will add the "compatible = "axiado,ax-uart", "cdns,uart-r1p12". We 
> will append in the dt-bindings doc and driver.
> 
> 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


  reply	other threads:[~2025-06-26  9:12 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 [this message]
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=3660b275-8513-4017-aba4-5c4432eb5b6b@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 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.