mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andy Shevchenko <andy@kernel.org>,
	linux-fbdev@vger.kernel.org,
	Michael Hennerich <michael.hennerich@analog.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Helge Deller <deller@gmx.de>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Phillip Potter <phil@philpotter.co.uk>,
	Carlis <zhangxuezhi1@yulong.com>,
	Lee Jones <lee.jones@linaro.org>,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH v1 1/4] fbtft: Unorphan the driver
Date: Mon, 31 Jan 2022 11:28:23 +0100	[thread overview]
Message-ID: <e7fbef3c-2f87-15f9-b24d-34ffaa5a2853@suse.de> (raw)
In-Reply-To: <840ec74d-60c6-9480-709c-8cd597c6f5b0@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2364 bytes --]

Hi

Am 31.01.22 um 11:18 schrieb Javier Martinez Canillas:
> Hello Thomas,
> 
> On 1/31/22 10:18, Thomas Zimmermann wrote:
> 
> [snip]
> 
>>> There are some hacks in the driver though. For example it exposes an XRGB8888
>>> format even thought the OLED display is monochromatic and has 1 bit per pixel.
>>>
>>> The driver then goes and converts the XRGB8888 pixels first to grayscale and
>>> then to reverse mono. I took that idea from the repaper driver but that gives
>>> us the multiple copies that Geert was complaining about.
>>
>> This requires to update the console code for 1-bit BW output. The fbcon
>> side already supports this AFAIK. DRM's fbdev needs a few more branches
>> and something like a DRM_FORMAT_C1 fourcc. The XRGB8888 is really a
>> userspace requirement that is imposed by modern desktops. If DRM's
>> console has been updated, you could leave it out entirely.
>>
>> I could imagine that some simple userspace, such as Weston, comes with
>> support for palette formats and BW. Or there could be an entirely
>> separate program that puts graphics onto these displays.
>>
> 
> Yes, I understand the rationale of why the repaper driver is doing that way
> but was just pointing out because Geert mentioned that is not efficient.

It's a fair point, I think. People are concerned about resource 
consumption on low-end devices.

>   
> Maybe in the meantime we can add a drm_fb_gray8_to_mono_reversed() helper to
> drivers/gpu/drm/drm_format_helper.c since there is more than one driver that
> does the same ?

Sure.

> 
> It's not a big issue for this device really since the I2C bus is slow anyways
> and the multiple copies are not a bottleneck AFAICT.
> 
> I believe is worth to propose this driver as is and then try to optimize later.

Absolutely. If you post a cleaned-up version of the patch, I'd take a look.

> 
> Another thing that's missing is a DRM_MODE_CONNECTOR_I2C, because I used for
> now a DRM_MODE_CONNECTOR_Unknown.

That might have implications on userspace. Maybe ask around. (Not that 
we actually run userspace on the device).

Best regards
Thomas

> 
> Best regards,

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-01-31 10:28 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 20:21 [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 1/4] fbtft: Unorphan the driver Andy Shevchenko
2022-01-26  8:31   ` Greg Kroah-Hartman
2022-01-26 10:31     ` Daniel Vetter
2022-01-26 11:17       ` Helge Deller
2022-01-26 11:26         ` Greg Kroah-Hartman
2022-01-26 13:12           ` Andy Shevchenko
2022-01-26 13:46             ` Javier Martinez Canillas
2022-01-26 14:08               ` Andy Shevchenko
2022-01-26 14:10                 ` Andy Shevchenko
2022-01-26 14:15                   ` Javier Martinez Canillas
2022-01-31  8:29                     ` Javier Martinez Canillas
2022-01-31  9:18                       ` Thomas Zimmermann
2022-01-31 10:18                         ` Javier Martinez Canillas
2022-01-31 10:28                           ` Thomas Zimmermann [this message]
2022-02-01 17:00                             ` Geert Uytterhoeven
2022-02-01 17:06                               ` Daniel Vetter
2022-02-01 19:00                               ` Thomas Zimmermann
2022-01-31 11:36                       ` Andy Shevchenko
2022-01-31 12:08                         ` Javier Martinez Canillas
2022-01-31 13:23                           ` Andy Shevchenko
2022-01-31 13:24                             ` Andy Shevchenko
2022-01-31 13:55                             ` Javier Martinez Canillas
2022-01-31 14:06                               ` Andy Shevchenko
2022-01-26 17:34                 ` Jani Nikula
2022-01-26 11:27         ` Daniel Vetter
2022-01-26 13:14           ` Andy Shevchenko
2022-01-26 11:31         ` Thomas Zimmermann
2022-01-26 13:13           ` Andy Shevchenko
2022-01-26 13:07         ` Andy Shevchenko
2022-01-26 13:06       ` Andy Shevchenko
2022-01-26 13:22         ` Daniel Stone
2022-01-25 20:21 ` [PATCH v1 2/4] fbtft: Move driver out from staging Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 3/4] fbtft: Kill outdated documentation Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 4/4] fbtft: Replace 'depends on FB_TFT' by 'if FB_TFT ... endif' Andy Shevchenko
2022-01-25 20:40   ` Randy Dunlap
2022-01-26  8:54   ` Joe Perches
2022-01-26 13:02     ` Andy Shevchenko
2022-01-26  8:52 ` [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Thomas Zimmermann
2022-01-26 10:02   ` Andy Shevchenko
2022-01-26 10:04     ` Andy Shevchenko
2022-01-26 10:28       ` Dan Carpenter
2022-01-26 12:37         ` Javier Martinez Canillas
2022-01-26 12:56           ` Greg Kroah-Hartman
2022-01-26 13:18             ` Andy Shevchenko
2022-01-26 13:44               ` Javier Martinez Canillas
2022-01-26 13:19             ` Javier Martinez Canillas
2022-01-26 13:36               ` Andy Shevchenko
2022-01-26 13:17           ` Andy Shevchenko
2022-01-26 10:43     ` Daniel Vetter
2022-01-26 10:47     ` Greg Kroah-Hartman
2022-01-26 10:52       ` Daniel Vetter
2022-01-26 11:15         ` Greg Kroah-Hartman
2022-01-26 13:26           ` Andy Shevchenko
2022-01-26 13:24         ` Andy Shevchenko
2022-01-26 10:59     ` Helge Deller
2022-01-26 11:18       ` Javier Martinez Canillas
2022-01-26 11:24         ` Daniel Vetter
2022-01-26 11:38           ` Helge Deller
2022-01-26 11:45             ` Sven Schnelle
2022-01-26 13:30             ` Andy Shevchenko
2022-01-27  9:18               ` Maxime Ripard
2022-01-26 11:31         ` Helge Deller
2022-01-26 11:38           ` Greg Kroah-Hartman
2022-01-26 11:51             ` Helge Deller
2022-01-26 12:15               ` Greg Kroah-Hartman
2022-01-26 11:51           ` Thomas Zimmermann
2022-01-26 13:27         ` Andy Shevchenko
2022-01-26 13:47           ` Javier Martinez Canillas
2022-01-26 14:11             ` Andy Shevchenko
2022-01-26 14:18               ` Javier Martinez Canillas
2022-01-26 14:24                 ` Greg Kroah-Hartman
2022-01-26 14:45                   ` Dan Carpenter
2022-01-26 22:31                     ` Daniel Vetter
2022-01-27  6:29                       ` Dan Carpenter
2022-01-27 10:32                         ` Dmitry Vyukov
2022-01-27 11:11                           ` Daniel Vetter
2022-01-27 16:34                             ` Dmitry Vyukov
2022-01-26 22:37                   ` Daniel Vetter
2022-01-26 11:41       ` Thomas Zimmermann
2022-01-26 13:32         ` Andy Shevchenko
2022-01-26 15:02           ` Thomas Zimmermann
2022-01-26 15:33             ` Andy Shevchenko
2022-01-26 15:54             ` Helge Deller
2022-01-26 13:15 ` Noralf Trønnes
2022-01-26 13:21   ` Andy Shevchenko

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=e7fbef3c-2f87-15f9-b24d-34ffaa5a2853@suse.de \
    --to=tzimmermann@suse.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hkallweit1@gmail.com \
    --cc=javierm@redhat.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=michael.hennerich@analog.com \
    --cc=phil@philpotter.co.uk \
    --cc=zhangxuezhi1@yulong.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

all inboxes | Powered by JetHome®