From: Conor Dooley <conor@kernel.org>
To: Paulo Pavacic <pavacic.p@gmail.com>
Cc: neil.armstrong@linaro.org, sam@ravnborg.org, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: panel: add fannal,c3004
Date: Mon, 5 Jun 2023 16:08:02 +0100 [thread overview]
Message-ID: <20230605-untracked-trillion-d30cb9cb77c5@spud> (raw)
In-Reply-To: <CAO9szn0crQzy0L2Y-NZGKEVbpspxZMkO0oPpYr1WMS081ZxKRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On Mon, Jun 05, 2023 at 04:56:13PM +0200, Paulo Pavacic wrote:
> Hello Conor,
>
> pon, 5. lip 2023. u 16:43 Conor Dooley <conor@kernel.org> napisao je:
> Sorry this is my first patch, I still don't understand, why should I
> add `maxItems: 1` to the 'reg:' ?
> Isn't part of the code:
> > required:
> > - compatible
> > - reg
> > - reset-gpios
>
> making `minItems: 1` redundant for reg properties?
I went and had another look, and you get enforcement of this from the
dsi-controller binding if extra reg entries are added.
Sorry for the noise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-05 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 14:24 [PATCH 0/2] drm/panel: add fannal c3004 panel Paulo Pavacic
2023-05-19 14:24 ` [PATCH 1/2] dt-bindings: display: panel: add fannal,c3004 Paulo Pavacic
2023-05-19 16:41 ` Conor Dooley
2023-06-05 14:33 ` Paulo Pavacic
2023-06-05 14:43 ` Conor Dooley
2023-06-05 14:56 ` Paulo Pavacic
2023-06-05 15:08 ` Conor Dooley [this message]
2023-05-20 13:58 ` kernel test robot
2023-05-19 14:24 ` [PATCH 2/2] drm/panel-fannal-c3004: Add fannal c3004 DSI panel Paulo Pavacic
2023-05-22 8:55 ` neil.armstrong
2023-05-23 17:33 ` Linus Walleij
2023-05-22 8:55 ` [PATCH 0/2] drm/panel: add fannal c3004 panel neil.armstrong
2023-05-23 13:15 ` Paulo Pavacic
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=20230605-untracked-trillion-d30cb9cb77c5@spud \
--to=conor@kernel.org \
--cc=airlied@gmail.com \
--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=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=pavacic.p@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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