From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Dmitry Torokhov <dtor@mail.ru>,
linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
Liam Girdwood <liam.girdwood@wolfsonmicro.com>,
Graeme Gregory <gg@opensource.wolfsonmicro.com>,
Rodolfo Giometti <giometti@enneenne.com>,
Russell King <rmk@arm.linux.org.uk>, Ian Molton <spyro@f2s.com>,
Vince Sanders <vince@kyllikki.org>,
Andrew Zabolotny <zap@homelink.ru>
Subject: Re: [PATCH 5/6] Driver for WM97xx touchscreens in streaming mode on PXA2xx systems
Date: Mon, 14 Jan 2008 16:35:52 +0000 [thread overview]
Message-ID: <20080114163552.GA26436@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <478B7A86.7010207@pengutronix.de>
On Mon, Jan 14, 2008 at 04:06:46PM +0100, Marc Kleine-Budde wrote:
> Mark Brown wrote:
> > On Mon, Jan 14, 2008 at 10:56:06AM +0100, Marc Kleine-Budde wrote:
> > The driver really isn't intended to cope with them. As you say, other
> > boards may have things wired up differently and therefore require
> > different configuration of the wm97xx and other bits of the system. The
> > expectation is that other systems will have their own driver.
> What bits have to setup in a different way? Only the stuff in
> wm97xx_acc_startup() or other things aswell. An irq can be put as utual
The main thing for pxa2xx would be the interrupt enable callback and
possibly also the acc_shutdown() function depending on what the startup
function had to do for the board. If there were platform data then at
least some of the module options (AC97 link slot, for example) ought to
have at least defaults supplied that way too. However...
> into a device's resouce, Setting up bits may be done like other stuff on
> pxa, too. e.g. pxa_set_ohci_info.
It's straightforward for something discovered using the platform bus but
unfortunately these controllers are AC97 devices and are discovered via
the AC97 bus. This makes life harder - I can't see any sensible way of
getting platform data to describe the machine to the driver. Hopefully
I'm missing something here but if not the options are limited.
> With my limited understanding of the pxa-wm97xx.c file, the only board
> dependent stuff is done in wm97xx_acc_startup() so a different "driver"
> for other boards would result in code duplication.
That's a concern I share - you'll likely end up with either that or
ifdefs, neither of which is ideal. Being able to use platform data
would be much nicer for all these drivers, not just pxa2xx-wm97xx.
prev parent reply other threads:[~2008-01-14 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 11:51 [PATCH 1/6] Core driver for WM97xx touchscreens Mark Brown
2008-01-10 11:51 ` [PATCH 2/6] Add chip driver for WM9705 touchscreen Mark Brown
2008-01-10 11:51 ` [PATCH 3/6] Add chip driver for WM9712 touchscreen Mark Brown
2008-01-10 11:51 ` [PATCH 4/6] Add chip driver for WM9713 touchscreen Mark Brown
2008-01-10 11:51 ` [PATCH 5/6] Driver for WM97xx touchscreens in streaming mode on PXA2xx systems Mark Brown
2008-01-10 11:51 ` [PATCH 6/6] Build system and MAINTAINERS entry for WM97xx touchscreen drivers Mark Brown
2008-01-10 15:41 ` Sam Ravnborg
2008-01-10 16:00 ` Mark Brown
2008-01-14 9:56 ` [PATCH 5/6] Driver for WM97xx touchscreens in streaming mode on PXA2xx systems Marc Kleine-Budde
2008-01-14 14:42 ` Mark Brown
2008-01-14 15:06 ` Marc Kleine-Budde
2008-01-14 16:35 ` Mark Brown [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=20080114163552.GA26436@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dtor@mail.ru \
--cc=gg@opensource.wolfsonmicro.com \
--cc=giometti@enneenne.com \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=rmk@arm.linux.org.uk \
--cc=spyro@f2s.com \
--cc=vince@kyllikki.org \
--cc=zap@homelink.ru \
/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).