linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Wu <michael.wu@kneron.us>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jan Dabros <jsd@semihalf.com>,
	linux-i2c@vger.kernel.org
Cc: Andi Shyti <andi.shyti@kernel.org>,
	Morgan Chang <morgan.chang@kneron.us>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: i2c: snps,designware-i2c: add bus-loading and clk-freq-optimized
Date: Wed, 25 Sep 2024 13:32:39 +0200	[thread overview]
Message-ID: <1e570a30-af84-4ec3-9e3d-3f358b29c0ff@kernel.org> (raw)
In-Reply-To: <20240925080432.186408-3-michael.wu@kneron.us>

On 25/09/2024 10:04, Michael Wu wrote:
> Since there are no registers controlling the hardware parameters
> IC_CAP_LOADING and IC_CLK_FREQ_OPTIMIZATION, their values can only be
> noted in the device tree.
> 
> "bus-loading" is used to declare the value of IC_CAP_LOADING, and
> "clk-freq-optimized" is used to declare IC_CLK_FREQ_OPTIMIZATION = 1.
> 
> Signed-off-by: Michael Wu <michael.wu@kneron.us>

<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>

> ---
>  .../bindings/i2c/snps,designware-i2c.yaml     | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml b/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
> index 60035a787e5c..f954f5014a00 100644
> --- a/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/snps,designware-i2c.yaml
> @@ -87,6 +87,16 @@ properties:
>        This value is used to compute the tHIGH period.
>      default: 300
>  
> +  bus-loading:
> +    description: |
> +      This property should be 100 or 400 for high speed mode.
> +      This value is used to compute the tHIGH period and the tLOW period.

How? This wasn't ever tested obviously... Missing units in property name
(or ref but units are preferred).

> +    default: 100
> +
> +  clk_freq_optimized:

No underscores.

> +    description: |
> +      Thie property is used to declare whether the internal latency is reduced.

Your descriptions don't tell me much. Drop redundant parts "This
property" and instead describe the hardware aspect of this property.


> +
>    dmas:
>      items:
>        - description: TX DMA Channel
> @@ -146,4 +156,13 @@ examples:
>        interrupts = <8>;
>        clocks = <&ahb_clk>;
>      };
> +  - |
> +    i2c@ce500000 {

No, no need.



Best regards,
Krzysztof


      reply	other threads:[~2024-09-25 11:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  8:04 [PATCH 0/2] Compute HS HCNT and LCNT based on HW parameters Michael Wu
2024-09-25  8:04 ` [PATCH 1/2] i2c: designware: determine HS tHIGH and tLOW based on HW paramters Michael Wu
2024-09-25  9:16   ` Andy Shevchenko
2024-09-25  9:21     ` Andy Shevchenko
2024-09-26  8:45       ` Michael Wu
2024-09-26 12:18         ` Andy Shevchenko
2024-09-26 13:50           ` Krzysztof Kozlowski
2024-09-26 14:09             ` Andy Shevchenko
2024-09-25 10:58   ` Jarkko Nikula
2024-09-25 11:02     ` Andy Shevchenko
2024-09-26  9:11     ` Michael Wu
2024-09-25 11:33   ` Krzysztof Kozlowski
2024-09-27 13:41   ` kernel test robot
2024-09-25  8:04 ` [PATCH 2/2] dt-bindings: i2c: snps,designware-i2c: add bus-loading and clk-freq-optimized Michael Wu
2024-09-25 11:32   ` Krzysztof Kozlowski [this message]

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=1e570a30-af84-4ec3-9e3d-3f358b29c0ff@kernel.org \
    --to=krzk@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.wu@kneron.us \
    --cc=mika.westerberg@linux.intel.com \
    --cc=morgan.chang@kneron.us \
    /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;
as well as URLs for NNTP newsgroup(s).