public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yicong Yang <yangyicong@huawei.com>
To: Weilong Chen <chenweilong@huawei.com>, <yangyicong@hisilicon.com>,
	<wsa@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<xuwei5@huawei.com>
Subject: Re: [PATCH next v2 2/2] dt-bindings: i2c: add entry for hisilicon,hisi-i2c
Date: Wed, 31 Aug 2022 17:53:51 +0800	[thread overview]
Message-ID: <ffa076ea-2675-05ab-00bb-30b77ef13cba@huawei.com> (raw)
In-Reply-To: <20220825092412.307052-2-chenweilong@huawei.com>

[+cc xuwei for device tree expertise]

On 2022/8/25 17:24, Weilong Chen wrote:
> Add the new compatible for hisi common i2c.
> 

s/hisi/HiSilicon

> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
> ---
>  .../bindings/i2c/hisilicon,hisi-i2c.yaml      | 50 +++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.yaml
> 
> diff --git a/Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.yaml b/Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.yaml
> new file mode 100644
> index 000000000000..ea967abfe144
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.yaml
> @@ -0,0 +1,50 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/i2c/hisilicon,hisi-i2c.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Hisilicon common IIC controller Device Tree Bindings
> +

It's ok to have "HiSilicon common IIC controller"

> +maintainers:
> +  - yangyicong@huawei.com
> +
> +allOf:
> +  - $ref: /schemas/i2c/i2c-controller.yaml#
> +
> +properties:
> +  compatible:
> +    const: hisilicon,hisi-i2c
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  clk_rate:
> +    maxItems: 1
> +
> +  clock-frequency:
> +    default: 100000
> +

I think it misses some properties here?

- i2c-sda-hold-time-ns
- sda_fall_ns
- scl_rise_ns
...

Do we need to mention them here?

Thanks.

> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - clk_rate
> +  - clock-frequency
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    i2c1: i2c@5038B0000{
> +      compatible = "hisilicon,hisi-i2c";
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +      reg = <0x5 0x038B0000 0 0x10000>;
> +      interrupts = <0x0 120 0x4>;
> +      clk_rate = <0x0 0xEE6B280>;
> +      clock-frequency = <400000>;
> +    };
> 

  reply	other threads:[~2022-08-31  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  9:24 [PATCH next v2 1/2] i2c: i2c-hisi: Add support for initializing control module via DT Weilong Chen
2022-08-25  9:24 ` [PATCH next v2 2/2] dt-bindings: i2c: add entry for hisilicon,hisi-i2c Weilong Chen
2022-08-31  9:53   ` Yicong Yang [this message]
2022-09-02  1:00     ` chenweilong
2022-09-07 21:32     ` Wolfram Sang
2022-08-31  9:44 ` [PATCH next v2 1/2] i2c: i2c-hisi: Add support for initializing control module via DT Yicong Yang

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=ffa076ea-2675-05ab-00bb-30b77ef13cba@huawei.com \
    --to=yangyicong@huawei.com \
    --cc=chenweilong@huawei.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@kernel.org \
    --cc=xuwei5@huawei.com \
    --cc=yangyicong@hisilicon.com \
    /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