linux-kernel - Re: [PATCH] arm: clk: Add ETH switch clock description for vf610 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f68ebe15-69ee-428a-8079-8bb05d7aa21b@lunn.ch>
Date: Thu, 20 Feb 2025 16:23:22 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Lukasz Majewski <lukma@...x.de>
Cc: Abel Vesa <abelvesa@...nel.org>, Peng Fan <peng.fan@....com>,
	Michael Turquette <mturquette@...libre.com>,
	Stephen Boyd <sboyd@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	Pengutronix Kernel Team <kernel@...gutronix.de>,
	Fabio Estevam <festevam@...il.com>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-clk@...r.kernel.org,
	imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] arm: clk: Add ETH switch clock description for vf610 SoC

> > Seems like a reasonable compromise. You would only load this driver if
> > you intend to make use of the switch...
> 
> Yes, the main use case would be the switch (after bridge ... command
> called).
> 
> However, until then we shall? have port separation.

Yes. The model Linux uses is that the ports are individual interfaces
to start with. We should keep to that model.

> > MoreThanIP is now part of Synopsys. I wounder if this IP now exists in
> > other SoCs? The press release however suggests Synopsys was
> > interesting in the high speed interfaces, not a two ports Fast
> > Ethernet switch.
> 
> I would need some detailed documentation....

Which is probably not available. You might be able to get some clues
from the Freescale datasheets, if they have kept the address spaces
separated. I don't see it as a strong requirement, given how old this
IP is, and the limited interest in supporting it over the years, My
guess is, nobody else uses it.

	Andrew