[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d3d96cdede2f1e40ed9ae5742a0468d@walle.cc>
Date: Thu, 18 Aug 2022 16:49:49 +0200
From: Michael Walle <michael@...le.cc>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: devicetree@...r.kernel.org, netdev@...r.kernel.org,
Shawn Guo <shawnguo@...nel.org>, Li Yang <leoyang.li@....com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH devicetree 0/3] NXP LS1028A DT changes for multiple switch
CPU ports
Am 2022-08-18 16:05, schrieb Vladimir Oltean:
> The Ethernet switch embedded within the NXP LS1028A has 2 Ethernet
> ports
> towards the host, for local packet termination. In current device
> trees,
> only the first port is enabled. Enabling the second port allows having
> a
> higher termination throughput.
Is it used automatically or does the userspace has to configure
something?
> Care has been taken that this change does not produce regressions when
> using updated device trees with old kernels that do not support
> multiple
> DSA CPU ports. The only difference for old kernels will be the
> appearance of a new net device (for &enetc_port3) which will not be
> very
> useful for much of anything.
Mh, I don't understand. Does it now cause regressions or not? I mean
besides that there is a new unused interface?
I was just thinking of that systemready stuff where the u-boot might
supply its (newer) device tree to an older kernel, i.e. an older debian
or similar.
-michael
Powered by blists - more mailing lists