devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Wolfram Sang <wsa@kernel.org>,
	Michal Simek <michal.simek@amd.com>,
	Shubhrajyoti Datta <Shubhrajyoti.datta@amd.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: i2c: cadence: Document `cdns,fifo-depth` property
Date: Mon, 6 Feb 2023 10:58:36 -0600	[thread overview]
Message-ID: <20230206165836.GA216424-robh@kernel.org> (raw)
In-Reply-To: <20230205230208.58355-2-lars@metafoo.de>

On Sun, Feb 05, 2023 at 03:02:08PM -0800, Lars-Peter Clausen wrote:
> The depth of the FIFO of the Cadence I2C controller IP is a synthesis
> configuration parameter. Different instances of the IP can have different
> values. For correct operation software needs to be aware of the size of the
> FIFO.
> 
> Add the documentation for the devicetree property that describes the FIFO
> depth of the IP core.
> 
> The default value of 16 is for backwards compatibility reasons with
> existing hardware descriptions where this property is not specified and
> software has assumed that the FIFO depth is 16.
> 
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
>  Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml b/Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml
> index 2e95cda7262a..3daa2fa73257 100644
> --- a/Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml
> +++ b/Documentation/devicetree/bindings/i2c/cdns,i2c-r1p10.yaml
> @@ -38,6 +38,12 @@ properties:
>      description: |
>        Input clock name.
>  
> +  cdns,fifo-depth:

We already have:

fifo-size
rx-fifo-size
tx-fifo-size
fifo-depth
tx-fifo-depth
rx-fifo-depth

And we have cdns,fifo-depth too (among other vendor specific ones), but 
pick a non-vendor specific one.


> +    description:
> +      Size of the data FIFO in words.

What's the word size? Use bytes.

> +    $ref: "/schemas/types.yaml#/definitions/uint32"
> +    default: 16
> +
>  required:
>    - compatible
>    - reg
> @@ -57,4 +63,6 @@ examples:
>          clock-frequency = <400000>;
>          #address-cells = <1>;
>          #size-cells = <0>;
> +
> +        cdns,fifo-depth = <8>;
>      };
> -- 
> 2.30.2
> 

  parent reply	other threads:[~2023-02-06 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 23:02 [PATCH 1/2] i2c: cadence: Allow to specify the FIFO depth and maximum transfer length Lars-Peter Clausen
2023-02-05 23:02 ` [PATCH 2/2] dt-bindings: i2c: cadence: Document `cdns,fifo-depth` property Lars-Peter Clausen
2023-02-06  7:32   ` Michal Simek
2023-02-06  7:41   ` Krzysztof Kozlowski
2023-02-06 15:20     ` Lars-Peter Clausen
2023-02-06 16:58   ` Rob Herring [this message]
2023-02-06  8:02 ` [PATCH 1/2] i2c: cadence: Allow to specify the FIFO depth and maximum transfer length Michal Simek
2023-02-16 14:12   ` Lars-Peter Clausen
2023-02-17  9:34     ` Michal Simek

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=20230206165836.GA216424-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Shubhrajyoti.datta@amd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=wsa@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;
as well as URLs for NNTP newsgroup(s).