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: resolved
Date: Tue, 12 Aug 2025 07:54:46 +0200 [thread overview]
Message-ID: <m3a545t789.fsf@t19.piap.pl> (raw)
In-Reply-To: <m3zfcet41n.fsf@t19.piap.pl> ("Krzysztof Hałasa"'s message of "Tue, 05 Aug 2025 13:13:08 +0200")
Hi Stefan et al,
BTW I've added Lucas Stach and Shawn Guo to "Cc" list.
The problem is the CPU core power supply voltage :-)
- while the reference manual specifies the max ISP and MEDIA clocks at
500 MHz, the datasheets show this requires the "overdrive" mode =
increased CPU power supply voltage. In "normal" mode the ISPs are
limited to 400 MHz (there are other limits, too).
- I've tried lowering the clock rate after booting the systems (with
a CCM register write), but it didn't fix the problem. I guess some
reset logic is affected here, and the (lower) clock rate must be set
right from the start, in the DT.
- anyway, lowering the frequencies of ISP and MEDIA root clocks fixes
the ISP2 MI corruption. I'm currently investigating PMIC settings
(both my Compulab and SolidRun modules use PCA9450C PMICs), so perhaps
I'll be able to use the higher 500 MHz clocks. It doesn't matter much,
though.
- the question is if we should lower the clocks in the main imx8mp.dtsi
DT file, or the overdrive mode should stay there, and the changes
should be made to the individual board files, or maybe the U-Boot
configs (PMIC output voltages) should be changed etc.
--
Krzysztof "Chris" HaBasa
Sieć Badawcza Aukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2025-08-12 5:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 9:00 FYI: i.MX8MP ISP (RKISP1) MI registers corruption Krzysztof Hałasa
2025-07-17 13:03 ` Krzysztof Hałasa
2025-07-21 8:46 ` Stefan Klug
2025-07-21 13:16 ` Krzysztof Hałasa
2025-07-23 10:19 ` Stefan Klug
2025-07-23 12:06 ` Krzysztof Hałasa
2025-07-23 12:09 ` Laurent Pinchart
2025-07-24 4:20 ` Krzysztof Hałasa
2025-07-24 8:21 ` Krzysztof Hałasa
2025-07-25 11:09 ` Stefan Klug
2025-07-30 10:30 ` Krzysztof Hałasa
2025-08-01 12:19 ` Krzysztof Hałasa
2025-08-05 10:57 ` Krzysztof Hałasa
2025-08-05 11:13 ` Krzysztof Hałasa
2025-08-12 5:54 ` Krzysztof Hałasa [this message]
2025-08-12 10:32 ` FYI: i.MX8MP ISP (RKISP1) MI registers corruption: resolved Laurent Pinchart
2025-08-12 12:28 ` Krzysztof Hałasa
2025-08-12 15:02 ` Stefan Klug
2025-08-12 18:22 ` Adam Ford
2025-08-13 5:10 ` Krzysztof Hałasa
2025-09-02 9:54 ` Krzysztof Hałasa
2025-09-02 11:23 ` Alexander Stein
2025-09-03 0:56 ` Paul Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3a545t789.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=dafna@fastmail.com \
--cc=heiko@sntech.de \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=megi@xff.cz \
--cc=paul.elder@ideasonboard.com \
--cc=stefan.klug@ideasonboard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox