Re: FYI: i.MX8MP ISP (RKISP1) MI registers corruption

From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Stefan Klug <stefan.klug@ideasonboard.com>
Cc: Dafna Hirschfeld <dafna@fastmail.com>,
	 Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	 Heiko Stuebner <heiko@sntech.de>,
	Paul Elder <paul.elder@ideasonboard.com>,
	 Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	 Ondrej Jirman <megi@xff.cz>,
	linux-media@vger.kernel.org,  linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: FYI: i.MX8MP ISP (RKISP1) MI registers corruption
Date: Tue, 05 Aug 2025 12:57:07 +0200	[thread overview]
Message-ID: <m34iumujcs.fsf@t19.piap.pl> (raw)
In-Reply-To: <m3cy9futcj.fsf@t19.piap.pl> ("Krzysztof Hałasa"'s message of "Fri, 01 Aug 2025 14:19:56 +0200")

Hi,

just in case someone finds it helpful:

SError Interrupt on CPU3, code 0x00000000bf000002 -- SError
CPU: 3 UID: 0 PID: 40083 Comm: devmem Not tainted 6.15+ PREEMPT
pstate: 60000000 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Kernel panic - not syncing: Asynchronous SError Interrupt

What did i do? Wrote 32-bit value to an ISP register (0x32E22E2E4C =
a histogram-64 register) while repeatedly reading other ISP
registers (in userspace). The video stream was active.

This ISP apparently has its own problems.
--
Krzysztof "Chris" Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa