From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Dominik Kierner <dkierner@dh-electronics.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"maxime@cerno.tech" <maxime@cerno.tech>,
"noralf@tronnes.org" <noralf@tronnes.org>,
"sam@ravnborg.org" <sam@ravnborg.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v6 3/6] drm: Add driver for Solomon SSD130x OLED displays
Date: Wed, 1 Jun 2022 19:58:18 +0300 [thread overview]
Message-ID: <Ypeaqgc9r7TOiSbn@smile.fi.intel.com> (raw)
In-Reply-To: <536d4700-6f28-176d-7883-5793f5cd7c8e@redhat.com>
On Wed, May 25, 2022 at 09:46:24PM +0200, Javier Martinez Canillas wrote:
> On 3/10/22 14:11, Dominik Kierner wrote:
...
> > # DRM Mode Configuration via Device Tree
> >
> > In the old fbdev driver, the display modes are hard-coded, which means
> > for every new display configuration, a new patch needs to be mainlined,
> > which slows down official Kernel support and
> > puts burden on the maintainers.
> > Additionally, with the DRM-subsystem supporting height and length
> > information, for scaling, this opens up a lot of new combinations.
> > The SSD1306 for example, is available in multiple resolutions like
> > 128x64 and 96x16 and comes in different sizes per resolution as well.
> > Just to name a few:
> > * 128x64 0.96" (22x11mm)
> > * 128x64 1.3" (30x15mm)
> > * 96x16 0.69" (18x3mm)
> >> Instead of hard-coding, I would suggest something along the lines of
> > of_get_drm_display_mode().
> > The displays won't need to support multiple modes at the same time,
> > let alone support for switching between them,
> > so the one-time invocation of this expensive function might be worth it.
> > maybe a new and simpler function that could be named:
> > of_get_drm_display_mode_simple()
>
> This makes sense to me as well.
What about non-OF platforms? Please, do not spread OF-only interfaces,
and use fwnode instead.
> > Providing a mode could later prove useful for a conversion to
> > drm_panel, if that is feasible.
> >
> > But for a function like this, I have to chicken out.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-01 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 13:11 [PATCH v6 3/6] drm: Add driver for Solomon SSD130x OLED displays Dominik Kierner
2022-05-25 19:46 ` Javier Martinez Canillas
2022-06-01 16:58 ` andriy.shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-14 14:05 Dominik Kierner
2022-06-13 11:39 Dominik Kierner
2022-06-13 15:35 ` andriy.shevchenko
2022-06-13 17:41 ` Javier Martinez Canillas
2022-06-13 18:17 ` Javier Martinez Canillas
2022-02-14 13:37 [PATCH v6 0/6] " Javier Martinez Canillas
2022-02-14 13:37 ` [PATCH v6 3/6] " Javier Martinez Canillas
2022-02-16 9:16 ` Maxime Ripard
2022-03-08 16:30 ` Geert Uytterhoeven
2022-03-09 12:14 ` Javier Martinez Canillas
2022-03-09 12:56 ` Geert Uytterhoeven
2022-03-09 13:43 ` Javier Martinez Canillas
2022-03-09 20:04 ` Geert Uytterhoeven
2022-03-09 20:13 ` Javier Martinez Canillas
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=Ypeaqgc9r7TOiSbn@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dkierner@dh-electronics.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.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