mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Caleb James DeLisle <cjd@cjdns.fr>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com,
	chester.a.unal@arinc9.com, daniel@makrotopia.org,
	linux@armlinux.org.uk, arinc.unal@arinc9.com,
	Landen.Chao@mediatek.com, dqfext@gmail.com,
	sean.wang@mediatek.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, naseefkm@gmail.com,
	b.larsson@gmx.com
Subject: Re: [PATCH v4 6/7] dt-bindings: net: dsa: mediatek,mt7530: add EcoNet EN751221 switches
Date: Tue, 3 Nov 2026 14:15:32 +0100	[thread overview]
Message-ID: <39cb446e-b667-4766-bd79-2635eb36166c@cjdns.fr> (raw)
In-Reply-To: <20261103-soft-lyrical-squid-c5a108@quoll>

Hello,

Thanks for the review.

On 03/11/2026 12:08, Krzysztof Kozlowski wrote:
> On Thu, Oct 29, 2026 at 06:42:01PM +0000, Caleb James DeLisle wrote:
>> The EcoNet EN751221 MIPS SoC integrates an MT7530 switch memory-mapped
>> in the SoC register space. It is similar to the econet,en7528-switch
>> except that ports 0..3 are 10/100 only, port 4 has a gigabit PHY, and
>> port 5 has no PHY, but is in some implementations connected to a
>> downstream MT7530 multi-chip module via a TRGMII link.
>>
>> The downstream MT7530 is similar to the MT7621 multi-chip module and
>> has all gigabit ports.
>>
>> Add the econet,en751221-switch compatible with the same constraints as
>> the other built-in switches and also add the econet,en751221-gswitch
>> multi-chip-module switch whose port 6 is configured as a DSA link port.
>>
>> Signed-off-by: Caleb James DeLisle <cjd@cjdns.fr>
>> ---
>>   .../bindings/net/dsa/mediatek,mt7530.yaml     | 43 ++++++++++++++++++-
>>   1 file changed, 41 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml b/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
>> index f98b9113ad12..011c94ef9554 100644
>> --- a/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
>> +++ b/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
>> @@ -29,6 +29,12 @@ description: |
>>     and the switch registers are directly mapped into SoC's memory map rather than
>>     using MDIO. The DSA driver currently doesn't support MT7620 variants.
>>   
>> +  EcoNet EN751221 SoCs have a memory mapped MT7530 with 3x 10/100 PHYs and 1x
>> +  gigabit PHY. Some EN751221 chips such as EN7513G and EN7526G have a multi-chip
>> +  module implementation of the MT7530 as well as the on-die switch. In these
>> +  packages, the multi-chip module is connected to port 5 of the on-die switch
>> +  via a TRGMII link and allows for 5 gigabit ports.
>> +
>>     There is only the standalone version of MT7531.
>>   
>>     Port 5 on MT7530 supports various configurations:
>> @@ -109,6 +115,14 @@ properties:
>>             Built-in switch of the EcoNet EN7528 SoC
>>           const: econet,en7528-switch
>>   
>> +      - description:
>> +          Built-in switch of EcoNet EN751221 SoC
> You can drop, pointless description, repeats the compatible.


Perhaps reword "On-die switch of EcoNet EN751221 SoC" to avoid confusion 
with MCM switch?


>
>> +        const: econet,en751221-switch
>> +
>> +      - description:
>> +          Multi-chip module gigabit MT7530 in EN751221 SoC
> Keep it in one line with description. No need to inflate it even more.


OK


>
>> +        const: econet,en751221-gswitch
> That's almost the same compatible, which makes me wonder if you describe
> the same device twice. Same device, same compatible.


Well, these are both MT7530 based, but one of them is on-die with the 
SoC and the other one is an MCM so for the driver they are very 
different - they're even loaded by different kmods. I think since one is 
MMIO and the other is MDIO, using the same compatible won't cause a 
driver problem - but I don't know if it's best practice to smooth over 
such a difference or not. Your advice here would be most appreciated.


Thanks,

Caleb


>
> Best regards,
> Krzysztof

  reply	other threads:[~2026-11-03 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 18:41 [PATCH v4 0/7] net: dsa: mt7530: support EcoNet EN751221 Caleb James DeLisle
2026-10-29 18:41 ` [PATCH v4 1/7] net: dsa: mt7530: get ctrl phy addr using a function Caleb James DeLisle
2026-10-29 18:41 ` [PATCH v4 2/7] dt-bindings: net: dsa: mediatek,mt7530: describe 'passthrough' hierarchy Caleb James DeLisle
2026-11-03 10:59   ` Krzysztof Kozlowski
2026-10-29 18:41 ` [PATCH v4 3/7] net: dsa: mediatek: add support for passthrough mode Caleb James DeLisle
2026-10-29 18:41 ` [PATCH v4 4/7] net: dsa: mediatek: support PLL setup on MMIO MT7530 Caleb James DeLisle
2026-10-29 18:42 ` [PATCH v4 5/7] net: dsa: mediatek: support MDIO switch downstream of MMIO switch Caleb James DeLisle
2026-10-29 18:42 ` [PATCH v4 6/7] dt-bindings: net: dsa: mediatek,mt7530: add EcoNet EN751221 switches Caleb James DeLisle
2026-11-03 11:08   ` Krzysztof Kozlowski
2026-11-03 13:15     ` Caleb James DeLisle [this message]
2026-10-29 18:42 ` [PATCH v4 7/7] net: dsa: mediatek: support EN751221 switch Caleb James DeLisle
2026-11-03 14:59 ` [PATCH v4 0/7] net: dsa: mt7530: support EcoNet EN751221 Paolo Abeni

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=39cb446e-b667-4766-bd79-2635eb36166c@cjdns.fr \
    --to=cjd@cjdns.fr \
    --cc=Landen.Chao@mediatek.com \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arinc.unal@arinc9.com \
    --cc=b.larsson@gmx.com \
    --cc=chester.a.unal@arinc9.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=matthias.bgg@gmail.com \
    --cc=naseefkm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=sean.wang@mediatek.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

all inboxes | Powered by JetHome®