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: Thu, 5 Nov 2026 22:47:10 +0100	[thread overview]
Message-ID: <8cc1d8d6-c563-4eb7-a738-5ba51ae60ac0@cjdns.fr> (raw)
In-Reply-To: <7c15c254-d157-4f5b-bfae-06a5301af222@kernel.org>


On 04/11/2026 08:20, Krzysztof Kozlowski wrote:
> On 03/11/2026 14:15, Caleb James DeLisle wrote:
>>>> +        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.
>>
> The drivers do not matter - we have one compatible for I2C/SPI/Serial
> devices as well. The only question is about the hardware, what are these
> devices and what are you here exactly describing. Compatible is en751221
> but you call it MT7530, so even more confusion.


Let me address these in reverse order: The compatibles are 
econet,en751221-switch and econet,en751221-gswitch but the switch is an 
MT7530. This is a convention used for this switch: When it is integrated 
in an SoC and has customization for that SoC, it is identified using the 
name of the SoC suffixed by "-switch" (except in the case of 
mediatek,mt7621 where it takes the exact name of the SoC, but this looks 
like it was a mistake).


Regarding the en751221-switch vs. en751221-gswitch dichotomy, the 
meaningful difference to the DT is that the gswitch is a 
multi-chip-module so the CPU port is phy-mode "trgmii", and on the 
on-die switch it's "internal" since there's no PHY between it and the 
CPU. Moreover the gswitch requires the mediatek,mcm; attribute while the 
on-die switch forbids it. I can of course relax the restrictions so they 
can use the same compatible, but I don't know which way is most 
appropriate so I would like to follow your advice.


Thanks,

Caleb


>
> Best regards,
> Krzysztof

  reply	other threads:[~2026-11-05 21:47 UTC|newest]

Thread overview: 14+ 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
2026-11-04  7:20       ` Krzysztof Kozlowski
2026-11-05 21:47         ` 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=8cc1d8d6-c563-4eb7-a738-5ba51ae60ac0@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®