From: Krzysztof Kozlowski <krzk@kernel.org>
To: Doug Anderson <dianders@chromium.org>,
Langyan Ye <yelangyan@huaqin.corp-partner.google.com>
Cc: neil.armstrong@linaro.org, quic_jesszhan@quicinc.com,
airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: display: panel: Add compatible for CSOT PNA957QT1-1
Date: Mon, 27 Jan 2025 18:45:30 +0100 [thread overview]
Message-ID: <c6f3a3cd-e4a3-4a76-931d-784e35282578@kernel.org> (raw)
In-Reply-To: <CAD=FV=XcVnkYSzanqinLX65gRc5434WGbvauavBZPpabfT-2Yw@mail.gmail.com>
On 27/01/2025 18:33, Doug Anderson wrote:
>> Point us to your DTS so we can validate that you really tested it.
>
> Krzysztof: not sure what you're asking for here. I assume Langyan is
> posting support for this panel for hardware they are trying to bring
> up, and the device tree may not be officially posted anywhere yet.
> This is not really a requirement, is it? Given that Langyan is just
If that's the case, it's fine, but sometimes people just wait
unnecessarily with posting DTS.
> adding a compatible to an existing binding, it seems like we can be
> fairly certain that the binding is fine without needing an extra dts
> example, right?
Yes
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-27 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 1:46 [PATCH v1 0/2] support for csot-pna957qt1-1 MIPI-DSI panel Langyan Ye
2025-01-27 1:46 ` [PATCH v1 1/2] dt-bindings: display: panel: Add compatible for CSOT PNA957QT1-1 Langyan Ye
2025-01-27 8:43 ` Krzysztof Kozlowski
2025-01-27 17:33 ` Doug Anderson
2025-01-27 17:45 ` Krzysztof Kozlowski [this message]
2025-01-27 1:46 ` [PATCH v1 2/2] drm/panel: panel-himax-hx83102: support for csot-pna957qt1-1 MIPI-DSI panel Langyan Ye
2025-01-27 17:33 ` Doug Anderson
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=c6f3a3cd-e4a3-4a76-931d-784e35282578@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=yelangyan@huaqin.corp-partner.google.com \
/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