On Wed, Mar 10, 2010 at 12:49 AM, Jon Povey <jon.po...@racelogic.co.uk>wrote:
> I am porting our drivers from MV 2.6.10 kernel to Kevin's git kernel. > > We have 3 different boards using DM355, with different gpio / pinmux > setups. So far, our device drivers are modules which fiddle the pinmux > registers directly. > > I see in the git kernel that pinmux settings are defined in an array > per-CPU (i.e. dm355.c) and the board file calls davinci_cfg_reg for > those it wants setup. > > I'd like to build a single kernel which can support all of our board > types, possibly detecting which it is running on by a parameter passed > from u-boot. > > I could just update the hacks in our drivers, and our bootloader should > setup the muxing right anyway, but if there is a supported "right" way > to do this then I'd be interested to hear it. I like the debug warning > messages if muxing is changed and feel like I should be using that code. > > At the moment I am thinking that I might want to split up > davinci_cfg_reg into two functions so it's not hardwired to > soc_info->pinmux_pins, and I could pass my own mux_config structs in. If > this is of interest I can have a go at doing this and submitting the > patch here. > > Any thoughts welcome. thanks. > For board specific pinmux, you can put them in board-dm355-*.c. There are some board specific pinmux setup in board-da830-evm.c. Look for da8xx_pinmux_setup. Regards, Steve
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
