From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pranav Kharche <pranavkharche7@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] dt-bindings: media: convert hix5hd2-ir to DT schema
Date: Sun, 29 Mar 2026 11:45:16 +0200 [thread overview]
Message-ID: <20260329-authentic-smiling-cat-0be663@quoll> (raw)
In-Reply-To: <20260328084238.201452-2-pranavkharche7@gmail.com>
On Sat, Mar 28, 2026 at 02:12:38PM +0530, Pranav Kharche wrote:
> Convert the legacy plaintext binding for HiSilicon hix5hd2 IR remote
> controller to JSON Schema (DT schema) format in YAML.
>
> This binding documents the infrared remote receiver found in HiSilicon
> SoCs such as hix5hd2 and hi3796cv300. The conversion includes:
>
> - Standardized property definitions with types and constraints
Drop
> - Reference to rc.yaml base schema for remote controller properties
Drop
> - Addition of include directives for interrupt-controller bindings
Drop
> - Proper example with GIC interrupt specifiers
Drop
> - Schema validation support for device tree sources
Drop
>
> The new schema enables:
> - Validation improvement
Drop
>
> tested with: make dt_binding_check DT_SCHEMA_FILES=...
> All schema validation checks pass.
Drop
Please write useful commit msgs, meaning you do not need to state
obvious things. Plenty of examples in git log.
What you MUST say here is documenting the changes you done to the
binding. You removed existing property which is not explained at all,
introduces undocumented ABI and adds new warnings. No, seriously, no.
And if you TESTED this you would see errors, so back to basic
requirements of schema conversion - see my posts on social.kernel.org.
>
> Signed-off-by: Pranav Kharche <pranavkharche7@gmail.com>
> ---
> .../devicetree/bindings/media/hix5hd2-ir.txt | 26 ---------
> .../devicetree/bindings/media/hix5hd2-ir.yaml | 53 +++++++++++++++++++
> 2 files changed, 53 insertions(+), 26 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/media/hix5hd2-ir.txt
> create mode 100644 Documentation/devicetree/bindings/media/hix5hd2-ir.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/hix5hd2-ir.txt b/Documentation/devicetree/bindings/media/hix5hd2-ir.txt
> deleted file mode 100644
> index ca4cf774662e..000000000000
> --- a/Documentation/devicetree/bindings/media/hix5hd2-ir.txt
> +++ /dev/null
> @@ -1,26 +0,0 @@
> -Device-Tree bindings for hix5hd2 ir IP
> -
> -Required properties:
> - - compatible: Should contain "hisilicon,hix5hd2-ir", or:
> - - "hisilicon,hi3796cv300-ir" for Hi3796CV300 IR device.
> - - reg: Base physical address of the controller and length of memory
> - mapped region.
> - - interrupts: interrupt-specifier for the sole interrupt generated by
> - the device. The interrupt specifier format depends on the interrupt
> - controller parent.
> - - clocks: clock phandle and specifier pair.
> -
> -Optional properties:
> - - linux,rc-map-name: see rc.txt file in the same directory.
> - - hisilicon,power-syscon: DEPRECATED. Don't use this in new dts files.
> - Provide correct clocks instead.
> -
> -Example node:
> -
> - ir: ir@f8001000 {
> - compatible = "hisilicon,hix5hd2-ir";
> - reg = <0xf8001000 0x1000>;
> - interrupts = <0 47 4>;
> - clocks = <&clock HIX5HD2_IR_CLOCK>;
> - linux,rc-map-name = "rc-tivo";
> - };
> diff --git a/Documentation/devicetree/bindings/media/hix5hd2-ir.yaml b/Documentation/devicetree/bindings/media/hix5hd2-ir.yaml
> new file mode 100644
> index 000000000000..91cba6ec88c5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/hix5hd2-ir.yaml
Filename must match the compatible, choose one.
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/hix5hd2-ir.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: HiSilicon Hix5hd2 infrared remote controller
> +
> +maintainers:
> + - Pranav Kharche <pranavkharche7@gmail.com>
> +
> +allOf:
> + - $ref: rc.yaml#
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + This binding describes the infrared remote controller found in
So description describes that your binding describes... No, drop.
Explain the hardware and if you do not have any explanation, no need to
state obvious and paste here compatibles.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-03-29 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 8:42 [PATCH 0/1] dt-bindings: media: convert hix5hd2-ir to DT schema Pranav Kharche
2026-03-28 8:42 ` [PATCH 1/1] " Pranav Kharche
2026-03-29 9:45 ` Krzysztof Kozlowski [this message]
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=20260329-authentic-smiling-cat-0be663@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pranavkharche7@gmail.com \
--cc=robh@kernel.org \
/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