From: Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
To: noralf@tronnes.org, Rob Herring <robh+dt@kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
Subject: [PATCH v2 0/2] Support for tft displays based on ilitek,ili9486
Date: Sun, 26 Jan 2020 23:09:00 +0530 [thread overview]
Message-ID: <cover.1580059987.git.kamlesh.gurudasani@gmail.com> (raw)
The goal of this series is to get the displays based on ilitek,ili9486
working.
Ozzmaker, Piscreen and waveshare,rpi-lcd-35 are such displays.
v2 changes:
* Changing file from txt to yaml format
* removed ilitek,ili9486 from compatible string
* assignment of dbi_command before registration
* made dc and reset gpio compulsory
* typos and unwanted comments removed
* changed the name of function which were display specific
* arranged the Makefile entries in alphabetical order
Kamlesh Gurudasani (2):
dt-bindings: add binding for tft displays based on ilitek,ili9486
drm/tinydrm: add support for tft displays based on ilitek,ili9486
.../bindings/display/ilitek,ili9486.yaml | 79 ++++++
MAINTAINERS | 7 +
drivers/gpu/drm/tiny/Kconfig | 14 +
drivers/gpu/drm/tiny/Makefile | 1 +
drivers/gpu/drm/tiny/ili9486.c | 283 +++++++++++++++++++++
5 files changed, 384 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/ilitek,ili9486.yaml
create mode 100644 drivers/gpu/drm/tiny/ili9486.c
--
2.7.4
next reply other threads:[~2020-01-26 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 17:39 Kamlesh Gurudasani [this message]
2020-01-26 17:42 ` [PATCH v2 1/2] dt-bindings: add binding for tft displays based on ilitek,ili9486 Kamlesh Gurudasani
2020-01-27 14:27 ` Rob Herring
2020-01-26 17:42 ` [PATCH v2 2/2] drm/tinydrm: add support " Kamlesh Gurudasani
2020-01-27 13:04 ` Noralf Trønnes
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=cover.1580059987.git.kamlesh.gurudasani@gmail.com \
--to=kamlesh.gurudasani@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=noralf@tronnes.org \
--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).