From: "Philippe Rétornaz" <philippe.retornaz@epfl.ch>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Marc Reilly <marc@cpdesign.com.au>,
Samuel Ortiz <sameo@linux.intel.com>,
Sascha Hauer <kernel@pengutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mc13xxx-core: kernel hangs after 'regmap_read'
Date: Tue, 22 May 2012 14:48:28 +0200 [thread overview]
Message-ID: <2220592.xdm62UZBs9@laptop> (raw)
In-Reply-To: <CAOMZO5DJUXna-zn98Zs0exin+THQhB3SG9To5N-QEEcDYrmXRA@mail.gmail.com>
Le mardi 22 mai 2012 08:40:30 Fabio Estevam a écrit :
> Hi Philippe,
>
> On Tue, May 22, 2012 at 6:25 AM, Mark Brown
>
> <broonie@opensource.wolfsonmicro.com> wrote:
> > It's only this chip that's doing so. I'd suggest putting a scope on it
> > and having a look at the formatted data.
>
> Does mx31-moboard allow you to put the scope on the SPI lines
> connected to the mc13783?
Yes, I have access to MISO/MOSI/CLK, but not CS on mx31moboard.
BTW, mx31-ads give access to the full SPI bus, but I never booted it.
I cannot debug this right now, but I should be able to do it on friday.
Regards,
Philippe
next prev parent reply other threads:[~2012-05-22 12:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:06 mc13xxx-core: kernel hangs after 'regmap_read' Fabio Estevam
2012-05-22 0:53 ` Marc Reilly
2012-05-22 9:25 ` Mark Brown
2012-05-22 11:40 ` Fabio Estevam
2012-05-22 12:48 ` Philippe Rétornaz [this message]
2012-05-22 14:45 ` Fabio Estevam
2012-05-23 1:12 ` Fabio Estevam
2012-05-23 2:05 ` Fabio Estevam
2012-05-23 8:49 ` Mark Brown
2012-05-23 14:18 ` Fabio Estevam
2012-05-23 15:29 ` Fabio Estevam
2012-05-23 17:36 ` Mark Brown
2012-05-23 19:32 ` Fabio Estevam
2012-05-23 16:42 ` Shawn Guo
2012-05-23 16:34 ` Fabio Estevam
2012-05-24 0:48 ` Shawn Guo
2012-05-24 4:07 ` Fabio Estevam
2012-05-24 6:04 ` Shawn Guo
2012-05-24 6:39 ` Shawn Guo
2012-05-24 6:46 ` Uwe Kleine-König
2012-05-24 7:33 ` Shawn Guo
2012-05-24 9:08 ` Marc Reilly
2012-05-24 10:37 ` Mark Brown
2012-05-24 11:22 ` Marc Reilly
2012-05-24 12:14 ` Mark Brown
2012-05-24 13:06 ` Marc Reilly
2012-05-24 16:37 ` Mark Brown
2012-05-24 13:01 ` Fabio Estevam
2012-05-24 13:38 ` Marc Reilly
2012-05-24 16:16 ` Philippe Rétornaz
2012-05-24 16:36 ` Mark Brown
2012-05-24 16:41 ` Uwe Kleine-König
2012-05-24 17:39 ` Fabio Estevam
2012-05-24 18:03 ` Mark Brown
2012-05-24 19:42 ` philippe.retornaz
2012-05-24 22:21 ` Mark Brown
2012-05-25 8:56 ` Shawn Guo
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=2220592.xdm62UZBs9@laptop \
--to=philippe.retornaz@epfl.ch \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@cpdesign.com.au \
--cc=sameo@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.