mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, wsa+renesas@sang-engineering.com,
	Ryan.Wanner@microchip.com, romain.sioen@microchip.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ARM: dts: Add support for pcb8385
Date: Fri, 28 Nov 2025 10:08:45 +0100	[thread overview]
Message-ID: <da46dd3f-7259-40a6-b9cd-2586ee5a4aed@kernel.org> (raw)
In-Reply-To: <20251127092450.h3t5vxdfvseartx2@DEN-DL-M31836.microchip.com>

On 27/11/2025 10:24, Horatiu Vultur wrote:
> The 11/26/2025 11:24, Krzysztof Kozlowski wrote:
>>
> 
> Hi Krzysztof,
> 
>>> +
>>> +&flx0 {
>>> +     atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_TWI>;
>>> +     status = "okay";
>>> +
>>> +     i2c0: i2c@600 {
>>
>> You added a label, so this feels like a new node, but then you miss
>> compatible and status feels redundant.
> 
> Ah.. OK. I didn't want to add a new node.
> 
>>
>> If this is override, you should rather override by labels/phandles in
>> the first place. Even when overriding by full node path, you should not
>> add custom labels - they belong to the base SoC.
> 
> I can remove the label.
> So, when I want to override or extend with new properties I should
> labels?


Yes, child of serial engine should still be extended by label/phandle,
unless this SoC subsystem has different rule.

Best regards,
Krzysztof

  reply	other threads:[~2025-11-28  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 10:01 [PATCH v3 0/2] ARM: add " Horatiu Vultur
2025-11-26 10:01 ` [PATCH v3 1/2] dt-bindings: arm: at91: add lan966 pcb8385 board Horatiu Vultur
2025-11-26 10:01 ` [PATCH v3 2/2] ARM: dts: Add support for pcb8385 Horatiu Vultur
2025-11-26 10:24   ` Krzysztof Kozlowski
2025-11-27  9:24     ` Horatiu Vultur
2025-11-28  9:08       ` Krzysztof Kozlowski [this message]
2025-11-28 13:04         ` Horatiu Vultur
2025-11-29  9:15           ` Krzysztof Kozlowski
2025-11-26 22:46 ` [PATCH v3 0/2] ARM: add " Rob Herring

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=da46dd3f-7259-40a6-b9cd-2586ee5a4aed@kernel.org \
    --to=krzk@kernel.org \
    --cc=Ryan.Wanner@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh@kernel.org \
    --cc=romain.sioen@microchip.com \
    --cc=wsa+renesas@sang-engineering.com \
    /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®