[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1490873226.708.68.camel@linux.intel.com>
Date: Thu, 30 Mar 2017 14:27:06 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Willy TARREAU <wtarreau@...roxy.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Miguel Ojeda Sandonis <miguel.ojeda.sandonis@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v1 1/2] auxdisplay: Move panel.c to drivers/auxdisplay
folder
On Mon, 2017-03-27 at 11:01 +0200, Willy TARREAU wrote:
> On Mon, Mar 27, 2017 at 10:26:07AM +0200, Geert Uytterhoeven wrote:
> > On Mon, Mar 27, 2017 at 10:11 AM, Willy TARREAU <wtarreau@...roxy.co
> > m> wrote:
> > > On Fri, Mar 24, 2017 at 04:19:43PM +0100, Geert Uytterhoeven
> > > wrote:
> > > > On Fri, Mar 24, 2017 at 3:29 PM, Andy Shevchenko
> > > > <andriy.shevchenko@...ux.intel.com> wrote:
> > > > > On Fri, 2017-03-24 at 15:19 +0100, Geert Uytterhoeven wrote:
> > > > > > On Fri, Mar 24, 2017 at 3:06 PM, Andy Shevchenko
> > > > > > <andriy.shevchenko@...ux.intel.com> wrote:
> In fact here the output signals should be seen as a shared bus with
> multiple
> chip select signals. Note that in some designs it's even possible that
> pressing
> multiple buttons will cause crap to be sent to the LCD by short-
> circuiting
> the lines (if no diodes are used) but it might be acceptable for many
> designs,
> especially the DIY field where the principle is "don't do it".
So, summarizing the comments are we okay to proceed or there is a clear
objection?
P.S. Note, that there is at least one driver under drivers/auxdisplay
which supports key buttons.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists