From: Paul Barker <paul.barker@sancloud.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone: switch to new cpsw switch drv
Date: Fri, 6 Aug 2021 08:12:30 +0100 [thread overview]
Message-ID: <20210806081230.3afd6e26.paul.barker@sancloud.com> (raw)
In-Reply-To: <20210805230956.7379-1-grygorii.strashko@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Fri, 6 Aug 2021 02:09:56 +0300
Grygorii Strashko <grygorii.strashko@ti.com> wrote:
> 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 - it's safe
> to switch drivers.
>
> So, Switch BeagleBone boards to use new cpsw switch driver. Those boards
> have or 2 Ext. port wired and configured in dual_mac mode by default, or
> only 1 Ext. port.
>
> For am335x-sancloud-bbe-common.dtsi also removed duplicated davinci_mdio DT
> nodes which already defined in am335x-bone-common.dtsi.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
>
> changes in v2:
> - commit message updated to indicate duplicated nodes removal in am335x-sancloud-bbe-common.dtsi
> - dropped phy-handle for cpsw port in am335x-sancloud-bbe-common.dtsi
Thanks for the quick response to my feedback.
Reviewed-by: Paul Barker <paul.barker@sancloud.com>
--
Paul Barker
Principal Software Engineer
SanCloud Ltd
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-08-06 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 23:09 [PATCH v2] ARM: dts: am335x-bone: switch to new cpsw switch drv Grygorii Strashko
2021-08-06 6:31 ` Tony Lindgren
2021-08-06 7:12 ` Paul Barker [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-05 17:29 Grygorii Strashko
2021-08-05 17:58 ` Paul Barker
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=20210806081230.3afd6e26.paul.barker@sancloud.com \
--to=paul.barker@sancloud.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).