On Thu, Apr 24, 2014 at 02:30:36PM +0100, Mark Brown wrote: > On Wed, Apr 23, 2014 at 10:25:46PM +0200, Carlo Caione wrote: > > > I'm having a really hard time with this problem, so any hint is welcome > > :) The small modification I'm using on top of the patches in this series > > is here: http://bpaste.net/show/228330/ > > > Unfortunately as I said I got this when booting: > > http://bpaste.net/show/nUhUTzELT32v9HNPathL/ > > Huh, actually the arizona drivers do show this (it was being masked in > my logs by another unrelated bug). I guess the Wolfson guys aren't > working with upstream much (though Charles did write the orignal code > here...). I run upstream fairly regularly here (although mostly on Arndale rather than Speyside). On closer inspection of my kernel log don't seem to have anything related to it, which is odd. > The issue is the MFD core, it shouldn't be using managed allocations > here - the error reported by the assert is entirely correct. If the > CODEC driver is bound and unbound it'll not be possible to reload it > as things stand. > > Your driver is correct but the implementation needs to be fixed - > possibly with an API change on free since at the minute the cells to be > freed don't get passed back into the MFD core when deallocating. This does indeed look broken, I will have a look and think about it. Unfortunately I am travelling most of next week, so if I don't manage to get something out over the weekend there may be a slight delay on me getting a fix out. Thanks, Charles -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
