LKML Archive on
help / color / mirror / Atom feed
From: Mark Brown <>
Subject: Re: [UPDATED v4] WM97xx touchscreen drivers
Date: Wed, 6 Feb 2008 13:57:30 +0000	[thread overview]
Message-ID: <20080206135730.GA11117@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <>

On Tue, Feb 05, 2008 at 06:20:15PM -0500, wrote:

> > The expectation of this driver is that the battery monitor driver will
> > register as the "wm97xx-battery" device and use the wm97xx_read_aux_adc()
> > function exported by the wm97xx-core driver to access the ADC.  Is your
> > driver using this interface?

> Yes, but this makes the wm97xx-battery device depend on configuring in the
> touchscreen.

Indeed.  Could you expand on why this is a problem?

> The problem we're having is that when we updated wm97xx-core.c from
> version 0.62 to 0.65 the ADC values returned by wm97xx_read_aux_adc() to
> the battery driver changed.  We did modify both versions to make the

Version 0.62 predates our git history so I don't have the old version to
hand.  I can't spot anything obvious in the information I do have except
perhaps something introduced when the drivers were split to start
pulling out the codec parts.

> struct wm97xx * global so the battery monitor could pass it to
> wm97xx_read_aux_adc() (is there a better way?).

Well, other than using wm97xx-battery to find it not really.  To be
honest I don't really see what this buys you over using the battery
device since what you suggest means you need to wait until it is
registered anyway.

> > The intention is that these drivers should be able to coexist with the
> > existing ASoC drivers as-is.  We do have existing users doing this - the

> They don't just coexist with soc, they depend on it.  If you configure out
> the AC97 driver under soc the touchscreen and battery drivers won't work
> (but they'll build).

What sorts of problems are you seeing?  I've done a very large
proportion of my touchscreen work with ASoC completely disabled and
haven't noticed any issues.  In this case I was using the non-ASoC
PXA AC97 driver (CONFIG_SND_AC97_CODEC, sound/arm/pxa2xx-ac97.c).
Within ASoC it should be possible to use the generic AC97 codec driver
but I can't say I've ever tested that.

>                       We used the same architecture as tosa and retained
> the OH guys for the app framework (and platform assistance - thanks RP :).

OK, that's good - sounds like you're doing something fairly standard.

> The first release is publicly available; the release I'm working on was
> aimed for the 2.6.24 merge window but some key stuff (ARM clock/power
> management, USB gadget) changed causing me to re-engineer.  I'm still
> troubleshooting some 2.6.18-->24 port issues here (pxa27x_ac97 errors on
> resume - we use deep sleep, not sleep on the pxa270), but can publicize a
> source tarball and send you the link.

Yes, that'd be really helpful.  I don't have the hardware so any non
working stuff isn't going to affect me too much :) .

  reply	other threads:[~2008-02-06 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 19:00 linux01
2008-02-04 21:31 ` Mark Brown
2008-02-05 23:20   ` linux01
2008-02-06 13:57     ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-26 15:18 Mark Brown
2008-01-29 22:03 ` Dmitry Baryshkov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080206135730.GA11117@rakim.wolfsonmicro.main \ \ \ \ \
    --subject='Re: [UPDATED v4] WM97xx touchscreen drivers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).