From: Conor Dooley <conor@kernel.org>
To: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: convert to dt schema
Date: Wed, 19 Jun 2024 18:27:26 +0100 [thread overview]
Message-ID: <20240619-exemplify-tabloid-9d15e5005513@spud> (raw)
In-Reply-To: <20240619154941.144011-2-kanakshilledar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
On Wed, Jun 19, 2024 at 09:19:36PM +0530, Kanak Shilledar wrote:
$subject is missing a prefix for the device in question.
> diff --git a/Documentation/devicetree/bindings/i2c/nxp,lpc1788-i2c.yaml b/Documentation/devicetree/bindings/i2c/nxp,lpc1788-i2c.yaml
> new file mode 100644
> index 000000000000..79d6774dd54f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/nxp,lpc1788-i2c.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/nxp,lpc1788-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP I2C controller for LPC2xxx/178x/18xx/43xx
> +
> +maintainers:
> + - Vladimir Zapolskiy <vz@mleia.com>
> +
> +allOf:
> + - $ref: /schemas/i2c/i2c-controller.yaml#
> +
> +properties:
> + compatible:
> + const: nxp,lpc1788-i2c
> +
> + reg:
> + description: physical address and length of the device registers
Drop all of these descriptions as they're obvious, other than...
> + maxItems: 1
> +
> + interrupts:
> + description: a single interrupt specifier
> + maxItems: 1
> +
> + clocks:
> + description: clock for the device
> + maxItems: 1
> +
> + clock-frequency:
> + description: the desired I2C bus clock frequency in Hz
..maybe this one. Otherwise this looks okay to me.
Thanks,
Conor.
> + default: 100000
> +
> + resets:
> + description: reset for the device
> + maxItems: 1
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
These two come for free with the ref to i2c-controller.yaml :)
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - "#address-cells"
> + - "#size-cells"
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include "dt-bindings/clock/lpc18xx-ccu.h"
> +
> + i2c@400a1000 {
> + compatible = "nxp,lpc1788-i2c";
> + reg = <0x400a1000 0x1000>;
> + interrupts = <18>;
> + clocks = <&ccu1 CLK_APB1_I2C0>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-19 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:49 [PATCH] dt-bindings: i2c: convert to dt schema Kanak Shilledar
2024-06-19 17:27 ` Conor Dooley [this message]
2024-06-19 18:26 ` kernel test robot
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=20240619-exemplify-tabloid-9d15e5005513@spud \
--to=conor@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kanakshilledar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vz@mleia.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;
as well as URLs for NNTP newsgroup(s).