From: neil.armstrong@linaro.org
To: Daniel Schultz <d.schultz@phytec.de>, Maxime Ripard <mripard@kernel.org>
Cc: jessica.zhang@oss.qualcomm.com,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, sam@ravnborg.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH 1/2] drm/panel: panel-simple: Add Sharp LQ070Y3LG05
Date: Wed, 26 Nov 2025 09:18:54 +0100 [thread overview]
Message-ID: <2fdd5660-e25e-4c29-95da-1e342feb424d@linaro.org> (raw)
In-Reply-To: <4989e0fa-7251-4f2b-b1b1-0bd534a585b1@phytec.de>
On 11/24/25 14:53, Daniel Schultz wrote:
> On 11/24/25 13:51, Maxime Ripard wrote:
>> On Mon, Nov 24, 2025 at 04:39:37AM -0800, Daniel Schultz wrote:
>>> Add the Sharp LQ070Y3LG05 7" WVGA lanscape LVDS RGB TFT-LCD panel.
>>>
>>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>>> ---
>>> drivers/gpu/drm/panel/panel-simple.c | 28 ++++++++++++++++++++++++++++
>>> 1 file changed, 28 insertions(+)
>> Any reason to use panel-simple over panel-lvds?
>
> I didn't know panel-lvds exist. I just convert these timings to panel-lvds and works fine, too. Thanks!
>
> I don't plan to send my device-tree with the new timings included in the near future. Should or can I already add this panel as compatible to panel-simple.yaml?
Any reason why it won't fit in Documentation/devicetree/bindings/display/panel/panel-lvds.yaml ?
Neil
>
> - Daniel
>
>>
>> Maxime
prev parent reply other threads:[~2025-11-26 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 12:39 [PATCH 1/2] drm/panel: panel-simple: Add Sharp LQ070Y3LG05 Daniel Schultz
2025-11-24 12:39 ` [PATCH 2/2] dt-bindings: display: simple: " Daniel Schultz
2025-11-24 12:45 ` Krzysztof Kozlowski
2025-11-24 12:51 ` [PATCH 1/2] drm/panel: panel-simple: " Maxime Ripard
2025-11-24 13:53 ` Daniel Schultz
2025-11-26 8:18 ` neil.armstrong [this message]
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=2fdd5660-e25e-4c29-95da-1e342feb424d@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=d.schultz@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
--cc=upstream@lists.phytec.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