From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Asmaa Mnebhi <asmaa@nvidia.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
robh@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Khalil Blaiech <kblaiech@nvidia.com>
Subject: Re: [PATCH v5 8/8] i2c: i2c-mlxbf.c: Update binding devicetree
Date: Wed, 21 Sep 2022 08:59:07 +0200 [thread overview]
Message-ID: <b71a576b-170c-d596-a024-884223be44c6@linaro.org> (raw)
In-Reply-To: <20220920174736.9766-9-asmaa@nvidia.com>
On 20/09/2022 19:47, Asmaa Mnebhi wrote:
> In the latest version of the i2c-mlxbf.c driver, the "Smbus block"
> resource was broken down to 3 separate resources "Smbus timer",
> "Smbus master" and "Smbus slave" to accommodate for BlueField-3
> SoC registers' changes.
>
> Reviewed-by: Khalil Blaiech <kblaiech@nvidia.com>
> Signed-off-by: Asmaa Mnebhi <asmaa@nvidia.com>
> ---
> reg:
> minItems: 3
> @@ -25,6 +27,9 @@ properties:
> - description: Cause master registers
> - description: Cause slave registers
> - description: Cause coalesce registers
> + - description: Smbus timer registers
> + - description: Smbus master registers
> + - description: Smbus slave registers
>
> interrupts:
> maxItems: 1
> @@ -35,6 +40,13 @@ properties:
> bus frequency used to configure timing registers;
> The frequency is expressed in Hz. Default is 100000.
>
> + resource_version:
No underscores in names.
> + enum: [ 0, 1 ]
> + description:
> + Version of the device tree. resource_version = 0 when the driver uses
> + Smbus block resource. resource_version = 1 when the driver uses Smbus
> + timer, Smbus master and Smbus slave resources.
No way. That's not a DT property.
> +
> required:
> - compatible
> - reg
> @@ -42,18 +54,6 @@ required:
>
> unevaluatedProperties: false
>
> -if:
> - properties:
> - compatible:
> - contains:
> - enum:
> - - mellanox,i2c-mlxbf1
> -
> -then:
> - properties:
> - reg:
> - maxItems: 3
Why?
> -
> examples:
> - |
> i2c@2804000 {
> @@ -61,8 +61,13 @@ examples:
> reg = <0x02804000 0x800>,
> <0x02801200 0x020>,
> <0x02801260 0x020>;
> + <0x00000001 0x1>;
> + <0x02804000 0x40>,
> + <0x02804200 0x200>,
> + <0x02804400 0x200>,
> interrupts = <57>;
> clock-frequency = <100000>;
> + resource_version = <1>;
> };
>
> - |
> @@ -72,6 +77,25 @@ examples:
> <0x02808e00 0x020>,
> <0x02808e20 0x020>,
> <0x02808e40 0x010>;
> + <0x02808800 0x040>;
> + <0x02808a00 0x200>,
> + <0x02808c00 0x200>,
> interrupts = <57>;
> clock-frequency = <400000>;
> + resource_version = <1>;
> + };
> +
> + - |
> + i2c@2808800 {
> + compatible = "mellanox,i2c-mlxbf3";
> + reg = <0x00000001 0x1>,
> + <0x13404400 0x020>,
> + <0x13404420 0x020>,
> + <0x13404440 0x010>;
> + <0x13404480 0x40>,
> + <0x13404200 0x200>,
> + <0x13404000 0x200>,
No need for the same example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-21 6:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:47 [PATCH v5 0/8] i2c: i2c-mlxbf.c: bug fixes and new feature support Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 1/8] i2c: i2c-mlxbf.c: Fix frequency calculation Asmaa Mnebhi
2022-09-21 19:44 ` Wolfram Sang
2022-09-20 17:47 ` [PATCH v5 2/8] i2c: i2c-mlxbf.c: remove IRQF_ONESHOT Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 3/8] i2c: i2c-mlxbf.c: incorrect base address passed during io write Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 4/8] i2c: i2c-mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 5/8] i2c: i2c-mlxbf.c: support lock mechanism Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 6/8] i2c: i2c-mlxbf: add multi slave functionality Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 7/8] i2c: i2c-mlxbf.c: support BlueField-3 SoC Asmaa Mnebhi
2022-09-20 17:47 ` [PATCH v5 8/8] i2c: i2c-mlxbf.c: Update binding devicetree Asmaa Mnebhi
2022-09-21 6:55 ` Krzysztof Kozlowski
2022-09-21 13:12 ` Asmaa Mnebhi
2022-09-21 13:19 ` Krzysztof Kozlowski
2022-09-21 20:01 ` How to remove DT support from a driver? (was Re: [PATCH v5 8/8] i2c: i2c-mlxbf.c: Update binding devicetree) Wolfram Sang
2022-09-21 20:17 ` Asmaa Mnebhi
2022-09-24 17:31 ` Rob Herring
2022-09-26 13:18 ` Asmaa Mnebhi
2022-09-26 18:57 ` Wolfram Sang
2022-09-21 6:57 ` [PATCH v5 8/8] i2c: i2c-mlxbf.c: Update binding devicetree Krzysztof Kozlowski
2022-09-21 6:59 ` Krzysztof Kozlowski [this message]
2022-09-21 13:24 ` [PATCH v5 0/8] i2c: i2c-mlxbf.c: bug fixes and new feature support Asmaa Mnebhi
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=b71a576b-170c-d596-a024-884223be44c6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=asmaa@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=kblaiech@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®