archive mirror
 help / color / mirror / Atom feed
From: Grygorii Strashko <>
To: Tony Lindgren <>
Cc: <>, <>,
	Sekhar Nori <>,
	Vignesh Raghavendra <>,
	Murali Karicheri <>,
	Grygorii Strashko <>
Subject: [PATCH next 0/3] ARM: dts: am437x: switch to new cpsw switch drv
Date: Fri, 11 Sep 2020 01:25:05 +0300	[thread overview]
Message-ID: <> (raw)

Hi Tony,

Since Kernel v5.5 commits:
 111cf1ab4da3 ("net: ethernet: ti: introduce cpsw switchdev based driver part 2 - switch")
 ed3525eda4c4 ("net: ethernet: ti: introduce cpsw switchdev based driver part 1 - dual-emac")
the new CPSW driver with switchdev support has been introduced and one
am571x-idk board was converted to use it. And since that time (Nov 2019) no
significant issues were reported for the new CPSW driver.

Therefore it's time to switch all am437x boards to use new cpsw switch
driver. Those boards have 1 or 2 Ext. ports wired and configured in dual_mac mode
by default. The dual_mac mode has been preserved the same way between
legacy and new driver, and one port devices works the same as 1 dual_mac port,
so it's safe to switch drivers.

Grygorii Strashko (3):
  ARM: dts: am437x-l4: add dt node for new cpsw switchdev driver
  ARM: dts: am437x: switch to new cpsw switch drv
  ARM: dts: am437x-l4: drop legacy cpsw dt node

 arch/arm/boot/dts/am4372.dtsi        |  4 +-
 arch/arm/boot/dts/am437x-cm-t43.dts  | 14 +++--
 arch/arm/boot/dts/am437x-gp-evm.dts  | 13 +++--
 arch/arm/boot/dts/am437x-idk-evm.dts | 13 +++--
 arch/arm/boot/dts/am437x-l4.dtsi     | 77 +++++++++++++++-------------
 arch/arm/boot/dts/am437x-sk-evm.dts  | 14 +++--
 arch/arm/boot/dts/am43x-epos-evm.dts | 13 +++--
 7 files changed, 78 insertions(+), 70 deletions(-)


             reply	other threads:[~2020-09-10 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 22:25 Grygorii Strashko [this message]
2020-09-11  9:55 ` [PATCH next 0/3] ARM: dts: am437x: switch to new cpsw switch drv Grygorii Strashko
2020-09-10 22:25 Grygorii Strashko
2020-09-25 11:32 ` Tony Lindgren

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).