From: Michael Zavertkin <misha.zavertkin@mail.ru>
To: Conor Dooley <conor@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rustam Adilov <adilov@disroot.org>
Subject: Re: [PATCH 2/2] dt-bindings: i2c: rtl9300: add pinctrl
Date: Wed, 7 Oct 2026 20:33:46 +0700 [thread overview]
Message-ID: <asZKOn8HIuIaaqKA@gamepc> (raw)
In-Reply-To: <20261007-370cbe94c765a69550a85bbd@squawk>
On Wed, Oct 07, 2026 at 11:12:36AM +0100, Conor Dooley wrote:
> > If so, what would be better - print warning about realtek,scl (only for
> > RTL9607C) and work as earlier, potentially interfering with pinctrl
> > driver - or abort probe with error if there is no pinctrl property?
> > Explicit error or message is better then silent regression, if I
> > understand you correctly.
>
> If there's genuinely only two users, then I suppose you can break it.
> But two known users doesn't meant two users. Otherwise, use pintrl if
> available and use the fallback to the existing property if not. Mark the
> property deprecated and probably emit a warning.
Okay, I'll prepare v2. Support for deprecated property should be removed
somewhere in future, right?
next prev parent reply other threads:[~2026-10-07 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 15:32 [PATCH 0/2] i2c: rtl9300: remove IO_MODE configuration Michael Zavertkin
2026-10-04 15:32 ` [PATCH 1/2] " Michael Zavertkin
2026-10-04 15:32 ` [PATCH 2/2] dt-bindings: i2c: rtl9300: add pinctrl Michael Zavertkin
2026-10-05 10:38 ` Conor Dooley
2026-10-05 13:53 ` Michael Zavertkin
2026-10-07 10:12 ` Conor Dooley
2026-10-07 13:33 ` Michael Zavertkin [this message]
2026-10-07 14:01 ` Conor Dooley
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=asZKOn8HIuIaaqKA@gamepc \
--to=misha.zavertkin@mail.ru \
--cc=adilov@disroot.org \
--cc=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor@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
all inboxes | Powered by JetHome®