On Mon, Feb 04, 2008 at 02:00:24PM -0500, linux01@architechnical.net 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? 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 first publicly available example that springs to mind is tosa which also uses the wm9712 with touchscreen and battery, together with the ASoC driver for audio (the ASoC bits of this have been merged since ASoC was merged in 2006, the other bits are out of tree partly due to the fact that they depend on this driver). I'm disappointed to hear that, particularly with the wm9712 since that especially has had a reasonable degree of testing with our drivers over a fairly long time period. The most obvious way forward if we can't resolve these problems with the existing scheme is to pull out the core driver as you say above - this is the approach already taken by the touch drivers to allow battery monitoring while the touchscreen is in use. Is your kernel (or the wm9712-related code at least) publicly available? If not would it be possible for you to share it with me off-list? It might help me understand what's going on here. --
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Gabriel C | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | [GIT]: Networking |
| Thomas Jarosch | Re: TCP connection stalls under 2.6.24.7 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
