From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonas Jelonek <jelonek.jonas@gmail.com>, linux-i2c@vger.kernel.org
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
Markus Stockhausen <markus.stockhausen@gmx.de>
Subject: Re: [PATCH 3/3] dt-bindings: i2c: realtek,rtl9301-i2c: extend for RTL9310 support
Date: Wed, 2 Jul 2025 08:11:30 +0200 [thread overview]
Message-ID: <8d671dcc-bcc2-4b1d-9063-f7d69d52d29d@kernel.org> (raw)
In-Reply-To: <123042be-63dc-46bf-b781-6da022a8f4c5@gmail.com>
On 01/07/2025 16:31, Jonas Jelonek wrote:
>
>
> On 01.07.2025 15:17, Krzysztof Kozlowski wrote:
>> You have some very odd wrapping of emails.
>
> Sorry for that, I'm not used to this workflow and obviously haven't configured
> my editor properly. I'm working on that.
>
>> Anyway, you keep mentioning in multiple places rtl9311-9313, so that's
>> confusing. If you mention them, I would expect compatibles. They cannot
>> use rtl9310 compatible alone.
>>
>> I don't mind skipping them, but then just don't mention any sort of
>> treatment for other devices. You add this and only this hardware, if you
>> do not want to follow the make-binding-complete principle (see writing
>> bindings).
>>
>
> I think I got. I'll adjust this in v2.
>>>>> + scl-num:
>>>> No, you do not get own instance IDs.
>>> Is that meant for the wording/naming of the property and/or its
>>> description or for the general idea of this property?
>> You do not get such property. We don't accept it, it's generic rule.
>> Nowhere in the kernel... unless this is a standard, generic property
>> (there is no vendor prefix), but I could not find it. If it is standard
>> property, where is it defined in dtschema or common bindings?
>>
>> I don't get the need for this property and description does not help, so
>> just drop it.
>
> Ok, I missed that this is seen as a generic rule then. Sorry for that.
>
> For the purpose:
> RTL9310 changed the register layout compared to RTL9300. Activating
> the SCL line is done by setting bit 12 for master 1 and bit 13 for master 2
> in a global register which is located before the master-specific registers.
> Thus, the driver needs to know which master (1 or 2) it is currently doing
> something for. That is what this property is intended to be used, naming
> to-be-discussed.
There is no global register space here and no syscon, so I don't
understand how can you access it, especially when they are located
BEFORE your address space.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-02 6:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 9:17 [PATCH 0/3] i2c: rework and extend RTL9300 I2C driver Jonas Jelonek
2025-07-01 9:17 ` [PATCH 1/3] i2c: rework RTL9300 I2C controller driver Jonas Jelonek
2025-07-02 0:36 ` Chris Packham
2025-07-01 9:17 ` [PATCH 2/3] i2c: add RTL9310 support to " Jonas Jelonek
2025-07-01 20:14 ` AW: " markus.stockhausen
2025-07-01 9:17 ` [PATCH 3/3] dt-bindings: i2c: realtek,rtl9301-i2c: extend for RTL9310 support Jonas Jelonek
2025-07-01 11:33 ` Krzysztof Kozlowski
2025-07-01 12:34 ` Jonas Jelonek
2025-07-01 13:17 ` Krzysztof Kozlowski
2025-07-01 14:31 ` Jonas Jelonek
2025-07-02 6:11 ` Krzysztof Kozlowski [this message]
2025-07-02 7:34 ` Jonas Jelonek
2025-07-02 7:49 ` Krzysztof Kozlowski
2025-07-02 9:24 ` Jonas Jelonek
2025-07-01 11:35 ` Krzysztof Kozlowski
2025-07-01 12:34 ` Jonas Jelonek
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=8d671dcc-bcc2-4b1d-9063-f7d69d52d29d@kernel.org \
--to=krzk@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=jelonek.jonas@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.