From: Heiko Stuebner <heiko@sntech.de>
To: thierry.reding@gmail.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, seanpaul@chromium.org,
briannorris@chromium.org, hl@rock-chips.com,
nickey.yang@rock-chips.com, Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH v2 0/3] Kingdisplay-kd097d04-panel
Date: Mon, 2 Jul 2018 12:32:26 +0200 [thread overview]
Message-ID: <20180702103229.3952-1-heiko@sntech.de> (raw)
The Innolux p097pfg is one of two possible panels used in the
gru-scarlet ChromeOS devices.
This v2 updates the driver with changes from the ChromeOS side
and tries to address most of the comments received from Sean Paul.
Nickey Yang (3):
dt-bindings: Add vendor prefix for kingdisplay
dt-bindings: Add KINGDISPLAY KD097D04 panel bindings
drm/panel: add Kingdisplay kd097d04 panel driver
.../display/panel/kingdisplay,kd097d04.txt | 22 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/gpu/drm/panel/Kconfig | 11 +
drivers/gpu/drm/panel/Makefile | 1 +
.../drm/panel/panel-kingdisplay-kd097d04.c | 469 ++++++++++++++++++
5 files changed, 504 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/panel/kingdisplay,kd097d04.txt
create mode 100644 drivers/gpu/drm/panel/panel-kingdisplay-kd097d04.c
--
2.17.0
next reply other threads:[~2018-07-02 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 10:32 Heiko Stuebner [this message]
2018-07-02 10:32 ` [PATCH v2 1/3] dt-bindings: Add vendor prefix for kingdisplay Heiko Stuebner
2018-07-10 11:02 ` Thierry Reding
2018-07-02 10:32 ` [PATCH v2 2/3] dt-bindings: Add KINGDISPLAY KD097D04 panel bindings Heiko Stuebner
2018-07-10 11:05 ` Thierry Reding
2018-07-02 10:32 ` [PATCH v2 3/3] drm/panel: add Kingdisplay kd097d04 panel driver Heiko Stuebner
2018-07-10 11:11 ` Thierry Reding
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=20180702103229.3952-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hl@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nickey.yang@rock-chips.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=thierry.reding@gmail.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
Powered by JetHome