From: Michael Haas <haas@computerlinguist.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Linux hangs due to commit v2015.10-15-g02cc27c on loading i2c-mv64xx
Date: Sun, 20 Mar 2016 16:56:32 +0100 [thread overview]
Message-ID: <56EEC830.9090809@computerlinguist.org> (raw)
Hello all,
I'm running Debian Jessie with Linux 4.3.0-0.bpo.1-armmp-lpae on my
a20-olinuxino-lime2.
I have noticed that my board hangs with my recent u-boot versions when I
load the i2c module.
git-bisect narrowed the problem down to the following commit:
02cc27c74f9b884b538bcd1b93342a4c05b5d608 is the first bad commit
commit 02cc27c74f9b884b538bcd1b93342a4c05b5d608
Author: Hans de Goede <hdegoede@redhat.com>
Date: Sat Oct 3 15:29:24 2015 +0200
sunxi: power: Change axp209 LDO3 and LDO4 default to disabled
LDO3 and LDO4 are normally either unused, or used to power csi
attached camera sensors, and as such do not need to be enabled at
boot time.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Ian Campbell <ijc@hellion.org.uk>
:040000 040000 9ff2e54e613a4386473cdf66c3bc5dc830a31bc7
d5330c13ef2c86643499f476b7042748969fd523 MT>>>>>drivers
The axp209 is attached to the i2c bus, so that is likely the real
culprit. In my setup, the axp209 drivers are loaded before I insert
i2c-mv64xxx.
What would be the best course of action here?
* Revert the commit
* Enable LDO3 and LDO4 for the a20-olinuxino-lime2 only?
* Fix linux
Best,
Michael
next reply other threads:[~2016-03-20 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 15:56 Michael Haas [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-20 19:15 [U-Boot] Linux hangs due to commit v2015.10-15-g02cc27c on loading i2c-mv64xx Hans de Goede
2016-03-25 7:59 ` Michael Haas
2016-03-28 13:02 ` 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=56EEC830.9090809@computerlinguist.org \
--to=haas@computerlinguist.org \
--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