linux-kernel - Re: [linux][PATCH v5 0/3] Convert Microchip's HLCDC Text based DT bindings to JSON schema

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <478cab42-5f30-4fbe-b42d-02d16b81ca11@microchip.com>
Date: Thu, 1 Feb 2024 03:38:37 +0000
From: <Dharma.B@...rochip.com>
To: <sam@...nborg.org>, <bbrezillon@...nel.org>,
	<maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
	<tzimmermann@...e.de>, <airlied@...il.com>, <daniel@...ll.ch>,
	<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
	<conor+dt@...nel.org>, <Nicolas.Ferre@...rochip.com>,
	<alexandre.belloni@...tlin.com>, <claudiu.beznea@...on.dev>,
	<dri-devel@...ts.freedesktop.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
	<lee@...nel.org>, <thierry.reding@...il.com>,
	<u.kleine-koenig@...gutronix.de>, <linux-pwm@...r.kernel.org>
CC: <Hari.PrasathGE@...rochip.com>, <Manikandan.M@...rochip.com>
Subject: Re: [linux][PATCH v5 0/3] Convert Microchip's HLCDC Text based DT
 bindings to JSON schema

Hi Rob,

On 31/01/24 9:05 am, Dharma B - I70843 wrote:
> Converted the text bindings to YAML and validated them individually using following commands
> 
> $ make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/
> $ make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/
> 
> changelogs are available in respective patches.
> 
> As Sam suggested I'm sending the PWM binding as it is in this patch series, clean up patch
> will be sent as separate patch.
> 

I would want to know if I can have the examples in display and pwm 
bindings separately or if I have to delete them from both and have a 
single, comprehensive example in mfd binding. I'm a little puzzled about 
this.

> Dharma Balasubiramani (3):
>    dt-bindings: display: convert Atmel's HLCDC to DT schema
>    dt-bindings: atmel,hlcdc: convert pwm bindings to json-schema
>    dt-bindings: mfd: atmel,hlcdc: Convert to DT schema format
> 
>   .../atmel/atmel,hlcdc-display-controller.yaml | 85 ++++++++++++++++
>   .../bindings/display/atmel/hlcdc-dc.txt       | 75 --------------
>   .../devicetree/bindings/mfd/atmel,hlcdc.yaml  | 99 +++++++++++++++++++
>   .../devicetree/bindings/mfd/atmel-hlcdc.txt   | 56 -----------
>   .../bindings/pwm/atmel,hlcdc-pwm.yaml         | 44 +++++++++
>   .../bindings/pwm/atmel-hlcdc-pwm.txt          | 29 ------
>   6 files changed, 228 insertions(+), 160 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/display/atmel/atmel,hlcdc-display-controller.yaml
>   delete mode 100644 Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt
>   create mode 100644 Documentation/devicetree/bindings/mfd/atmel,hlcdc.yaml
>   delete mode 100644 Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt
>   create mode 100644 Documentation/devicetree/bindings/pwm/atmel,hlcdc-pwm.yaml
>   delete mode 100644 Documentation/devicetree/bindings/pwm/atmel-hlcdc-pwm.txt
> 

-- 
With Best Regards,
Dharma B.