William,

The omap_mux stuff doesn't really exist the same way it used to exist. Previously, the board files would preload a set of pin mux options based on the the chip package. As part of that pre-load it was more easily known which pins corresponded to which GPIO's and which were shared.

Now, the device tree handles most of that. For GPIO pins that have not been assigned to devices, you can still use the export mechanism to get the GPIO. If you want to do the pin mux, I suggest defining those in the bootloader.

If you don't have the DM3730 Technical Reference Manual, I would suggest downloading it from TI. I can't share it due to NDA, but you can download it from them.

What you'll want to do is form the register value for each GPIO.

For example, if you want the GPIO_103 to be setup as an output, you can look at the technical reference manual for the address for GPIO_103.

From the TRM, this is going to be the high 16 bits of 0x4800 211c (or you can directly address is at 0x4800211e as a 16-bit word), and you'll want MODE4

The description of how the registers are set are defined in CONTROL_PADCONF_X.

If you want to make a GPIO_103 pin mux as mode 4 without anything special, you can write 0x04 to 0x4800211c using devmem

Once you have done that, you should be able to export the GPIO pins as usual:

#export gpio to sysfs
echo 103 > /sys/class/gpio/export

#set pin as output
echo out > /sys/class/gpio/gpio103/direction

#Set pin driver level
echo 0 > /sys/class/gpio/gpio103/value


Let me know if that helps.

adam

Really helped. Thank you.