[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BvQ7gpye53=+egExfzX_hJLN9AiR2QY3cbEiDSb=9XJQ@mail.gmail.com>
Date: Tue, 22 May 2012 11:45:01 -0300
From: Fabio Estevam <festevam@...il.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Marc Reilly <marc@...esign.com.au>,
Samuel Ortiz <sameo@...ux.intel.com>,
Sascha Hauer <kernel@...gutronix.de>,
Philippe Rétornaz <philippe.retornaz@...l.ch>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: mc13xxx-core: kernel hangs after 'regmap_read'
On Tue, May 22, 2012 at 6:25 AM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Tue, May 22, 2012 at 10:53:21AM +1000, Marc Reilly wrote:
>
>> It was a new format which introduced a padding bit. I wonder if Mark Brown can
>> comment on whether any other devices are using it successfully. (Sorry I can't
>> offer more insights there).
>
> 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.
As I don't have a way to access the SPI pins via scope I did a
git checkout 91b5e7411, which corresponds to the following commit:
commit 91b5e741184ea9836cd7d7509e4f9b6eefa27df2
Author: Marc Reilly <marc@...esign.com.au>
Date: Sun Apr 1 16:41:37 2012 +1000
mfd: Use regmap for the mc13xxx-core register access
,and now at least it does not silently hang and gives me a regmap failure:
spi_imx imx31-cspi.1: master is unqueued, this is deprecated
mc13xxx spi1.1: Failed to initialize register map: -22
mc13xxx: probe of spi1.1 failed with error -22
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists