From: lvzhaoxiong <lvzhaoxiong@huaqin.corp-partner.google.com>
To: mripard@kernel.org, airlied@gmail.com, daniel@ffwll.ch,
robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, dianders@google.com, hsinyi@google.com
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
lvzhaoxiong <lvzhaoxiong@huaqin.corp-partner.google.com>
Subject: [PATCH v1 0/2] Add kd101ne3 bindings and driver.
Date: Thu, 18 Apr 2024 16:15:46 +0800 [thread overview]
Message-ID: <20240418081548.12160-1-lvzhaoxiong@huaqin.corp-partner.google.com> (raw)
Add bindings and driver for kd101ne3.
lvzhaoxiong (2):
dt-bindings: display: panel: Add KD101NE3-40TI support
drm/panel: kd101ne3: add new panel driver
.../panel/kingdisplay,kd101ne3-40ti.yaml | 63 ++
drivers/gpu/drm/panel/Kconfig | 9 +
drivers/gpu/drm/panel/Makefile | 1 +
.../drm/panel/panel-kingdisplay-kd101ne3.c | 607 ++++++++++++++++++
4 files changed, 680 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/panel/kingdisplay,kd101ne3-40ti.yaml
create mode 100644 drivers/gpu/drm/panel/panel-kingdisplay-kd101ne3.c
--
2.17.1
next reply other threads:[~2024-04-18 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 8:15 lvzhaoxiong [this message]
2024-04-18 8:15 ` [PATCH v1 1/2] dt-bindings: display: panel: Add KD101NE3-40TI support lvzhaoxiong
2024-04-18 22:59 ` Krzysztof Kozlowski
2024-04-18 8:15 ` [PATCH v1 2/2] drm/panel: kd101ne3: add new panel driver lvzhaoxiong
2024-04-18 11:46 ` Dmitry Baryshkov
2024-04-18 13:11 ` Hsin-Yi Wang
2024-04-18 14:11 ` Dmitry Baryshkov
2024-04-23 18:10 ` Hsin-Yi Wang
2024-04-23 20:41 ` Doug Anderson
2024-04-23 21:20 ` Dmitry Baryshkov
2024-04-24 21:04 ` Doug Anderson
2024-04-24 21:18 ` Hsin-Yi Wang
2024-04-24 21:49 ` Dmitry Baryshkov
2024-04-24 22:15 ` Hsin-Yi Wang
2024-04-24 22:50 ` Dmitry Baryshkov
2024-04-24 23:25 ` Doug Anderson
2024-04-24 23:37 ` Dmitry Baryshkov
2024-04-25 0:21 ` Doug Anderson
2024-04-24 22:27 ` 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=20240418081548.12160-1-lvzhaoxiong@huaqin.corp-partner.google.com \
--to=lvzhaoxiong@huaqin.corp-partner.google.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).