devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Paulo Pavacic <pavacic.p@gmail.com>
Cc: krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	neil.armstrong@linaro.org, sam@ravnborg.org, airlied@gmail.com,
	robh+dt@kernel.org, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: display: panel: add panel-mipi-dsi-bringup
Date: Wed, 17 May 2023 10:32:36 +0200	[thread overview]
Message-ID: <250e0e95-9f34-5fb7-aa5d-61b227dc9cf1@linaro.org> (raw)
In-Reply-To: <356bfe96-75e6-1c6d-0049-d664e719a266@gmail.com>

On 17/05/2023 10:29, Paulo Pavacic wrote:
> Hello,
> 
> If I understood you correctly you'd prefer it to be named 
> fannal,c3004.yaml?

This is what I wrote:
"Judging by compatible, this should be fannal,c3004.yaml"

>  My logic is that if more panels were to be added that 
> means that each one would have yaml files that would look exactly the 
> same with the same user.

It's not a big deal. Although anyway why would other panels have exactly
the same supplies and all other properties?

BTW, you miss there supply.

Best regards,
Krzysztof


  reply	other threads:[~2023-05-17  8:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 13:09 [PATCH v2] dt-bindings: display: panel: add panel-mipi-dsi-bringup Paulo Pavačić
2023-05-16 15:57 ` Krzysztof Kozlowski
2023-05-16 22:13   ` Paulo Pavacic
2023-05-17  7:03     ` Krzysztof Kozlowski
2023-05-17  8:29       ` Paulo Pavacic
2023-05-17  8:32         ` Krzysztof Kozlowski [this message]
2023-05-17 12:20     ` Jagan Teki
2023-05-17 13:04       ` Paulo
2023-05-17 16:32         ` Jagan Teki
2023-05-18 14:47           ` Paulo Pavacic
2023-05-18 19:25             ` Conor Dooley
2023-05-17 10:25 ` Dave Stevenson

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=250e0e95-9f34-5fb7-aa5d-61b227dc9cf1@linaro.org \
    --to=krzysztof.kozlowski@linaro.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;
as well as URLs for NNTP newsgroup(s).