From: Andrew Lunn <andrew@lunn.ch>
To: Lukasz Majewski <lukma@denx.de>
Cc: Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-clk@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm: clk: Add ETH switch clock description for vf610 SoC
Date: Wed, 19 Feb 2025 21:58:54 +0100 [thread overview]
Message-ID: <3cebe152-6326-454c-9da6-5cf5a64f71c9@lunn.ch> (raw)
In-Reply-To: <20250219114936.3546530-1-lukma@denx.de>
On Wed, Feb 19, 2025 at 12:49:36PM +0100, Lukasz Majewski wrote:
> The NXP's vf610 soc is equipped with L2 switch IP block from More
> Than IP (MTIP) vendor.
>
> It requires special clock (VF610_CLK_ESW) to be operational.
So you have a driver for this switch? It has been talked about in the
past, but nobody made any progress with it. Ah, it was you in 2020. It
will be interesting to see what you came up with in the end, pure
switchdev or a DSA driver.
Andrew
next prev parent reply other threads:[~2025-02-19 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:49 [PATCH] arm: clk: Add ETH switch clock description for vf610 SoC Lukasz Majewski
2025-02-19 12:06 ` Krzysztof Kozlowski
2025-02-19 12:18 ` Fabio Estevam
2025-02-19 20:58 ` Andrew Lunn [this message]
2025-02-19 22:38 ` Lukasz Majewski
2025-02-20 13:39 ` Andrew Lunn
2025-02-20 14:48 ` Lukasz Majewski
2025-02-20 15:23 ` Andrew Lunn
2025-02-20 16:05 ` 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=3cebe152-6326-454c-9da6-5cf5a64f71c9@lunn.ch \
--to=andrew@lunn.ch \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--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