linux-kernel - Re: [PATCH v1 1/4] fbtft: Unorphan the driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 1 Feb 2022 20:00:34 +0100
From:   Thomas Zimmermann <tzimmermann@...e.de>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Andy Shevchenko <andy@...nel.org>,
        Linux Fbdev development list <linux-fbdev@...r.kernel.org>,
        Lee Jones <lee.jones@...aro.org>,
        Michael Hennerich <michael.hennerich@...log.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Helge Deller <deller@....de>, linux-staging@...ts.linux.dev,
        Javier Martinez Canillas <javierm@...hat.com>,
        DRI Development <dri-devel@...ts.freedesktop.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Carlis <zhangxuezhi1@...ong.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Phillip Potter <phil@...lpotter.co.uk>,
        Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [PATCH v1 1/4] fbtft: Unorphan the driver

Hi

Am 01.02.22 um 18:00 schrieb Geert Uytterhoeven:
> Hi Thomas,
> 
> On Tue, Feb 1, 2022 at 5:16 PM Thomas Zimmermann <tzimmermann@...e.de> wrote:
>> Am 31.01.22 um 11:18 schrieb Javier Martinez Canillas:
>>> 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).
> 
> Looking at the list of connector types (and wondering if we're gonna
> need more when converting existing fbdev drivers to drm drivers),
> there seem to be two different families of connector types, for
>    1. transports between CRTC and display (e.g. VGA, DVID, HDMI),
>    2. transports between CPU and CRTC (e.g. SPI, possibly USB, and
>       the proposed I2C)?

I think I had a similar discussion when we merged the gud driver. gud is 
a driver for a RasPi-based usb display adapter.  My point was that USB 
is just an internal transport bus, like PCI. But that wasn't convincing. 
So now we have USB and other busses as connector types.

My preference would be to use a panel type as Daniel suggested; and 
maybe 'Unknown' for a few special cases.

Best regards
Thomas

> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds

-- 
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

Download attachment "OpenPGP_signature" of type "application/pgp-signature" (841 bytes)