From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: ucb1x00 patches
Date: Sun, 11 Oct 2009 14:14:58 +0200 [thread overview]
Message-ID: <20091011121458.GA1356@ucw.cz> (raw)
In-Reply-To: <20091007081235.GA6246@n2100.arm.linux.org.uk>
On Wed 2009-10-07 09:12:35, Russell King - ARM Linux wrote:
> On Wed, Oct 07, 2009 at 09:56:42AM +0200, Marek Vasut wrote:
> > Dne St 7. ????jna 2009 09:13:22 Lothar Wa??mann napsal(a):
> > > Hi,
> > >
> > > Thomas Kunze writes:
> > > > Hi,
> > > >
> > > > I posted these patches at linux-arm-kernel as part of the patchset
> > > > "collie and SA1100 patches".
> > > > Could you please comment on them? I'd also like to know you opinion on
> > > > moving ucb1x00-ts.c to
> > > > input/drivers/touchscreen.
> > >
> > > What about the ucb1400_ts.c which is already there?
> > >
> >
> > I'd be for unifying all the ucb drivers into a single one, but Russell was
> > against it iirc.
>
> They're different beasts, and I really don't think they should be unified.
> They have different register layouts, and different access arrangements,
> which need different handling.
>
> The result is that the UCB1200/UCB1300 support gets unnecessarily penalised
> when UCB1400 is integrated - instead of merely taking a spinlock and
> accessing the register, you have to ensure everything you do is in thread
> context, including interrupt handlers.
Is it that bad?
If sharing makes sense on source-code level, that kind of penalty
should be acceptable. If it makes more eyes on the sources, it will
still be a win.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-11 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 16:32 ucb1x00 patches Thomas Kunze
2009-10-07 7:13 ` Lothar Waßmann
2009-10-07 7:56 ` Marek Vasut
2009-10-07 8:12 ` Russell King - ARM Linux
2009-10-11 12:14 ` Pavel Machek [this message]
2009-10-12 13:08 ` Russell King - ARM Linux
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=20091011121458.GA1356@ucw.cz \
--to=pavel@ucw.cz \
--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).