From: "Noralf Trønnes" <noralf@tronnes.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Josef Lusticky <josef@lusticky.cz>,
dri-devel <dri-devel@lists.freedesktop.org>,
Thierry Reding <thierry.reding@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC 4/4] drm/panel/ili9341: Support mi0283qt
Date: Tue, 30 Jul 2019 19:04:33 +0200 [thread overview]
Message-ID: <01d421db-ff1e-51ec-ad99-af79a102ec47@tronnes.org> (raw)
In-Reply-To: <CAKMK7uH8S9xZNFNJkmrEjSasb0v6tnL5OMZRC-KyXiNiJj2U9A@mail.gmail.com>
Den 30.07.2019 17.22, skrev Daniel Vetter:
> On Tue, Jul 30, 2019 at 4:30 PM Noralf Trønnes <noralf@tronnes.org> wrote:
>>
>>
>>
>> Den 29.07.2019 21.55, skrev Noralf Trønnes:
>>> Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
>>> ---
>>> drivers/gpu/drm/panel/panel-ilitek-ili9341.c | 179 ++++++++++++++++++-
>>> 1 file changed, 170 insertions(+), 9 deletions(-)
>>>
>>
>> I have realised that this will change the DRM driver name from mi0283qt
>> to drm_mipi_dbi. This means that this panel will loose its MESA kmsro[1]
>> support. I haven't tried it, but this is the first thing that gives this
>> driver any real advantage over its fbdev counterpart in
>> drivers/staging/fbtft, so I don't want to loose that.
>> So even if MIPI DBI panel support is implemented in some form, I will
>> wait with converting mi0283qt until someone has updated the kmsro driver.
>
> Why does it change? You should be able to stuff whatever you feel like
> into the drm driver name, this doesn't have to match either your
> platform/spi/whatever driver name nor the module option.
Strictly it doesn't have to change, I could pass a mi0283qt specific
struct drm_driver to drm_mipi_dbi_panel_register() and keep the DRM
driver name.
Noralf.
> -Daniel
>
>
>> Noralf.
>>
>> [1]
>> https://gitlab.freedesktop.org/mesa/mesa/tree/master/src/gallium/winsys/kmsro/drm
>> https://gitlab.freedesktop.org/mesa/mesa/blob/master/src/gallium/targets/dri/target.c
>
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-30 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 19:55 [RFC 0/4] drm/mipi-dbi: Support panel drivers Noralf Trønnes
2019-07-29 19:55 ` [RFC 1/4] drm/panel: Add Ilitek ILI9341 parallel RGB panel driver Noralf Trønnes
2019-07-29 19:55 ` [RFC 2/4] drm/panel/ili9341: Rebase and some more Noralf Trønnes
2019-07-30 6:45 ` Josef Luštický
2019-07-29 19:55 ` [RFC 3/4] drm/mipi-dbi: Support command mode panel drivers Noralf Trønnes
2019-07-29 19:55 ` [RFC 4/4] drm/panel/ili9341: Support mi0283qt Noralf Trønnes
2019-07-30 8:34 ` Josef Luštický
2019-07-30 14:18 ` Noralf Trønnes
2019-07-30 14:30 ` Noralf Trønnes
2019-07-30 15:22 ` Daniel Vetter
2019-07-30 17:04 ` Noralf Trønnes [this message]
2019-07-30 17:12 ` Emil Velikov
2019-07-30 17:33 ` Noralf Trønnes
2019-07-31 8:23 ` Daniel Vetter
2019-07-31 13:35 ` Emil Velikov
2019-07-30 6:40 ` [RFC 0/4] drm/mipi-dbi: Support panel drivers Josef Luštický
2019-07-30 14:08 ` Noralf Trønnes
2019-07-30 14:27 ` Josef Luštický
2019-07-30 14:51 ` 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=01d421db-ff1e-51ec-ad99-af79a102ec47@tronnes.org \
--to=noralf@tronnes.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=josef@lusticky.cz \
--cc=laurent.pinchart@ideasonboard.com \
--cc=sam@ravnborg.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