From: Rob Herring <robh@kernel.org>
To: Khalil Blaiech <kblaiech@nvidia.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
wsa+renesas@sang-engineering.com,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH i2c-next v1 6/6] dt-bindings: i2c: Convert DT file to YAML schema
Date: Thu, 29 Oct 2020 10:33:06 -0500 [thread overview]
Message-ID: <20201029153306.GA1905314@bogus> (raw)
In-Reply-To: <77461da87050051e0d2e7decdc9b088ff8738e19.1603925078.git.kblaiech@nvidia.com>
On Wed, Oct 28, 2020 at 06:55:54PM -0400, Khalil Blaiech wrote:
> Write the devicetree binding text file in schema file, JSON
> compatible subset of YAML.
> Besides, add an entry within MAINTAINERS file.
The subject should contain something about Mellanox BlueField.
>
> Fixes: d9becc53b3ade81e ("dt-bindings: i2c: I2C binding for Mellanox BlueField SoC")
Fixes is not appropriate for this.
> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
> Signed-off-by: Khalil Blaiech <kblaiech@nvidia.com>
> ---
> .../bindings/i2c/mellanox,i2c-mlxbf.txt | 42 ----------
> .../bindings/i2c/mellanox,i2c-mlxbf.yaml | 78 +++++++++++++++++++
> MAINTAINERS | 1 +
> 3 files changed, 79 insertions(+), 42 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml
>
> diff --git a/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt b/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
> deleted file mode 100644
> index 566ea861aa00..000000000000
> --- a/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
> +++ /dev/null
> @@ -1,42 +0,0 @@
> -Device tree configuration for the Mellanox I2C SMBus on BlueField SoCs
> -
> -Required Properties:
> -
> -- compatible : should be "mellanox,i2c-mlxbf1" or "mellanox,i2c-mlxbf2".
> -
> -- reg : address offset and length of the device registers. The
> - registers consist of the following set of resources:
> - 1) Smbus block registers.
> - 2) Cause master registers.
> - 3) Cause slave registers.
> - 4) Cause coalesce registers (if compatible isn't set
> - to "mellanox,i2c-mlxbf1").
> -
> -- interrupts : interrupt number.
> -
> -Optional Properties:
> -
> -- clock-frequency : bus frequency used to configure timing registers;
> - allowed values are 100000, 400000 and 1000000;
> - those are expressed in Hz. Default is 100000.
> -
> -Example:
> -
> -i2c@2804000 {
> - compatible = "mellanox,i2c-mlxbf1";
> - reg = <0x02804000 0x800>,
> - <0x02801200 0x020>,
> - <0x02801260 0x020>;
> - interrupts = <57>;
> - clock-frequency = <100000>;
> -};
> -
> -i2c@2808800 {
> - compatible = "mellanox,i2c-mlxbf2";
> - reg = <0x02808800 0x600>,
> - <0x02808e00 0x020>,
> - <0x02808e20 0x020>,
> - <0x02808e40 0x010>;
> - interrupts = <57>;
> - clock-frequency = <400000>;
> -};
> diff --git a/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml b/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml
> new file mode 100644
> index 000000000000..b9f6b07c503f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: GPL-2.0
If you have rights, please dual license adding BSD-2-Clause.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/mellanox,i2c-mlxbf.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Mellanox I2C SMBus on BlueField SoCs
> +
> +maintainers:
> + - Khalil Blaiech <kblaiech@nvidia.com>
allOf:
- $ref: i2c-controller.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - mellanox,i2c-mlxbf1
> + - mellanox,i2c-mlxbf2
> +
> + reg:
> + minItems: 3
> + maxItems: 4
> + items:
> + - description: Smbus block registers
> + - description: Cause master registers
> + - description: Cause slave registers
> + - description: Cause coalesce registers
> +
> + interrupts:
> + maxItems: 1
> +
> + clock-frequency:
> + enum: [ 100000, 400000, 1000000 ]
> +
Drop the blank line.
> + description:
> + bus frequency used to configure timing registers;
> + The frequency is expressed in Hz. Default is 100000.
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +unevaluatedProperties: false
> +
> +if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - mellanox,i2c-mlxbf1
> +
> +then:
> + properties:
> + reg:
> + maxItems: 3
> +
> +examples:
> + - |
> + i2c@2804000 {
> + compatible = "mellanox,i2c-mlxbf1";
> + reg = <0x02804000 0x800>,
> + <0x02801200 0x020>,
> + <0x02801260 0x020>;
> + interrupts = <57>;
> + clock-frequency = <100000>;
> + };
> +
> + - |
> + i2c@2808800 {
> + compatible = "mellanox,i2c-mlxbf2";
> + reg = <0x02808800 0x600>,
> + <0x02808e00 0x020>,
> + <0x02808e20 0x020>,
> + <0x02808e40 0x010>;
> + interrupts = <57>;
> + clock-frequency = <400000>;
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9128200af1d0..8dba7ace4a40 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11075,6 +11075,7 @@ MELLANOX BLUEFIELD I2C DRIVER
> M: Khalil Blaiech <kblaiech@nvidia.com>
> L: linux-i2c@vger.kernel.org
> S: Supported
> +F: Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml
> F: drivers/i2c/busses/i2c-mlxbf.c
>
> MELLANOX ETHERNET DRIVER (mlx4_en)
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-10-29 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 22:54 [PATCH i2c-next v1 0/6] i2c: Incremental fixes for Mellanox BlueField I2C Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 1/6] i2c: mlxbf: Add CONFIG_ACPI to guard ACPI function call Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 2/6] i2c: mlxbf: Fix resrticted cast warning of sparse Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 3/6] i2c: mlxbf: Remove unecessary wrapper functions Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 4/6] i2c: mlxbf: Update reference clock frequency Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 5/6] i2c: mlxbf: Update author and maintainer email info Khalil Blaiech
2020-10-28 22:55 ` [PATCH i2c-next v1 6/6] dt-bindings: i2c: Convert DT file to YAML schema Khalil Blaiech
2020-10-29 15:33 ` Rob Herring [this message]
2020-11-03 14:08 ` Khalil Blaiech
2020-10-29 15:33 ` Rob Herring
2020-11-03 14:06 ` Khalil Blaiech
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=20201029153306.GA1905314@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kblaiech@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-i2c@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.