Netdev List
 help / color / mirror / Atom feed
From: Jesse Van Gavere <jesse.vangavere@scioteq.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"woojung.huh@microchip.com" <woojung.huh@microchip.com>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
	"olteanv@gmail.com" <olteanv@gmail.com>
Subject: DSA to switchdev (TI CPSW) ethernet ports
Date: Thu, 28 Nov 2024 14:01:23 +0000	[thread overview]
Message-ID: <PASP264MB5297F50F5E2118BBFEA191CAFC292@PASP264MB5297.FRAP264.PROD.OUTLOOK.COM> (raw)

Hello,

I have a question in regards to connecting switchdev ports (TI AM62 CPSW in my case) to a switch configured in the DSA framework.
My setup is two KSZ9896Cs connected, one to each port of the AM62x.
Using something like cpsw_port1/2 as the ethernet for the conduit port fails I presume in of_find_net_device_by_node(ethernet) as both eth seem to be under cpsw3g which is the actual ethernet.

So when changing the ethernet for the conduit port to cpsw3g I can actually get switch working, and I see it registers under eth0 of the ethernet, however when the second switch tries to come up it fails because it tries to register a dsa folder under eth0 again.

I'm kind of at a loss what the correct solution here would be, or if this is currently even supported to connect e.g. a cpsw port to a conduit port, if that would not be the case, what is the suggested work I'd best be doing to actually get this working?

Kind regards,
Jesse Van Gavere

             reply	other threads:[~2024-11-28 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 14:01 Jesse Van Gavere [this message]
2024-11-28 14:19 ` DSA to switchdev (TI CPSW) ethernet ports Vladimir Oltean
2024-11-28 15:42   ` Jesse Van Gavere
2024-11-28 15:46     ` Vladimir Oltean

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=PASP264MB5297F50F5E2118BBFEA191CAFC292@PASP264MB5297.FRAP264.PROD.OUTLOOK.COM \
    --to=jesse.vangavere@scioteq.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=woojung.huh@microchip.com \
    /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