All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 1 Jul 2025 13:33:59 +0200	[thread overview]
Message-ID: <d123375e-48ec-43f1-bc5a-1256c2f377ec@kernel.org> (raw)
In-Reply-To: <20250701091737.3430-4-jelonek.jonas@gmail.com>

On 01/07/2025 11:17, Jonas Jelonek wrote:
> This extends the dt-bindings for the I2C driver for RTL9300 to account

Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95

> for the added support for RTL9310 series.
> 
> A new property is added to explicitly set the SCL num/hardware instance
> of the controller that is used. In contrast to RTL9300 the driver needs
> to know that explicitly for RTL9310 because the SCL selection is now in
> a global register instead of a master-specific register.
> 
> The regex for child-node address is adjusted to account for the fact
> that RTL9310 supports 12 instead of 8 SDA lines.
> 
> A single generic compatible "realtek,rtl9310-i2c" is added. To best
> knowledge, all existing SoCs of RTL9310 series (RTL9311, RTL9312,
> RTL9313) have equal I2C capabilities thus don't need special treatment.


You always need specific front compatible (and fallback if applicable).



> However, in the unlikely case of future differences with specific
> SoCs within this series, more can be added as needed.
> 
> Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
> ---
>  .../bindings/i2c/realtek,rtl9301-i2c.yaml     | 33 ++++++++++++++++---
>  1 file changed, 29 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> index eddfd329c67b..3b32da3de2af 100644
> --- a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> @@ -10,9 +10,11 @@ maintainers:
>    - Chris Packham <chris.packham@alliedtelesis.co.nz>
>  
>  description:
> -  The RTL9300 SoC has two I2C controllers. Each of these has an SCL line (which
> -  if not-used for SCL can be a GPIO). There are 8 common SDA lines that can be
> -  assigned to either I2C controller.
> +  The RTL9300 SoCs have two I2C controllers. Each of these has an SCL line
> +  (which if not-used for SCL can be a GPIO). There are 8 common SDA lines
> +  that can be assigned to either I2C controller.
> +  The RTL9310 SoCs have equal capabilities but support 12 common SDA lines
> +  which can be assigned to either I2C controller.
>  
>  properties:
>    compatible:
> @@ -24,6 +26,7 @@ properties:
>                - realtek,rtl9303-i2c
>            - const: realtek,rtl9301-i2c
>        - const: realtek,rtl9301-i2c
> +      - const: realtek,rtl9310-i2c
>  
>    reg:
>      description: Register offset and size this I2C controller.
> @@ -34,8 +37,18 @@ properties:
>    "#size-cells":
>      const: 0
>  
> +  scl-num:


No, you do not get own instance IDs.

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof

  reply	other threads:[~2025-07-01 11:34 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 [this message]
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
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=d123375e-48ec-43f1-bc5a-1256c2f377ec@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.