Date: Fri, 11 Mar 2016 18:14:46 +0100
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Jean-Denis Girard <jd.girard@sysnux.pf>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] v4.4.4-rt11
Message-ID: <20160311171446.GB3815@breakpoint.cc>
References: <20160309135142.GF10517@linutronix.de>
 <nbq16a$7li$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8BIT
In-Reply-To: <nbq16a$7li$1@ger.gmane.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1219
Lines: 33

On 2016-03-09 10:31:06 [-1000], Jean-Denis Girard wrote:
> Hi,
Hi,

please don't cut people from TO and CC.

> Le 09/03/2016 03:51, Sebastian Andrzej Siewior a écrit :
> > - AT91 got a little better. A larger patch series by Boris Brezillon has
> >   been merged. That means SAMA5 boots now. There is one warning left
> >   about invoking free_irq() twice. I would be glad about some feedback
> >   from pre-SAMA5 SoC. Those which share UART and timer interrupt. It
> >   seems that that one I have here does not do this anymore.
> > 
> > - A patch on top the AT91 series to avoid two warning while switching
> >   from period to oneshow mode.
> 
> I got this warning when booting my arietta G25:
> 
> clocksource: pit: mask: 0xfffffff max_cycles: 0xfffffff, max_idle_ns:
> 14334453866 ns
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 0 at kernel/irq/manage.c:1541 __free_irq+0xb0/0x2b0()
> Trying to free already-free IRQ 16

…
> Nevertheless it does boot, and seems to work fine.
This looks promising. Can you check if IRQ 16 is used by another
peripherals? While we need get rid fo the warning I am curious if it
works on boards which chare the timer with UART or something.

> Thanks,

Sebastian