All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Stefan Wahren <wahrenst@gmx.net>,
	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,
	Simon Horman <horms@kernel.org>
Subject: Re: [net-next v5 2/6] ARM: dts: nxp: mxs: Adjust the imx28.dtsi L2 switch description
Date: Thu, 17 Apr 2025 08:33:34 +0200	[thread overview]
Message-ID: <20250417083334.69b565b0@wsk> (raw)
In-Reply-To: <2c9a5438-40f1-4196-ada9-bfb572052122@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

Hi Andrew,

> > > -		eth_switch: switch@800f8000 {
> > > -			reg = <0x800f8000 0x8000>;
> > > +		eth_switch: switch@800f0000 {
> > > +			compatible = "nxp,imx28-mtip-switch";
> > > +			reg = <0x800f0000 0x20000>;
> > > +			interrupts = <100>, <101>, <102>;
> > > +			clocks = <&clks 57>, <&clks 57>, <&clks
> > > 64>, <&clks 35>;
> > > +			clock-names = "ipg", "ahb", "enet_out",
> > > "ptp"; status = "disabled";  
> > from my understanding of device tree this file should describe the
> > hardware, not the software implementation. After this change the
> > switch memory region overlaps the existing mac0 and mac1 nodes.
> > 
> > Definition in the i.MX28 reference manual:
> > ENET MAC0 ENET 0x800F0000 - 0x800F3FFF 16KB
> > ENET MAC1 ENET 0x800F4000 - 0x800F7FFF 16KB
> > ENT Switch SWITCH 0x800F8000 - 0x800FFFFF 32KB
> > 
> > I'm not the expert how to solve this properly. Maybe two node
> > references to mac0 and mac1 under eth_switch in order to allocate
> > the memory regions separately.  
> 
> I get what you are saying about describing the hardware, but...
> 
> The hardware can be used in two different ways.
> 
> 1) Two FEC devices, and the switch it left unused.
> 
> For this, it makes sense that each FEC has its own memory range, there
> are two entries, and each has a compatible, since there are two
> devices.
> 
> 2) A switch and MAC conglomerate device, which makes use of all three
>    blocks in a single driver.
> 
> The three hardware blocks have to be used as one consistent whole, by
> a single driver. There is one compatible for the whole. Given the
> ranges are contiguous, it makes little sense to map them individually,
> it would just make the driver needlessly more complex.
> 
> It should also be noted that 1) and 2) are mutually exclusive, so i
> don't think it matters the address ranges overlap. Bad things are
> going to happen independent of this if you enable both at once.
> 

+1

>       Andrew


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2025-04-17  6:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 14:01 [net-next v5 0/6] net: mtip: Add support for MTIP imx287 L2 switch driver Lukasz Majewski
2025-04-14 14:01 ` [net-next v5 1/6] dt-bindings: net: Add MTIP L2 switch description Lukasz Majewski
2025-04-15 22:08   ` Rob Herring
2025-04-16  7:36     ` Lukasz Majewski
2025-04-16 18:46   ` Stefan Wahren
2025-04-17  6:38     ` Lukasz Majewski
2025-04-14 14:01 ` [net-next v5 2/6] ARM: dts: nxp: mxs: Adjust the imx28.dtsi " Lukasz Majewski
2025-04-16 19:15   ` Stefan Wahren
2025-04-16 21:58     ` Andrew Lunn
2025-04-16 22:39       ` Stefan Wahren
2025-04-17  6:36         ` Lukasz Majewski
2025-04-17  6:33       ` Lukasz Majewski [this message]
2025-04-14 14:01 ` [net-next v5 3/6] ARM: dts: nxp: mxs: Adjust XEA board's DTS to support L2 switch Lukasz Majewski
2025-04-16 18:27   ` Stefan Wahren
2025-04-14 14:01 ` [net-next v5 4/6] net: mtip: The L2 switch driver for imx287 Lukasz Majewski
2025-04-15  1:43   ` Andrew Lunn
2025-04-17 10:32   ` Stefan Wahren
2025-04-14 14:01 ` [net-next v5 5/6] ARM: mxs_defconfig: Update mxs_defconfig to 6.15-rc1 Lukasz Majewski
2025-04-16 14:41   ` Stefan Wahren
2025-04-16 16:47     ` Fabio Estevam
2025-04-17  7:33     ` Lukasz Majewski
2025-04-14 14:01 ` [net-next v5 6/6] ARM: mxs_defconfig: Enable CONFIG_FEC_MTIP_L2SW to support MTIP L2 switch Lukasz Majewski
2025-04-16 18:20   ` Stefan Wahren

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=20250417083334.69b565b0@wsk \
    --to=lukma@denx.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@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=horms@kernel.org \
    --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=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 \
    --cc=wahrenst@gmx.net \
    /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.