From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Misc: ARM_CHAR_LCD: Permit the use of a driver on any ARM machine
Date: Sun, 18 Nov 2012 12:02:37 +0000 [thread overview]
Message-ID: <20121118120237.GU3290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1353239366.88869804@f19.mail.ru>
On Sun, Nov 18, 2012 at 03:49:26PM +0400, Alexander Shiyan wrote:
> > > arm-charlcd driver can be used on any ARM machine, so dependency of
> > > PLAT_VERSATILE is removed.
> >
> > This needs a better explanation. We know that it's used on ARMs
> > reference boards. Which other platforms will be making use of this
> > driver? Do these other boards implement the same interface, including
> > the presence of the interrupt?
> >
> > I'd need to re-read the specs, but I think that the interface this
> > driver uses is provided by ARMs FPGA rather than the LCD module itself,
> > and re-use of this driver would need that IP to be implemented elsewhere.
> Additionally: But, you are right. This should be reviewed more accuracy for a
> support for other machines, so please drop this patch.
What would be nice to see is a driver library for these LCD modules which
can then be hooked into whatever interface a platform presents, and come
up with some kind of solution to that where the platform interface can be
represented in DT form.
prev parent reply other threads:[~2012-11-18 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 10:56 [PATCH v2] Misc: ARM_CHAR_LCD: Permit the use of a driver on any ARM machine Alexander Shiyan
2012-11-18 11:10 ` Russell King - ARM Linux
2012-11-18 11:36 ` Re[2]: " Alexander Shiyan
2012-11-18 11:49 ` Alexander Shiyan
2012-11-18 12:02 ` 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=20121118120237.GU3290@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.