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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6feb419e-ee3d-4573-8820-19c70acdb426@kernel.org>
Date: Fri, 12 Sep 2025 08:37:53 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jeremy Kerr <jk@...abs.org>, Ryan Chen <ryan_chen@...eedtech.com>
Cc: "robh@...nel.org" <robh@...nel.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>,
 "andriy.shevchenko@...ux.intel.com" <andriy.shevchenko@...ux.intel.com>,
 "andi.shyti@...nel.org" <andi.shyti@...nel.org>,
 "linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
 Mo Elbadry <elbadrym@...gle.com>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "joel@....id.au" <joel@....id.au>,
 "p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
 "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>
Subject: Re: [PATCH v16 1/3] dt-bindings: i2c: aspeed: support for
 AST2600-i2cv2

On 11/09/2025 11:03, Jeremy Kerr wrote:
> Hi all,
> 
> After a bit of a chat with Ryan, some updates on this:
> 
>> 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