From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel-2 for v3.2
Date: Thu, 6 Oct 2011 18:14:18 +0100 [thread overview]
Message-ID: <20111006171418.GA23532@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111006155701.GA1470@opensource.wolfsonmicro.com>
On Thu, Oct 06, 2011 at 04:57:01PM +0100, Mark Brown wrote:
> The bisect did end up pointing at the GPIO commits, the build errors
> were causing issues. Not really made any further progress on this issue
> today, some other things came up.
So, I've been trying some other directions here. What I'm seeing by
pulling devices out of my config is that if I enable the LCD power
control then the board fails to boot. Also, the I2C controllers appear
to be non-functional - I'm getting timeouts waiting for the bus to
become free which halt the boot for long enough that it'd look like it
had crashed if all the devices came up (there's a lot of I2C devices
there).
I've not had time to actually drill down below that level but it did
occur to me that there may be a problem with the pinmux code?
next prev parent reply other threads:[~2011-10-06 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 9:25 [GIT PULL] Samsung devel-2 for v3.2 Kukjin Kim
2011-10-02 19:29 ` Mark Brown
2011-10-03 3:27 ` Kukjin Kim
2011-10-03 10:36 ` Mark Brown
2011-10-03 11:22 ` Russell King - ARM Linux
2011-10-03 12:16 ` Mark Brown
2011-10-07 17:56 ` Arnd Bergmann
2011-10-07 19:14 ` Mark Brown
2011-10-10 4:27 ` Kukjin Kim
2011-10-20 12:57 ` Arnd Bergmann
2011-10-04 12:45 ` Kukjin Kim
2011-10-04 12:59 ` Mark Brown
2011-10-05 16:54 ` Mark Brown
2011-10-05 23:05 ` Mark Brown
[not found] ` <00e601cc83f1$3298e660$97cab320$%kim@samsung.com>
[not found] ` <20111006155701.GA1470@opensource.wolfsonmicro.com>
2011-10-06 17:14 ` Mark Brown [this message]
2011-10-07 10:58 ` Kukjin Kim
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=20111006171418.GA23532@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).