linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: driver for the character LCD found in ARM refdesigns
Date: Fri, 16 Jul 2010 10:25:31 +0100	[thread overview]
Message-ID: <20100716092531.GC16995@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201007161119.55769.arnd@arndb.de>

On Fri, Jul 16, 2010 at 11:19:55AM +0200, Arnd Bergmann wrote:
> On Thursday 15 July 2010, Linus Walleij wrote:
> > > Or maybe drivers/platform/arm/ (to avoid Linus' complaint about
> > > drivers under arch/ ?)
> > 
> > Creating that for a single driver seems weird, I could just as well
> > create drivers/lcd for all LCDs in that case. But there is another
> > LCD-like driver for a USB-connected LCD under drivers/misc
> > IIRC, maybe I can make a patch for that as well and let the misc
> > maintainer decide if he wants it.
> 
> Most drivers are in directories based on the software interface, but
> as you explained, the driver does not interface with anything so far.
> 
> Other display drivers are under drivers/video. If it makes sense
> to use the display as the console, you could put it in
> drivers/video/console/. Another option would be to make it
> a tty and move it to driver/char.

It's a 2 line by 8 character LCD.  I don't think it makes sense for it
to be a console or even a tty driver.

      reply	other threads:[~2010-07-16  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 15:21 [PATCH 1/3] ARM: driver for the character LCD found in ARM refdesigns Linus Walleij
2010-07-07  8:47 ` Colin Tuckley
2010-07-07 12:32   ` Linus Walleij
2010-07-15 10:22 ` Russell King - ARM Linux
2010-07-15 11:49   ` Linus Walleij
2010-07-15 11:53     ` Russell King - ARM Linux
2010-07-15 16:32       ` H Hartley Sweeten
2010-07-16  9:19     ` Arnd Bergmann
2010-07-16  9:25       ` Russell King - ARM Linux [this message]

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=20100716092531.GC16995@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).