sricharan wrote: > > 1) All the pads of a hwmod for the device are classified > as static/dynamic. If a pad requires remuxing during > the device transitions between enable/idle transitions > then it is added to the dynamic list, static otherwise. > > 2) Both the static/dynamic pads of a hwmod are initialised > when the device gets enabled. When the device transitions > between enable/idle the dynamic pads are remuxed and > static pads are skipped. > > 3) When the driver gets removed both the static and the > dynamic pads are muxed to safe mode as default. > I haven't taken a look at the code. I do have a few concerns (which may really be non-issues, but I'm pointing them out anyway): - Not all pads have a safe mode. --- And why would you want statically muxed pads to be remuxed into safe mode anyway? What is the advantage of such a change, as against leaving them in a functional mode? - Many signals are muxed on more than one pad. - Many peripherals need pads to be configured in different mux modes depending on the way a board is wired up. With this, moving pad info to hwmod databases does not sound useful to me. Maybe I do not understand the need for this change, in place of what we have today. - Anand -- 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
