From: chenweilong <chenweilong@huawei.com>
To: Yicong Yang <yangyicong@huawei.com>, <yangyicong@hisilicon.com>,
<xuwei5@huawei.com>, <wsa@kernel.org>, <robh+dt@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH next v4 2/2] dt-bindings: i2c: add entry for hisilicon,hisi-i2c
Date: Tue, 13 Sep 2022 17:08:41 +0800 [thread overview]
Message-ID: <c644d852-6d33-9de0-c99b-9cdffa081b99@huawei.com> (raw)
In-Reply-To: <58bd3483-3830-bb64-d7d6-5c0f1126de73@huawei.com>
On 2022/9/13 15:59, Yicong Yang wrote:
> On 2022/9/9 15:48, Weilong Chen wrote:
>> Add the new compatible for HiSilicon common i2c.
>>
>> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
>> ---
>> .../bindings/i2c/hisilicon,hisi-i2c.yaml | 67 +++++++++++++++++++
>> 1 file changed, 67 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..f1cb6a4c70d1
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.yaml
>> @@ -0,0 +1,67 @@
>> +# 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
>> +
>> +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:
>> + default: 0xEE6B280
>> +
>> + clock-frequency:
>> + default: 400000
>> +
>> + i2c-sda-falling-time-ns:
>> + default: 343
>> +
>> + i2c-scl-falling-time-ns:
>> + default: 203
>> +
>> + i2c-sda-hold-time-ns:
>> + default: 0x33E
>> +
>> + i2c-scl-rising-time-ns:
>> + default: 365
>> +
>> + i2c-digital-filter-width-ns:
>> + default: 0
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + i2c1: i2c@5038B0000{
>> + compatible = "hisilicon,hisi-i2c";
>> + reg = <0x38B0000 0x10000>;
>> + interrupts = <0x0 120 0x4>;
>> + i2c-sda-falling-time-ns = <56>;
>> + i2c-scl-falling-time-ns = <56>;
>> + i2c-sda-hold-time-ns = <56>;
>> + i2c-scl-rising-time-ns = <56>;
> The values used here are different from above. Are they used on different
> products?
Yes, it's a specific config for new product.
>> + i2c-digital-filter;
> Should we discard the empty properties or is it necessary to have it?
>
> Others looks good to me, but the device tree experts may have some comments.
>
> This binding file should also be listed in the MAINTAINERS file.
>
> Thanks.
No, i2c-digital-filter is needed to fix the error:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/hisilicon,hisi-i2c.example.dtb: i2c@5038B0000: 'i2c-digital-filter' is a dependency of 'i2c-digital-filter-width-ns'
And, I'll update the MAINTAINERS file.
Thanks.
>> + i2c-digital-filter-width-ns = <0x0>;
>> + clk_rate = <0x0 0xEE6B280>;
>> + clock-frequency = <400000>;
>> + };
>>
> .
next prev parent reply other threads:[~2022-09-13 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 7:48 [PATCH next v4 1/2] i2c: hisi: Add initial device tree support Weilong Chen
2022-09-09 7:48 ` [PATCH next v4 2/2] dt-bindings: i2c: add entry for hisilicon,hisi-i2c Weilong Chen
2022-09-13 7:59 ` Yicong Yang
2022-09-13 9:08 ` chenweilong [this message]
2022-09-13 9:40 ` Yicong Yang
2022-09-13 12:22 ` Rob Herring
2022-09-14 4:13 ` chenweilong
2022-09-26 9:30 ` chenweilong
2022-09-13 7:48 ` [PATCH next v4 1/2] i2c: hisi: Add initial device tree support Yicong Yang
2022-09-13 9:01 ` chenweilong
2022-09-13 9:37 ` 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=c644d852-6d33-9de0-c99b-9cdffa081b99@huawei.com \
--to=chenweilong@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wsa@kernel.org \
--cc=xuwei5@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.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