public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hendrik <chasake@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Sunxi (Allwinner A20) GPIO problems on u-boot 2016.1 and 2016.3-rc3 but not on 2015.10
Date: Thu, 3 Mar 2016 17:54:17 +0100	[thread overview]
Message-ID: <56D86C39.3060809@yahoo.com> (raw)
In-Reply-To: <56D7F498.3040900@redhat.com>

Hello Hans,

Thank you very much for your message. The PIO program reported 
'PE6<0><0><1><1>' for both U-Boots but changing the configuration's 
CONFIG_AXP_ALDO3_VOLT and CONFIG_AXP_ALDO4_VOLT back to 2800 did indeed 
solve the problem. I can run U-Boot 2016.01 now and control PE6 properly.

LDO3 is connected to pin F19 in the Olimex schematics (VCC_CSI0, in the 
A20 datasheet mentioned as Port E Power Supply) and LDO4 is connected to 
pin E18 (VCC_CSI1 mentioned as Port G Power Supply).

So would the change in u-boot make sense by setting the default to 0 
now? I'm not sure if the git remark 'LDO3 and LDO4 are normally either 
unused, or used to power csi attached camera sensors' is correct as it 
seems (also?) to be the source or reference for the A20 chip pins 
itself..? At least this is the case for multiple (all?) Olimex A10/A20 
boards (I checked A20-SOM, A20-LIME2, A20-Lime and A10-Lime).

Regards,
Hendrik

  reply	other threads:[~2016-03-03 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 16:54 [U-Boot] Sunxi (Allwinner A20) GPIO problems on u-boot 2016.1 and 2016.3-rc3 but not on 2015.10 Hendrik
2016-03-03  8:23 ` Hans de Goede
2016-03-03 16:54   ` Hendrik [this message]
2016-03-04  7:54     ` Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56D86C39.3060809@yahoo.com \
    --to=chasake@yahoo.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox