From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Frank Wunderlich" <frank-w@public-files.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, erkin.bozoglu@xeront.com
Subject: Re: Aw: Re: Re: Re: Re: Re: [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5
Date: Fri, 9 Jun 2023 16:34:03 +0200 [thread overview]
Message-ID: <e80e29f3-9085-f1e3-feb9-23b85cc0c914@gmail.com> (raw)
In-Reply-To: <8f27983d-0b1d-47f1-9219-f609423c9fb6@arinc9.com>
On 03/06/2023 12:48, Arınç ÜNAL wrote:
> On 29.05.2023 16:40, Matthias Brugger wrote:
>>
>>
>> On 12/04/2023 19:06, Arınç ÜNAL wrote:
>>> On 12.04.2023 19:53, Frank Wunderlich wrote:
>>>> Hi
>>>>
>>>>> Gesendet: Mittwoch, 12. April 2023 um 18:21 Uhr
>>>>> Von: "Arınç ÜNAL" <arinc.unal@arinc9.com>
>>>>>> thanks, it changes the master when i upgrade iproute to 6.1 (from debian
>>>>>> bullseye-backports), but i cannot do any traffic on it after switching to
>>>>>> gmac1...
>>>>>>
>>>>>> 5: wan@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
>>>>>> state UP group default qlen 1000
>>>>>> link/ether f2:d2:51:56:cd:3d brd ff:ff:ff:ff:ff:ff
>>>>>> inet 192.168.0.11/24 scope global wan
>>>>>> valid_lft forever preferred_lft forever
>>>>>>
>>>>>> see no p5-TX/gmac-rx
>>>>
>>>>> Did you apply the vlan and flooding fix patches from Richard?
>>>>
>>>> have now applied all patches i've found from richard (which are all rejected):
>>>>
>>>> fe4495bb3cc2 2023-02-12 Fix setting up CPU and User ports to be in the
>>>> correct mode during setup and when toggling vlan_filtering on a bridge
>>>> port. (HEAD -> 6.3-rc)
>>>> b0641f3e1a69 2023-02-12 Fix Flooding: Disable by default on User ports and
>>>> Enable on CPU ports
>>>> cb04b3451524 2023-02-12 Do not add all User ports to the CPU by default.
>>>> This will break Multi CPU when added a seperate patch. It will be
>>>> overwritten by .port_enable and since we are forcing output to a port via
>>>> the Special Tag this is not needed.
>>>>
>>>> and now it seems working and is clear ;)
>>>>
>>>> root@bpi-r2:~# ip l show wan
>>>> 5: wan@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
>>>> UP mode DEFAULT group default qlen 1000
>>>> link/ether f2:d2:51:56:cd:3d brd ff:ff:ff:ff:ff:ff
>>>>
>>>> iperf3
>>>> [ ID] Interval Transfer Bitrate Retr
>>>> [ 5] 0.00-10.00 sec 1.09 GBytes 940 Mbits/sec 0 sender
>>>> [ 5] 0.00-10.03 sec 1.09 GBytes 936 Mbits/sec receiver
>>>>
>>>>
>>>> iperf3 -R
>>>> [ ID] Interval Transfer Bitrate Retr
>>>> [ 5] 0.00-10.04 sec 1.09 GBytes 936 Mbits/sec 0 sender
>>>> [ 5] 0.00-10.00 sec 1.09 GBytes 938 Mbits/sec receiver
>>>>
>>>>
>>>> how do you deal with these patches? do you include them into your mt7530
>>>> fixes series? they (and vladimirs preferred cpu-port) need to be applied
>>>> before these DTS-changes
>>>
>>> Dealing with this is the last step on my tasklist. Take a look:
>>>
>>> https://arinc9.notion.site/mt7530-c-improvements-bbfdc2ceb958484b9627297b88bc6d4a
>>>
>>
>> I'm a bit lost here. @frank can this be merged now or are there still
>> oustanding issues. It seems to me that not, but just in case...
>
> I fixed the network connectivity issue on the MT7530 DSA sudriver which was the
> main problem this patch series would cause. I don't see an issue that should
> block this series anymore.
>
> With the current MT7530 DSA sudriver, port 5 will be the active CPU port instead
> of 6. I've got a patch series to prefer port 6 instead but in the meantime, this
> patch series should be good to apply.
>
> Arınç
Applied now, thanks!
prev parent reply other threads:[~2023-06-09 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:25 [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 1/5] arm: dts: mt7623: add gmacs to mt7623.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 2/5] arm: dts: mt7623: add mt7530 switch to mt7623a.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 3/5] arm: dts: mt7623: change mt7530 switch address arinc9.unal
2023-02-10 18:25 ` [PATCH v3 4/5] arm: dts: mt7623: enable flow control on port@6 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 5/5] arm: dts: mt7623: add port@5 as CPU port arinc9.unal
2023-02-18 7:00 ` [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5 Arınç ÜNAL
2023-02-18 10:24 ` Aw: " Frank Wunderlich
2023-02-18 10:49 ` Arınç ÜNAL
2023-02-18 12:18 ` Aw: " Frank Wunderlich
2023-02-18 17:02 ` Arınç ÜNAL
2023-02-18 19:11 ` Frank Wunderlich
2023-02-18 19:34 ` Arınç ÜNAL
2023-02-19 13:52 ` Aw: " Frank Wunderlich
2023-04-12 12:49 ` Frank Wunderlich
2023-04-12 14:31 ` Arınç ÜNAL
2023-04-12 15:11 ` Aw: " Frank Wunderlich
2023-04-12 16:21 ` Arınç ÜNAL
2023-04-12 16:53 ` Aw: " Frank Wunderlich
2023-04-12 17:06 ` Arınç ÜNAL
2023-05-29 13:40 ` Matthias Brugger
2023-06-03 10:48 ` Arınç ÜNAL
2023-06-09 14:34 ` Matthias Brugger [this message]
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=e80e29f3-9085-f1e3-feb9-23b85cc0c914@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@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).