From: Mark Brown <broonie@kernel.org>
To: Aniket Limaye <a-limaye@ti.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, lianfeng.ouyang@starfivetech.com,
s-jain1@ti.com, andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH v5 1/2] dt-bindings: i2c: Add Synopsys DWC_i2c controller
Date: Thu, 12 Nov 2026 18:40:51 +0000 [thread overview]
Message-ID: <77286fa5-5952-4e02-9c4d-040b047cc2b5@sirena.org.uk> (raw)
In-Reply-To: <fdeee43b-9a27-43b2-9193-7b2db468e9c0@ti.com>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On Thu, Nov 12, 2026 at 11:46:27PM +0530, Aniket Limaye wrote:
> So if I understand it correctly,
> 1. you'd rather the driver have a generic compatible such that we can have
> distro kernels not requiring specific SOC support for this driver.
> 2. AND it is possible to have a *sane* fallback by using the IP's generic
> minimum fifo depth. The DWC_i2c manual specifies IC_TX_BUFFER_DEPTH and
> IC_RX_BUFFER_DEPTH as 2..1024, so using depth of 2 as a fallback would be
> functional on any integration, just slower.
Yes, exactly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-11-12 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 20:35 [PATCH v5 0/2] i2c: Add Synopsys Advanced I2C (DWC_i2c) support for TI TDA54 Aniket Limaye
2026-11-10 20:35 ` [PATCH v5 1/2] dt-bindings: i2c: Add Synopsys DWC_i2c controller Aniket Limaye
2026-11-11 0:05 ` Mark Brown
2026-11-11 8:41 ` Krzysztof Kozlowski
2026-11-11 13:24 ` Mark Brown
2026-11-12 18:16 ` Aniket Limaye
2026-11-12 18:40 ` Mark Brown [this message]
2026-11-10 20:35 ` [PATCH v5 2/2] i2c: Add Synopsys Advanced I2C (DWC_i2c) driver 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=77286fa5-5952-4e02-9c4d-040b047cc2b5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a-limaye@ti.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lianfeng.ouyang@starfivetech.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s-jain1@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®