public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Rustam Adilov <adilov@disroot.org>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
	Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/8] dt-bindings: i2c: realtek,rtl9301-i2c: extend for clocks and RTL9607C support
Date: Thu, 26 Mar 2026 18:13:21 +0000	[thread overview]
Message-ID: <20260326-sixtyfold-ooze-912e198a3057@spud> (raw)
In-Reply-To: <20260326152656.14030-6-adilov@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

On Thu, Mar 26, 2026 at 08:26:53PM +0500, Rustam Adilov wrote:
> Add the "realtek,rtl9607-i2c" compatible for i2c controller on the
> RTL9607C SoC series.
> 
> Add a clocks property to the properties to describe the i2c reference
> clock and make it available for all the compatibles. This i2c reference
> clock is assumed to be coming from switchcore region via Lexra bus as
> the other SoC peripherals.
> 
> According to the info available about the existing devices, they also
> have the i2c master controller clocks.
> 
> RTL9607C requires the "realtek,scl" and "clocks" to be specified
> and so handle it under separate if check for "realtek,rtl9607-i2c".
> 
> Signed-off-by: Rustam Adilov <adilov@disroot.org>

Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-03-26 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 15:26 [PATCH v5 0/8] i2c: rtl9300: support for RTL9607C I2C controller Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 1/8] i2c: rtl9300: split data_reg into read and write reg Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 2/8] i2c: rtl9300: introduce max length property to driver data Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 3/8] i2c: rtl9300: introduce F_BUSY to the reg_fields struct Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 4/8] i2c: rtl9300: introduce a property for 8 bit width reg address Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 5/8] dt-bindings: i2c: realtek,rtl9301-i2c: extend for clocks and RTL9607C support Rustam Adilov
2026-03-26 18:13   ` Conor Dooley [this message]
2026-03-26 15:26 ` [PATCH v5 6/8] i2c: rtl9300: introduce clk struct for upcoming rtl9607 support Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 7/8] i2c: rtl9300: intoduce new function properties to driver data Rustam Adilov
2026-03-26 15:26 ` [PATCH v5 8/8] i2c: rtl9300: add RTL9607C i2c controller support Rustam Adilov
2026-03-31 22:38 ` [PATCH v5 0/8] i2c: rtl9300: support for RTL9607C I2C controller Andi Shyti
2026-04-01 14:09   ` Rustam Adilov
2026-04-01 21:41     ` Andi Shyti

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=20260326-sixtyfold-ooze-912e198a3057@spud \
    --to=conor@kernel.org \
    --cc=adilov@disroot.org \
    --cc=andi.shyti@kernel.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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