From: Bartholomäus Steinmayr <BSteinmayr@thorlabs.com>
To: "mwalle@kernel.org" <mwalle@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: [PATCH 0/2] ili9806e: Add Densitron DMT050WVNMCMI-1A to ILI9806E DSI driver
Date: Wed, 11 Mar 2026 15:54:50 +0000 [thread overview]
Message-ID: <SN7PR08MB8467538698BF3A10C453C2FFA847A@SN7PR08MB8467.namprd08.prod.outlook.com> (raw)
Hi,
this patch series adds support for the Densitron DMT050WVNMCMI-1A panel
to the ILI9806E DSI driver. The patch mainly contains initialization
code for the panel.
However, the display also has a peculiarity which required some more
changes to the driver. The display contains a Goodix GT911 touchpanel
controller. The GT911 and ILI9806E share a single reset line. The i2c
address of the GT911 chip is set by manipulating an IO line during
reset. This is already handled by the existing GT911 driver, but it
means that the reset line MUST be controlled by the Goodix driver
(drivers/input/touchscreen/goodix.c). The ILI9806E should defer its
probing until the Goodix driver has completed its reset. The ILI9806E
should then probe with asserting the reset line.
To achieve this, this patch adds an optional dt node "i2c-frag" to the
ILI9806E driver. If this node exists, the Ilitek driver defers its
probing until the i2c node has been initialized. Furthermore, the
reset-gpios property has been made optional. To keep the Ilitek driver
from asserting the reset line, the reset-gpios property should be left
out for the DMT050 display.
This solution does not seem particularly elegant, but I could not find a
more straight-forward one. This is also my first kernel patch, so I
appreciate your patience.
Thank you.
next reply other threads:[~2026-03-11 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:54 Bartholomäus Steinmayr [this message]
2026-03-12 8:30 ` [PATCH 0/2] ili9806e: Add Densitron DMT050WVNMCMI-1A to ILI9806E DSI driver Michael Walle
2026-03-13 4:42 ` Claude review: " Claude Code Review Bot
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=SN7PR08MB8467538698BF3A10C453C2FFA847A@SN7PR08MB8467.namprd08.prod.outlook.com \
--to=bsteinmayr@thorlabs.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mwalle@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