public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Richard Cochran <richardcochran@gmail.com>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: net: Add MTIP L2 switch description
Date: Sun, 30 Mar 2025 11:47:32 +0200	[thread overview]
Message-ID: <564768c3-56f0-4236-86e6-00cacb7b6e7d@kernel.org> (raw)
In-Reply-To: <20250329231004.4432831b@wsk>

On 29/03/2025 23:10, Lukasz Majewski wrote:
>>> +  
>>
>> If this is ethernet switch, why it does not reference ethernet-switch
>> schema? or dsa.yaml or dsa/ethernet-ports? I am not sure which one
>> should go here, but surprising to see none.
> 
> It uses:
> $ref:·ethernet-controller.yaml#
> 
> for "ports".
> 
> Other crucial node is "mdio", which references $ref: mdio.yaml#

These are children, I am speaking about this device node.

> 
>>
>>> +properties:
>>> +  compatible:
>>> +    const: nxp,imx287-mtip--switch  
>>
>> Just one -.
>>
> 
> Ok.
> 
>>> +
>>> +  reg:
>>> +    maxItems: 1
>>> +    description:
>>> +      The physical base address and size of the MTIP L2 SW module
>>> IO range  
>>
>> Wasn't here, drop.
>>
> 
> The 'reg' property (reg = <0x800f0000 0x20000>;) is defined in
> imx28.dtsi, where the SoC generic properties (as suggested by Andrew -
> like clocks, interrupts, clock-names) are moved.

Drop description, not the reg. Reg was in the previous version. You
added random changes here, not coming from the previous review.

Best regards,
Krzysztof

  reply	other threads:[~2025-03-30  9:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 13:35 [PATCH v2 0/4] net: mtip: Add support for MTIP imx287 L2 switch driver Lukasz Majewski
2025-03-28 13:35 ` [PATCH v2 1/4] dt-bindings: net: Add MTIP L2 switch description Lukasz Majewski
2025-03-28 14:07   ` Krzysztof Kozlowski
2025-03-29 22:10     ` Lukasz Majewski
2025-03-30  9:47       ` Krzysztof Kozlowski [this message]
2025-03-30 21:04         ` Lukasz Majewski
2025-03-31  6:30           ` Krzysztof Kozlowski
2025-03-31  7:19             ` Lukasz Majewski
2025-03-28 18:23   ` Andrew Lunn
2025-03-30  6:36     ` Lukasz Majewski
2025-03-28 18:30   ` Andrew Lunn
2025-03-30  6:38     ` Lukasz Majewski
2025-03-29  1:37   ` Rob Herring (Arm)
2025-03-29 17:09   ` Rob Herring
2025-03-29 21:16     ` Lukasz Majewski
2025-03-28 13:35 ` [PATCH v2 2/4] ARM: dts: nxp: mxs: Adjust the imx28.dtsi " Lukasz Majewski
2025-03-28 13:35 ` [PATCH v2 3/4] ARM: dts: nxp: mxs: Adjust XEA board's DTS to support L2 switch Lukasz Majewski
2025-03-28 13:35 ` [PATCH v2 4/4] net: mtip: The L2 switch driver for imx287 Lukasz Majewski
2025-03-28 14:19   ` Krzysztof Kozlowski
2025-03-31  8:06     ` Lukasz Majewski
2025-03-28 19:30   ` Andrew Lunn
2025-03-30 20:20     ` Lukasz Majewski
2025-03-30 22:01       ` Andrew Lunn
2025-03-31  7:00         ` Lukasz Majewski
2025-03-28 13:43 ` [PATCH v2 0/4] net: mtip: Add support for MTIP imx287 L2 switch driver Jakub Kicinski
2025-03-28 13:49   ` Lukasz Majewski

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=564768c3-56f0-4236-86e6-00cacb7b6e7d@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukma@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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