On Thu, Sep 22, 2016 at 05:27:42PM +0200, Marek Vasut wrote: > On 09/22/2016 04:37 PM, Maciej S. Szmigiero wrote: > > There are three possible solutions: > > 1) Go back to RB tree cache (revert patch 4) and debug the lockdep warning, > > 2) Keep the flat cache introduced by patch 4 but debug the oops at > > cache init time (while keeping defaults read from hardware), > > 3) Keep both patches and risk the same issues that were previously > > caused by hardcoded register defaults in driver. > > However, Marek says the device works fine for him with the patches. > I believe switching to flat cache is harmless and it should be a better > mode for devices with small mmio address spaces. After some discussion > on IRC, I believe [1] should resolve the RBTREE crash (?). So, can we get a clear decision on this after testing? The discussion here and the discussion on IRC are a bit disjointed and I'd like to make sure we end up with something that definitely works.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
