>> >>[...] [I am not about to repeat everything I stated in previous >>threads.. so snipping the discussion down.] >> >>> >>> Otherwise the primary idea to remove OPP ID is good, and the way to go. >> >>good. So lets NAK that SR series and see how else we can implement it >>without OPP ID. I am open to any clean mechanisms you may propose >>without using OPP ID referencing :). Ok guys.. In the current V2 series , I have linked N targets with voltage.. Only it does not come from voltage layer but from smartreflex devices layer. The smartreflex driver does not use opp ids at all.. Also whether you call it by opp ids or by any other name, we need to know the number of different voltages supported by VDD1 and VDD2 and form the table.. That is exactly what I am doing in smartreflex device layer. I am just creating a table with different voltages and N target values associated with those voltages. To create this table I need to know there should be 5 voltages for VDD1 and 3 voltages for VDD2 which unfortunately coincides with the number of different OPP's defined in OMAP3430 today.. I also think it is an excellent idea to NAK a series of 19 patches for which everybody has been shouting for, for this reason. Regards Thara -- 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
