netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@kernel-space.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: mv88e6321, dual cpu port
Date: Tue, 10 Jan 2023 11:23:58 +0100 (CET)	[thread overview]
Message-ID: <ed027411-c1ec-631a-7560-7344c738754e@kernel-space.org> (raw)
In-Reply-To: <Y7yIK4a8mfAUpQ2g@lunn.ch>

Hi Andrew,

thanks a lot for the prompt reply,

actually, seems i can use both cpu ports by
some brctl lines:

ip link add name br0 type bridge
ip link add name br1 type bridge
brctl addif br0 eth0
brctl addif br1 eth1

I verified looking the tx_packets statistics (ethtool -S)
and both eth0 and eth1 ports are used.

Is it something that may work, eventually as a workaround ?

Also, could you help me to know the kernel version
implementing dual cpu port properly ?

I cannot actually upgrade the kernel, due to cpu producer
customizations that are not mainlined, so would try to
downgrade the driver.

Thanks a lot,
regards,
angelo

On Mon, 9 Jan 2023, Andrew Lunn wrote:

> On Mon, Jan 09, 2023 at 09:40:06PM +0100, Angelo Dureghello wrote:
>> Hi All,
>>
>> using kernel 5.4.70,
>> just looking for confirmation this layout
>> can work:
>>
>>    eth0 -> cpu port (port5, mii)  bridging port3 and 4
>>    eth1 -> cpu port (port6, rgmii)  bridging port0, 1, 2
>>
>> My devicetree actaully defines 2 cpu ports, it seems
>> to work, but please let me know if you see any
>> possible issue.
>
> Dual CPU ports is not supported with 5.4.70. Everything will go over
> the first cpu port in DT.
>
>    Andrew
>

  reply	other threads:[~2023-01-10 10:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 20:40 mv88e6321, dual cpu port Angelo Dureghello
2023-01-09 21:33 ` Andrew Lunn
2023-01-10 10:23   ` Angelo Dureghello [this message]
2023-01-10 22:22     ` Vladimir Oltean
2023-01-10 23:02       ` Andrew Lunn
2023-01-23  8:52         ` Angelo Dureghello
2023-01-23 11:28           ` Vladimir Oltean
2023-01-23 13:26             ` Angelo Dureghello
2023-01-23 19:18               ` Vladimir Oltean
2023-01-23 20:08                 ` Andrew Lunn
2023-01-24  7:21                   ` Angelo Dureghello
2023-01-24 11:41                     ` Vladimir Oltean
2023-01-24 13:57                     ` Andrew Lunn
2023-01-25  9:04                       ` Angelo Dureghello
2023-02-06 10:43                       ` Angelo Dureghello
2023-02-06 13:24                         ` Andrew Lunn
2023-02-16 11:20                       ` Angelo Dureghello
2023-02-16 12:50                         ` Vladimir Oltean
2023-02-16 12:59                           ` Andrew Lunn
2023-02-16 15:31                             ` Vladimir Oltean
2023-02-16 18:39                               ` Angelo Dureghello
2023-02-18 13:30                                 ` Vladimir Oltean
2023-02-18 13:56                                   ` Russell King (Oracle)
2023-02-16 14:24                           ` Angelo Dureghello

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=ed027411-c1ec-631a-7560-7344c738754e@kernel-space.org \
    --to=angelo@kernel-space.org \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).