linux-kernel - Re: [GIT PULL] move ARM LCD display driver to auxdisplay

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Apr 2016 12:41:29 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Robin van der Gracht <robin@...tonic.nl>
Cc:	"arm@...nel.org" <arm@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Miguel Ojeda Sandonis <maxextreme@...il.com>
Subject: Re: [GIT PULL] move ARM LCD display driver to auxdisplay

On Mon, Apr 25, 2016 at 1:57 PM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
> On Sat, Apr 23, 2016 at 11:43:58AM +0200, Linus Walleij wrote:
>> Hi ARM SoC guys,
>>
>> these two patches move the ARM character LCD driver from
>> misc drivers to the auxdisplay subsystem where it belongs and
>> updates the defconfig for the RealView accordingly.
>>
>> Please pull it into some cleanup branch in the ARM SoC
>> tree.
>>
>> I tried to get some ACK from the auxdisplay maintainer but no
>> reaction.
>
> Auxdisplay is not a new framework, but rather a very old one.
>
> It got introduced in 2.6.21, and only received a couple of drivers
> since.

Small problem for me, but Robin is submitting a brand new
auxdisplay driver:
http://marc.info/?l=linux-kernel&m=146001950512999&w=2
http://marc.info/?l=linux-kernel&m=146001988013230&w=2

> It seems to be quite redundant with fbdev deferred_io, which itself is
> almost deprecated these days.

That is a valid argument for moving cfag12864b* out to
drivers/video/* I guess, but it has nothing to do with this
driver whatsoever.

This driver has nothing to do with fbdev. Nothing at all.
It so not connected to any framebuffer.

This driver gets moved to auxdisplay to match the existing
LCD driver in drivers/auxdisplay/ks0108.c which is a similar
hardware, driving an LCD that likewise has nothing to do
with fbdev.

Yours,
Linus Walleij