From: Andrew Morton <akpm@linux-foundation.org>
To: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
Cc: pavel@ucw.cz, linux-parport@lists.infradead.org,
linux-kernel@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH] parport: Add character LCD driver for da850/omap-l138
Date: Thu, 3 Sep 2009 15:20:42 -0700 [thread overview]
Message-ID: <20090903152042.bec9e4b8.akpm@linux-foundation.org> (raw)
In-Reply-To: <000901ca2bd4$bf245190$3d6cf4b0$@raj@ti.com>
On Wed, 2 Sep 2009 19:23:27 +0530
"Sudhakar Rajashekhara" <sudhakar.raj@ti.com> wrote:
> On Tue, Sep 01, 2009 at 18:53:30, Pavel Machek wrote:
> > Hi!
> >
> > > On TI DA850/OMAP-L138 EVM, HD44780 (24x2) LCD panel is
> > > being used, interfaced through the SoC specific LCD
> > > interface[1].
> > >
> > > Driver from drivers/staging/panel/panel.c works for this
> > > LCD panel but that driver expects the LCD panel to be
> > > interfaced through a parallel port.
> > >
> > > This patch implements a dummy parallel port driver which
> > > interfaces to the panel driver in staging area through the
> > > LCD interface available on SoC.
> >
> > This is a nasty hack, right? Just fixup panel.c to work with your
> > interface, too?
> > Pavel
> >
>
> Agree, that this is a hack. I have submitted a patch which modifies
> panel.c to support this kind of interface.
>
> Currently the problem with panel.c is that, it is tightly coupled
> with parallel port interface. Panel driver needs to be completely
> re-written to de-couple parallel port related stuff. If I have to
> do this, then I need to start from ground zero as I do not have a
> setup on which HD44780 panel has been interfaced using parallel
> port. But I can certainly help here by testing such a modification
> to the panel driver by testing on the hardware what I have.
>
> In the meantime, can I re-submit this patch by moving the dummy
> parallel port driver to reside in staging area? Later it can be
> moved/deleted depending on the modifications to the panel driver.
>
If we're going to pull tricks like that then panel.c will never get
itself moved from outside staging/ :(
Really, I don't think we should be hacking things into drivers/parport/
code to accommodate design shortcomings in a staging/ driver. Once done,
these things have a tendency to never be undone.
prev parent reply other threads:[~2009-09-03 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 21:22 Sudhakar Rajashekhara
2009-09-01 13:23 ` Pavel Machek
[not found] ` <000901ca2bd4$bf245190$3d6cf4b0$@raj@ti.com>
2009-09-03 22:20 ` Andrew Morton [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=20090903152042.bec9e4b8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=pavel@ucw.cz \
--cc=sudhakar.raj@ti.com \
/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
all inboxes | Powered by JetHome®