On 03/28/2016 03:01 PM, Hans de Goede wrote:
>> but unless there's a real need
>> for me to verify this,
>> I'll simply revert the u-boot patch and enjoy working GPIO.
> Given the entire discussion in this thread, I agree that fixing this
> in u-boot
> is best. But I do not see reverting the u-boot patch disabling ldo3/4
> by default
> as the solution. ldo3/4 are unused on most boards, so disabling them
> by default
> clearly is the right thing todo IMHO.

I just checked the Banana Pi, which exposes ports from bank E on its
CON1. Admittedly,
that's the "Camera Serial Interface", but that connector is explicitly
also labelled
as supporting various GPIO pins: http://www.bananapi.org/p/product.html

On the Cubietruck, there's also CN9, exposing some GPIO ports from bank G:

Given that there tend to be crashes on re-enabling LDO3+LDO4 and many
boards expose affected pins (not only for CSI!): wouldn't be it be the
best to
keep them enabled?

FWIW, Olimex did reply to my inquiry regarding misleading pin names:

> I see. We used this Allwinner document as original reference design:
> a20_pad_std_v1_1.pdf @ sunxi
> <http://dl.linux-sunxi.org/A20/a20_pad_std_v1_1.pdf> - if you inspect
> the schematic you'd notice that the signals connected to E18 and E19
> are named respectively CSI1-VCC and CSI0-VCC. Hence, this is where the
> wrong naming of our processor pins came from. I'll add the proposal
> for correction for the future hardware revision of the boards affected.
> The difference between our boards and other boards come from the
> simple fact that their designs use 3.3V cameras, while we followed the
> original reference design and used 2.8V camera in A20-SOM-EVB (we even
> used the same camera - GT2005).


You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to