I am currently building a torpedo IO board.  Uboot is always returning that my torpedo SOM is actually a SOM LV.  It appears in hardware that the SOM LV has a pull down resistor on GPIO 189.  The torpedo does not. 

 In uboot I see it running this test to distinguish the two:

        if (!omap_request_gpio(189)) {
                twl4030_usb_ulpi_init();

                omap_set_gpio_direction(189, 0);
                omap_set_gpio_dataout(189, 1);

                /* Let it soak for a bit */
                for (i=0; i<0x100; ++i)
                        asm("nop");

                omap_set_gpio_direction(189, 1);
                val = omap_get_gpio_datain(189);
                omap_free_gpio(189);

                printf("Board:");
                if (cpu_family == CPU_OMAP36XX) {
                        /* printf(" DM37xx"); */
                        printf(" DM37xx");
                        if (val) {
                                printf(" Torpedo\n");
                                val = MACH_TYPE_DM3730_TORPEDO;
                        } else {
                                printf(" SOM LV\n");
                                val = MACH_TYPE_DM3730_SOM_LV;
                        }
                } else {
                        printf(" OMAP35xx");
                        if (val) {
                                printf(" Torpedo\n");
                                val = MACH_TYPE_OMAP3_TORPEDO;
                        } else {
                                printf(" SOM LV\n");
                                val = MACH_TYPE_OMAP3530_LV_SOM;
                        }
                }
        }

The resistor for GPIO 189 is actually on the module.  Why is u-boot always telling my torpedo linux image to boot as a SOM LV.  I do not understand how this works with this GPIO.  I also do not understand why my uboot continues to get it wrong if it does work.