From: Krzysztof Kozlowski <krzk@kernel.org>
To: suijingfeng <suijingfeng@loongson.cn>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] dt-bindings: display: Add Loongson display controller
Date: Wed, 22 Feb 2023 19:30:29 +0100 [thread overview]
Message-ID: <76bc79c9-a892-c43e-1f49-d07b54f52c90@kernel.org> (raw)
In-Reply-To: <20230222165514.684729-2-suijingfeng@loongson.cn>
On 22/02/2023 17:55, suijingfeng wrote:
> This patch add a trival DT usages for loongson display controller found
> in LS2k1000 SoC.
Trivial yet so many things to improve... if you only started from recent
kernel tree (since you Cced wrong address, I doubt you did) and bindings
you would avoid half of these comments.
>
> Signed-off-by: suijingfeng <suijingfeng@loongson.cn>
> ---
> .../loongson/loongson,display-controller.yaml | 58 +++++++++++++++++++
> 1 file changed, 58 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
>
> diff --git a/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml b/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
> new file mode 100644
> index 000000000000..98b78f449a80
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/loongson/loongson,display-controller.yaml
Filename based on compatible, so "loongson,ls2k1000-dc.yaml"
> @@ -0,0 +1,58 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/loongson/loongson,display-controller.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Loongson Display Controller Device Tree Bindings
Drop "Device Tree Bindings"
> +
> +maintainers:
> + - Sui Jingfeng <suijingfeng@loongson.cn>
> +
> +description: |+
Drop |+
> +
No need for blank line. Do you see it anywhere else in the bindings?
> + The display controller is a PCI device, it has two display pipe.
> + For the DC in LS2K1000 each way has a DVO output interface which
> + provide RGB888 signals, vertical & horizontal synchronisations
> + and the pixel clock. Each CRTC is able to support 1920x1080@60Hz,
> + the maximum resolution is 2048x2048 according to the hardware spec.
> +
> +properties:
> + $nodename:
> + pattern: "^display-controller@[0-9a-f],[0-9a-f]$"
Drop nodename.
> +
> + compatible:
> + oneOf:
Drop oneOf
> + - items:
and items...
> + - enum:
> + - loongson,ls2k1000-dc
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + bus {
> +
Drop blank line.
> + #address-cells = <3>;
> + #size-cells = <2>;
> + #interrupt-cells = <2>;
Why do you need interrupt-cells?
> +
> + display-controller@6,0 {
> + compatible = "loongson,ls2k1000-dc";
> + reg = <0x3000 0x0 0x0 0x0 0x0>;> + interrupts = <28 IRQ_TYPE_LEVEL_LOW>;
> + };
> + };
> +
> +...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-22 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 16:55 [PATCH 1/2] Mips: ls2k1000: dts: add the display controller device node suijingfeng
2023-02-22 16:55 ` [PATCH 2/2] dt-bindings: display: Add Loongson display controller suijingfeng
2023-02-22 18:30 ` Krzysztof Kozlowski [this message]
2023-02-23 9:51 ` suijingfeng
2023-02-23 10:09 ` Krzysztof Kozlowski
2023-02-22 18:32 ` [PATCH 1/2] Mips: ls2k1000: dts: add the display controller device node Krzysztof Kozlowski
2023-02-23 3:19 ` Sui jingfeng
2023-02-23 7:58 ` Krzysztof Kozlowski
2023-02-23 8:05 ` Krzysztof Kozlowski
2023-02-23 8:21 ` suijingfeng
2023-02-23 8:38 ` Krzysztof Kozlowski
2023-02-23 8:40 ` suijingfeng
2023-02-23 8:59 ` Krzysztof Kozlowski
2023-02-23 9:17 ` suijingfeng
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=76bc79c9-a892-c43e-1f49-d07b54f52c90@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=suijingfeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--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;
as well as URLs for NNTP newsgroup(s).