Question on pin mux being done at u-boot (was Re: [beagleboard] Re: [PATCH-OMAP3 v3] Modified pinmux to enable HSUSB2 (EHCI) on Beagle.)

one generic question:

Looks correct to me.

Thanks. I'm also providing the patch as an attachment, since some folks
have problems with what the Google Groups does to the e-mail.

Two questions here:
a) cant we have a common mux for all boards.. things like musb, sdrc
etc is generally common..
b) why should u-boot bear the burden of pin muxing everything that it
does not use? should it not be the job of the kernel mux framework to
handle it?
Regards,
Nishanth Menon

one generic question:

Looks correct to me.

Thanks. I'm also providing the patch as an attachment, since some folks
have problems with what the Google Groups does to the e-mail.

Two questions here:
a) cant we have a common mux for all boards.. things like musb, sdrc
etc is generally common..

Sounds like a good idea, but I think there will need to be a delta set as well. There are a lot of pins to manage, so getting to a common baseline might be nice, but it will need to remain flexible for new production systems.

b) why should u-boot bear the burden of pin muxing everything that it
does not use? should it not be the job of the kernel mux framework to
handle it?

U-boot should not. Some of this has come down to laziness/lack-of-time to address in the kernel where it belongs. That said, I want to use several of these features, such as the USB EHCI port, in u-boot, so it would need to be done here in u-boot anyway.