Hi, * sricharan <r.sricharan@xxxxxx> [110118 07:11]: > Pass the board specific serial pad mux data > to the platform level init code. > > Signed-off-by: sricharan <r.sricharan@xxxxxx> > --- > This is a test patch and not intended for a specific use case. > > 1) The support to add the pad data to the device hwmod entry and to use > it to dynamically configure the pads based on the state of the > hwmod is already present. > > 2) But using that for pads that requires only initialisation and not > dynamic remux, brings in a overhead to iterate over all the > hwmod signals of the device for every device enable/idle transitions. The right fix for this problem is to change the mux code to keep a separate list for dynamic pads and static pads. That way all the static pads can be skipped, and the dynamic list is empty in most cases. 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
