From: David Lechner <david@lechnology.com>
To: "Noralf Trønnes" <noralf@tronnes.org>, dri-devel@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, emil.l.velikov@gmail.com,
josef@lusticky.cz, thierry.reding@gmail.com,
laurent.pinchart@ideasonboard.com, sam@ravnborg.org
Subject: Re: [PATCH 3/4] drm/tiny/mi0283qt: Move driver to panel-ilitek-ili9341
Date: Thu, 1 Aug 2019 14:13:57 -0500 [thread overview]
Message-ID: <8ea8d09a-e057-d089-02de-d3ac48c16334@lechnology.com> (raw)
In-Reply-To: <20190801135249.28803-4-noralf@tronnes.org>
On 8/1/19 8:52 AM, Noralf Trønnes wrote:
> The MI0283QT panels use a ILI9341 controller so it makes sense to merge
> it with the other ili9341 code.
>
> The DRM driver name is ABI, so that is retained.
>
> Cc: David Lechner <david@lechnology.com>
> Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
> ---
...
> @@ -216,6 +339,10 @@ static int ili9341_probe(struct spi_device *spi)
> return PTR_ERR(dc);
> }
>
> + ili->regulator = devm_regulator_get(dev, "power");
> + if (IS_ERR(ili->regulator))
> + return PTR_ERR(ili->regulator);
> +
> ili->backlight = devm_of_find_backlight(dev);
> if (IS_ERR(ili->backlight))
> return PTR_ERR(ili->backlight);
> @@ -230,7 +357,12 @@ static int ili9341_probe(struct spi_device *spi)
> ili->panel.dev = dev;
> ili->panel.funcs = ili->conf->funcs;
>
Should probably add a comment here that this is for backwards
compatibility of the driver name so that no one is tempted to
to add more driver structs when adding new panels.
> - return drm_mipi_dbi_panel_register(&ili->panel, &ili->dbidev, &ili9341_drm_driver,
> + if (ili->conf == &mi0283qt_data)
> + driver = &mi0283qt_drm_driver;
> + else
> + driver = &ili9341_drm_driver;
> +
> + return drm_mipi_dbi_panel_register(&ili->panel, &ili->dbidev, driver,
> ili->conf->mode, rotation);
> }
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-01 19:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 13:52 [PATCH 0/4] drm/mipi-dbi: Support panel drivers Noralf Trønnes
2019-08-01 13:52 ` [PATCH 1/4] drm/mipi-dbi: Support command mode " Noralf Trønnes
2019-08-11 14:16 ` Sam Ravnborg
2019-08-12 12:05 ` Noralf Trønnes
2019-08-12 18:49 ` Sam Ravnborg
2019-08-13 16:24 ` Noralf Trønnes
2019-08-01 13:52 ` [PATCH 2/4] drm/tiny/ili9341: Move driver to drm/panel Noralf Trønnes
2019-08-01 19:43 ` David Lechner
2019-08-02 14:19 ` Noralf Trønnes
2019-08-11 15:24 ` Sam Ravnborg
2019-08-12 12:11 ` Noralf Trønnes
2019-08-01 13:52 ` [PATCH 3/4] drm/tiny/mi0283qt: Move driver to panel-ilitek-ili9341 Noralf Trønnes
2019-08-01 19:13 ` David Lechner [this message]
2019-08-01 13:52 ` [PATCH 4/4] drm/panel/ili9341: Support DPI panels Noralf Trønnes
2019-08-01 19:10 ` [4/4] " David Lechner
2019-08-02 14:14 ` Noralf Trønnes
2019-08-11 16:41 ` [PATCH 4/4] " Sam Ravnborg
2019-08-12 12:13 ` Noralf Trønnes
2019-08-12 15:35 ` Laurent Pinchart
2019-08-12 18:20 ` Sam Ravnborg
2019-08-11 17:02 ` Sam Ravnborg
2019-08-12 12:18 ` 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=8ea8d09a-e057-d089-02de-d3ac48c16334@lechnology.com \
--to=david@lechnology.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=josef@lusticky.cz \
--cc=laurent.pinchart@ideasonboard.com \
--cc=noralf@tronnes.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.