Re: [PATCH] i2c: designware: use enable on resume instead initialization

From	christian.ruppert@alitech.com
Newsgroups	linux.kernel
Subject	Re: [PATCH] i2c: designware: use enable on resume instead initialization
Date	2015-06-24 09:40 +0200
Message-ID	<pENrQ-3eJ-13@gated-at.bofh.it> (permalink)
References	(2 earlier) <pzwBk-6xd-25@gated-at.bofh.it> <pzIj7-7eI-7@gated-at.bofh.it> <pEzyx-8kv-9@gated-at.bofh.it> <pEzyx-8kv-7@gated-at.bofh.it> <pEzRU-vQ-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Dear Lucas,

Lucas De Marchi <lucas.de.marchi@gmail.com> wrote on 23.06.2015 19:02:03:
> On Tue, Jun 23, 2015 at 1:45 PM,  <christian.ruppert@alitech.com> wrote:
> > Hello,
> >
> > Christian Ruppert/ALi_GVA/ALi wrote on 10.06.2015 17:05:16:
> [...]
> > The result is not very encouraging: Out of five (identical) designware 
i2c
> > controllers we have on my test SOC, the first one initialises properly 
but
> > the second one gets stuck in the famous irq loop right away when the
> > module is enabled in i2c_dw_init. The system never gets around to try
> 
> Are you using the pci or platform driver?  I noticed yesterday the pci
> version is failing here with a NULL pointer dereference.

The test was performed with the platform driver (instantiated through 
device tree).
I just re-checked and the ultimate problem which hangs/kills the system in 
my case is the IRQ loop.
I haven't observed any NULL pointer dereferences on the road.

Greetings,
  Christian

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] i2c: designware: use enable on resume instead initialization christian.ruppert@alitech.com - 2015-06-24 09:40 +0200

csiph-web