* Eero Nurkkala <ext-eero.nurkkala@xxxxxxxxx> [090108 12:25]: > > Looks like we now have some McBSP clock issue probably related > > to the custom clock: > > Could you please try: > http://marc.info/?l=linux-omap&m=122597514326263&w=2 > > And possibly ack the patch? Well this has been on hold as we don't know yet if we should use or not use custom clocks. Custom clocks allow combining multiple clocks into a single clock, which makes it easy to use in the drivers. However, custom clocks have some problems that Paul has pointed out, like not knowing the parent. At this point I'd say that if Paul does not like custom clocks, we should stop using them. Up to Paul to decide me thinks unless somebody has better ideas. > McBSP has a known spin-lock deadlock, why carry it around? Would be nice to get rid of the spin-lock issue.. But this patch still does not help with the McBSP clocks failing because the parent is not known. Regards, Tony -- 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
