mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aniket Limaye <a-limaye@ti.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Nirujogi Pratap <pratap.nirujogi@amd.com>,
	Bin Du <bin.du@amd.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, vigneshr@ti.com, nm@ti.com,
	u-kumar1@ti.com, lianfeng.ouyang@starfivetech.com,
	Ritwick.Sharma@arm.com
Subject: Re: [PATCH 1/3] dt-bindings: i2c: dw: Add DWC_i2c compatible
Date: Tue, 22 Sep 2026 10:50:17 +0200	[thread overview]
Message-ID: <c6b2123b-539e-4c37-8105-3e53a5197ed0@kernel.org> (raw)
In-Reply-To: <203f72c8-4a06-41d4-9212-9625f6be0281@ti.com>

On 21/09/2026 19:25, Aniket Limaye wrote:
> 
> On 21/09/26 19:40, Mika Westerberg wrote:
>> On Mon, Sep 21, 2026 at 04:00:52PM +0200, Krzysztof Kozlowski wrote:
>>> On 21/09/2026 13:14, Mika Westerberg wrote:
>>>> Hi,
>>>>
>>>> On Mon, Sep 21, 2026 at 01:55:23PM +0530, Aniket Limaye wrote:
>>>>> On 20/09/26 23:54, Krzysztof Kozlowski wrote:
>>>>>> On Sat, Sep 19, 2026 at 02:36:06PM +0530, Aniket Limaye wrote:
>>>>>>> Add the "snps,dwc-i2c" compatible for Synopsys Advanced I2C Controller
>>>>>>> referred as DWC_i2c. Compared to the existing "snps,designware-i2c"
>>>>>> dwc is designware, so snps,dwc-i2c = snps,designware-i2c
>>>>>>
>>>>>> I think this is *the* argument why generic compatibles are wrong.
>>>>> These are 2 different controllers with some different registers and
>>>>> vastly different register offsets.
>>>>>
>>>>> So, the official product name (short format) for the SNPS Advanced I2C
>>>>> controller is "DWC_i2c", as per SNPS' own reference document [0].
>>>>> Whereas the original "snps,designware-i2c" corresponds to the product
>>>>> name "DW_apb_i2c" as per its own databook [1].
>>>>>
>>>>> So based on this I though it'd be best to keep "dwc-i2c" close to SNPS'
>>>>> own naming, despite the fact that it does seem very similar to the
>>>>> generic "snps,designware-i2c".
>>>>>
>>>>> If you'd prefer to make it more explicit, I could change this to something
>>>>> like "snps,dwc-adv-i2c"? Although, again, this does deviate from the
>>>>> convention that SNPS uses in it's own documents.
>>>> What about just "snps,ai2c" or "snps,advanced-i2c"?
>>> Can we just drop generic compatible completely instead? The block cannot
>>> work alone, needs SoC integration.
>> Works for me.
> 
> Original intent was to try to develop a generic driver so that it could be
> re-used by other SoCs with some more work (referring to an earlier 
> series [0])
> 

I did not comment on your driver. I did not even look there.

Best regards,
Krzysztof

  reply	other threads:[~2026-09-22  8:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  9:06 [PATCH 0/3] i2c: designware: Add DWC_i2c support Aniket Limaye
2026-09-19  9:06 ` [PATCH 1/3] dt-bindings: i2c: dw: Add DWC_i2c compatible Aniket Limaye
2026-09-20 18:24   ` Krzysztof Kozlowski
2026-09-21  8:25     ` Aniket Limaye
2026-09-21 11:14       ` Mika Westerberg
2026-09-21 14:00         ` Krzysztof Kozlowski
2026-09-21 14:10           ` Mika Westerberg
2026-09-21 17:25             ` Aniket Limaye
2026-09-22  8:50               ` Krzysztof Kozlowski [this message]
2026-09-19  9:06 ` [PATCH 2/3] i2c: designware: Introduce per-variant register offset and bit-layout tables Aniket Limaye
2026-09-21 11:11   ` Mika Westerberg
2026-09-21 17:10     ` Aniket Limaye
2026-09-19  9:06 ` [PATCH 3/3] i2c: designware: Add snps,dwc-i2c support and new compatible Aniket Limaye

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=c6b2123b-539e-4c37-8105-3e53a5197ed0@kernel.org \
    --to=krzk@kernel.org \
    --cc=Ritwick.Sharma@arm.com \
    --cc=a-limaye@ti.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bin.du@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lianfeng.ouyang@starfivetech.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nm@ti.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=robh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.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®