Subject: Re: [PATCH v16 1/3] dt-bindings: i2c: aspeed: support for
AST2600-i2cv2

On 11/09/2025 11:03, Jeremy Kerr wrote:

quoted

Hi all,

After a bit of a chat with Ryan, some updates on this:

quoted

The question was more: it sounds like you're switching between
*fundamentally different* hardware units with the mux switch - not
just a different register interface for the same peripheral hardware.
Is that the case?

Turns out: no. The controller core is the same, but what gets muxed
in/out is more of a compatibility interface. This provides an
ast2500-like register set to the ast2600 i2c peripheral.

If you had two separate bindings, how would you represent it in DTS? Two
device nodes, right? That's confusing, because there is only one device.

If the device can present or change its programming interface, it is still that
device, so still one binding for it. And that device driver will handle both (or
one) programming models.

I remember now the problem we talk about, but I don't get what exactly you
want to solve/discuss. Anyway any discussion should be about newest patch,
not something from February, so if you still have concerns please raise them at
v18 (or whichever version is now).

Best regards,
Krzysztof

Hello Krzysztof, 
	Thanks a lot.
	That I submitted with v18. (that add reason in commit why I add in yaml.
	So, let's back to v18 give me more feedback, that I can fulfill.
	Appreciate your help.
v18 https://lore.kernel.org/all/20250820051832.3605405-2-ryan_chen@aspeedtech.com/ (local)

Ryan