From: <Dharma.B@microchip.com>
To: <krzysztof.kozlowski@linaro.org>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: display: atmel,lcdc: convert to dtschema
Date: Mon, 4 Mar 2024 09:28:57 +0000 [thread overview]
Message-ID: <3d4e4b18-5318-4f1c-ab05-b925a0dfd317@microchip.com> (raw)
In-Reply-To: <ce1c5ba1-4f6a-4d20-8a12-fbae9003657a@linaro.org>
On 04/03/24 1:06 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 04/03/2024 06:36, Dharma Balasubiramani wrote:
>> Convert the atmel,lcdc bindings to DT schema.
>> Changes during conversion: add missing clocks and clock-names properties.
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
>> ---
>> This patch converts the existing lcdc display text binding to JSON schema.
>> The binding is split into two namely
>> lcdc.yaml
>> - Holds the frame buffer properties
>> lcdc-display.yaml
>> - Holds the display panel properties which is a phandle to the display
>> property in lcdc fb node.
>>
>> These bindings are tested against the existing at91 dts files using
>> dtbs_check.
>> ---
>> Changes in v2:
>> - Run checkpatch and remove whitespace errors.
>> - Add the standard interrupt flags.
>> - Split the binding into two, namely lcdc.yaml and lcdc-display.yaml.
>> - Link to v1: https://lore.kernel.org/r/20240223-lcdc-fb-v1-1-4c64cb6277df@microchip.com
>> ---
>> .../bindings/display/atmel,lcdc-display.yaml | 98 ++++++++++++++++++++++
>> .../devicetree/bindings/display/atmel,lcdc.txt | 87 -------------------
>> .../devicetree/bindings/display/atmel,lcdc.yaml | 70 ++++++++++++++++
>> 3 files changed, 168 insertions(+), 87 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/display/atmel,lcdc-display.yaml b/Documentation/devicetree/bindings/display/atmel,lcdc-display.yaml
>> new file mode 100644
>> index 000000000000..ea4fd34b9e2c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/display/atmel,lcdc-display.yaml
>> @@ -0,0 +1,98 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/display/atmel,lcdc-display.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Microchip's LCDC Display
>> +
>> +maintainers:
>> + - Nicolas Ferre <nicolas.ferre@microchip.com>
>> + - Dharma Balasubiramani <dharma.b@microchip.com>
>> +
>> +description:
>> + The LCD Controller (LCDC) consists of logic for transferring LCD image data
>> + from an external display buffer to a TFT LCD panel. The LCDC has one display
>> + input buffer per layer that fetches pixels through the single bus host
>> + interface and a look-up table to allow palletized display configurations. The
>> + LCDC is programmable on a per layer basis, and supports different LCD
>> + resolutions, window sizes, image formats and pixel depths.
>> +
>> +# We need a select here since this schema is applicable only for nodes with the
>> +# following properties
>> +
>> +select:
>> + anyOf:
>> + - required: [ 'atmel,dmacon' ]
>> + - required: [ 'atmel,lcdcon2' ]
>> + - required: [ 'atmel,guard-time' ]
>> + - required: [ bits-per-pixel ]
>
> Why quotes in other places?
I got the following warnings when I tried to compile without adding the
quotes for atmel,*
"[warning] too few spaces after comma (commas)"
and when I add quotes for "bits-per-pixel" it complained the following
"[error] string value is redundantly quoted with any quotes
(quoted-strings)"
So I added quotes for properties with comma in them.
> bits-per-pixel is generic property, so you
> are now selecting other bindings. Read carefully what Rob wrote.
My bad, I should have inquired before arriving at any conclusion.
Thanks for letting me know.
Shall I send v3 by removing "- required: [ bits-per-pixel ]" in select?
>
>
> Best regards,
> Krzysztof
>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2024-03-04 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 5:36 [PATCH v2] dt-bindings: display: atmel,lcdc: convert to dtschema Dharma Balasubiramani
2024-03-04 6:36 ` Rob Herring
2024-03-04 7:36 ` Krzysztof Kozlowski
2024-03-04 9:28 ` Dharma.B [this message]
2024-03-04 9:43 ` Krzysztof Kozlowski
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=3d4e4b18-5318-4f1c-ab05-b925a0dfd317@microchip.com \
--to=dharma.b@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
/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