On 12/19/2012 10:45 AM, Mark Brown wrote: > On Tue, Dec 18, 2012 at 11:54:50AM +0200, Felipe Balbi wrote: > >> damn, this is still part of our v3.7-rc kernel. Original commit was done >> with no testing whatsoever and caused a big regression to (at least) >> TI's WiFi driver which depend on SDIO to function. > >> Too bad things break and even when reported nobody gives a rat's *** >> about them :-s > > I guess it's going to be even more of an issue going forward given the > recent events but FWIW it was always very unusual to see any review of > any TWL patches, the PMIC appeared to have been rather abandoned so the > only way of getting any testing was to put stuff in -next and hope. As for the twl-regulator I still have plan to do a major cleanup there. It is just sad that it received the DT bindings for the current code. The DT support addition would have been the perfect place to sanitize it. Now it is just going to be a huge pain in the back. As for the 32k clock: I don't know the state of the common clock framework for OMAPs. Is it already up in 3.7? Or going for 3.8? 3.9? 3.10?... We need CCF to resolve this. I can cook up the clock driver for the 32k clock from twl, but in order to use it we need CCF on OMAP. -- Péter -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
