On Mon, Jan 12, 2015 at 10:39:38AM +0800, Chen-Yu Tsai wrote: > On Thu, Jan 8, 2015 at 5:38 PM, Maxime Ripard > <[email protected]> wrote: > > On Sat, Dec 20, 2014 at 08:43:27PM +0800, Chen-Yu Tsai wrote: > >> > That looks a lot like the A10 MMC clock. What's changing? only the > >> > data to feed to the factors setup code? > >> > >> That's correct. Only the mux width in the data fed to the setup code > >> and the lock differ. > >> > >> The hardware can work with the a10 mod0 code, but it won't recover from > >> cases where someone writes to the upper bits of the mux, since it doesn't > >> know about them. > > > > I'd very much prefer if we could factorise that code then. > > I was hoping to not have to extend sunxi-factors-clk any more. But yes, > I can add mux_width and mux_table fields to factors_data.
I didn't really thought of putting it into sunxi-factors, just have a common probe for the two, with for example the code checking which compatible is used, and put one value or another. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
