From: Nam Cao <namcao@linutronix.de>
To: Daniel Matyas <matyasdaniel006@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: Daniel Matyas <matyasdaniel006@gmail.com>,
linux-staging@lists.linux.dev, Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alex Lanzano <lanzano.alex@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFC] staging: fbtft: Moving fb_ili9341 (and others) to DRM
Date: Thu, 05 Nov 2026 22:47:06 +0100 [thread overview]
Message-ID: <874idv2bol.fsf@yellow.woof> (raw)
In-Reply-To: <20261105201154.37294-2-matyasdaniel006@gmail.com>
Daniel Matyas <matyasdaniel006@gmail.com> writes:
> Questions:
> a) Is removing fb_ili9341 acceptable, pointing users of other ILI9341
> modules to panel-mipi-dbi? The KD233 node would then have no driver.
> b) Or should KD233 panel support go into a DRM driver first? I don't have
> its init sequence or physical size, or the board...
> c) Is removal of all of fbtft already planned?
> d) Several other fbtft drivers have drm counterparts. Should I inspect those
> to see if removal is needed?
IIRC the main reason fbtft needs to stay is because it supports parallel
interface which is missing in the DRM drivers.
Nam
next prev parent reply other threads:[~2026-11-05 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 20:11 [RFC] staging: fbtft: Moving fb_ili9341 (and others) to DRM Daniel Matyas
2026-11-05 21:47 ` Nam Cao [this message]
2026-11-06 17:10 ` Daniel Matyas
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=874idv2bol.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=airlied@gmail.com \
--cc=alex@ghiti.fr \
--cc=andy@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matyasdaniel006@gmail.com \
--cc=mripard@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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