Hi Laurent,
On Fri, Feb 19, 2016 at 1:07 AM, Laurent Pinchart
wrote:
> Hi Magnus,
>
> On Friday 19 February 2016 01:02:18 Magnus Damm wrote:
>> On Fri, Feb 19, 2016 at 12:33 AM, Laurent Pinchart wrote:
>> > On Thursday 18 February 2016 10:17:16 Geert
Hi Magnus,
On Friday 19 February 2016 01:02:18 Magnus Damm wrote:
> On Fri, Feb 19, 2016 at 12:33 AM, Laurent Pinchart wrote:
> > On Thursday 18 February 2016 10:17:16 Geert Uytterhoeven wrote:
> >> On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto wrote:
> >> I tried this patch, but It
Hi Geert,
On Thursday 18 February 2016 10:17:16 Geert Uytterhoeven wrote:
> On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto wrote:
> I tried this patch, but It didn't use this printk().
> Am I wrong ?
>
> -
> diff --git
Hi Morimoto-san,
On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto
wrote:
>> > > I tried this patch, but It didn't use this printk().
>> > > Am I wrong ?
>> > >
>> > > -
>> > > diff --git a/drivers/regulator/da9210-regulator.c
>> > >
Hi Geert, again
> > > I tried this patch, but It didn't use this printk().
> > > Am I wrong ?
> > >
> > > -
> > > diff --git a/drivers/regulator/da9210-regulator.c
> > > b/drivers/regulator/da9210-regulator.c
> > > index 01c0e37..85c1166 100644
> > > ---
Hi Geert
> > I tried this patch, but It didn't use this printk().
> > Am I wrong ?
> >
> > -
> > diff --git a/drivers/regulator/da9210-regulator.c
> > b/drivers/regulator/da9210-regulator.c
> > index 01c0e37..85c1166 100644
> > --- a/drivers/regulator/da9210-regulator.c
> > +++
Hi Morimoto-san,
On Thu, Feb 18, 2016 at 9:39 AM, Kuninori Morimoto
wrote:
>> > [ 59.144598] irq 311: nobody cared (try booting with the "irqpoll"
>> > option)
>> > [ 59.151419] CPU: 0 PID: 410 Comm: irq/311-da9210 Not tainted
>> > 4.5.0-rc3-02009-g83c516e
Hi Geert
> > [ 59.144598] irq 311: nobody cared (try booting with the "irqpoll" option)
> > [ 59.151419] CPU: 0 PID: 410 Comm: irq/311-da9210 Not tainted
> > 4.5.0-rc3-02009-g83c516e #612
>
> Ugh, the da9210 interrupt.
>
> That probably means an event was set that isn't handled by
>
Hi Laurent
> I've ran into a WARN_ON related to the sound driver on v4.5-rc3 on Lager. The
> problem doesn't seem to occur on v4.4. It also doesn't occur at every boot,
> you sometimes have to boot the board several times before reproducing it (up
> to 5 times in my tests, but usually less