Op 6 jan 2011, om 19:29 heeft Nishanth Menon het volgende geschreven:
> Koen,
> Apologies on a late response.
>
> Koen Kooi had written, on 12/19/2010 08:42 AM, the following:
> [...]
>> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
>> b/arch/arm/mach-omap2/board-omap3beagle.c
>> index f1a8ede..4756ac7 100644
>> --- a/arch/arm/mach-omap2/board-omap3beagle.c
>> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
>> @@ -297,13 +297,35 @@ static int beagle_twl_gpio_setup(struct device *dev,
> [..]
>> +
>> + /* Power on DVI, Serial and PWR led */
>> + if (omap3_beagle_get_rev() == OMAP3BEAGLE_BOARD_XM) {
>> + gpio_request(gpio + 1, "nDVI_PWR_EN");
>> + gpio_direction_output(gpio + 1, 0);
>> + }
> earlier in this function, we do:
> gpio_request(gpio + 1, "EHCI_nOC");
> gpio_direction_input(gpio + 1);
> here we do
> gpio_request(gpio + 1, "nDVI_PWR_EN");
> gpio_direction_output(gpio + 1, 0);
>
> I am confused. is gpio+1 input or output line? and what level should it be on?
On early revB prototypes it was used to sense USB overcurrent, I'm not sure
what the current status is for that pin on revB and revC, but on xM it controls
the DVI, serial and led block.
Adding Gerald to CC: to see if he has some pearls of wisdom on this :)
regards,
Koen--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
