[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1514481444.7000.451.camel@intel.com>
Date: Thu, 28 Dec 2017 17:17:24 +0000
From: "Shevchenko, Andriy" <andriy.shevchenko@...el.com>
To: "tglx@...utronix.de" <tglx@...utronix.de>,
"alan@...ux.intel.com" <alan@...ux.intel.com>,
"Ailus, Sakari" <sakari.ailus@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>
Subject: IRQ behaivour has been changed from v4.14 to v4.15-rc1
Hi!
Experimenting with AtomISP (yes, code is ugly and MSI handling rather
hackish, though...).
So, with v4.14 base:
[ 33.639224] atomisp-isp2 0000:00:03.0: Start stream on pad 1 for asd0
[ 33.652355] atomisp-isp2 0000:00:03.0: irq:0x20
[ 33.662456] atomisp-isp2 0000:00:03.0: irq:0x20
[ 33.698064] atomisp-isp2 0000:00:03.0: stream[0] started.
Ctrl+C
[ 48.185643] atomisp-isp2 0000:00:03.0: <atomisp_dqbuf: -512
[ 48.204641] atomisp-isp2 0000:00:03.0: release device ATOMISP ISP
CAPTURE output
...
and machine still alive.
With v4.15-rc1 base (basically your branch + some my hack patches) the
IR
Q behaviour changed, i.e. I have got:
[ 85.167061] spurious APIC interrupt through vector ff on CPU#0,
should never happen.
[ 85.199886] atomisp-isp2 0000:00:03.0: stream[0] started.
and Ctrl+C does NOT work. Machine just hangs.
It might be related to this:
https://lkml.org/lkml/2017/12/22/697
Any comments, Thomas?
--
Andy Shevchenko <andriy.shevchenko@...el.com>
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Powered by blists - more mailing lists