From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 80625CA1012 for ; Thu, 4 Sep 2025 19:53:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=I++08KjYUaNnGA2vqwEBlEjrmrBVzCtUSpLQK9eM7Jw=; b=jocgDbPSY9yr2v4SjcDZSvj0oB 8BWf3YWHXxyUdId6qHBt2VA0rYJgV6BU9J1BaVSb/9NR5nwU6Yz6aIy113PYUi/OsiRhleBrF5xmA +xmbc9qxY6VgxWoLHW/I/PcuMqnPVuQoQq9vcLDuLOx88A3+Vp8ZM8nzyh1DKCw3drxzbyYgNV2Aw M+2EekaFM6AQ5wpquGgCM/pN6aVJgpjMMOiPINUgB+6oqgAtPQ+hTHeZpZyqYXSFh5eemSTxvv285 S1Hdcs5DqxK8V9gi2zDcr2I7fYwIrXyK8w0MK9maxwh+ORDpbxeoC1w1z/shUDl6XwzpZR6+97q1w aleMizXQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1uuG19-0000000E3bT-2iRs; Thu, 04 Sep 2025 19:53:11 +0000 Received: from bali.collaboradmins.com ([148.251.105.195]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1uuBlD-0000000CVDy-1jZN for linux-arm-kernel@lists.infradead.org; Thu, 04 Sep 2025 15:20:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1756999225; bh=lVG6RUOs/vuQiBSENy+Q+/Zs0wuP4CpZcsQ73d+Pss8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=U7Y5JcbY2K+IP0RMcFoAhMxwWToXwsmZAUBPqSUOj9V997aSIGUmbeK0y6imQs3Mq /yPGz/VKDcqdAlxxChCXdUDccQSCCrYO4CdLPYL4kBDnGqqnjlpchyf4QFdGbXfcpA s2cd5lGAV2Um5SV545DCTXRIJJPXvwOKFonzwsvH+mZSWKpDK5FZOkP+2ew0Rs5nHg wBtisdLnWdyT4UFDT1tBM9hQcvR5sfg7iZ7U/DEdUKx0NHagcfrDeXuT8Q/itWCbBc QjAgvmjtx5TS18EhBtX3mi52zUojjACKwpZnC5uobBoTUFImGh4oXZDLVVJa6ZGyBI cv54/J3WQod/w== Received: from fedora (unknown [IPv6:2a01:e0a:2c:6930:d919:a6e:5ea1:8a9f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bbrezillon) by bali.collaboradmins.com (Postfix) with ESMTPSA id A057617E04D6; Thu, 4 Sep 2025 17:20:24 +0200 (CEST) Date: Thu, 4 Sep 2025 17:20:19 +0200 From: Boris Brezillon To: Marek Vasut Cc: Peng Fan , linux-arm-kernel@lists.infradead.org, Conor Dooley , David Airlie , Fabio Estevam , Krzysztof Kozlowski , Liviu Dudau , Maarten Lankhorst , Maxime Ripard , Pengutronix Kernel Team , Philipp Zabel , Rob Herring , Sascha Hauer , Sebastian Reichel , Shawn Guo , Simona Vetter , Steven Price , Thomas Zimmermann , devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org, imx@lists.linux.dev Subject: Re: [PATCH v2 4/9] drm/panthor: Implement optional reset Message-ID: <20250904172019.58e5f589@fedora> In-Reply-To: <36298ed9-05e4-4871-8e99-dfe814342c29@mailbox.org> References: <20250321200625.132494-1-marex@denx.de> <20250321200625.132494-5-marex@denx.de> <20250324094333.7afb17a1@collabora.com> <20250325084349.344a0f11@collabora.com> <7aadf355-edf0-46fc-b969-65c3789375ca@denx.de> <20250325153507.61d82e39@collabora.com> <4c06aef3-a254-437c-aa15-8e3eb7bf5951@denx.de> <20250325155231.0d1b1000@collabora.com> <838a0c6b-845b-428d-86b3-1480e5b8080f@mailbox.org> <20250904082224.113d0cd1@fedora> <7d4e773b-64ac-49ce-8d8b-7a39c353d18f@mailbox.org> <20250904160445.1671f140@fedora> <36298ed9-05e4-4871-8e99-dfe814342c29@mailbox.org> Organization: Collabora X-Mailer: Claws Mail 4.3.1 (GTK 3.24.49; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250904_082027_604472_B8FB7FE5 X-CRM114-Status: GOOD ( 26.70 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 4 Sep 2025 16:54:38 +0200 Marek Vasut wrote: > On 9/4/25 4:04 PM, Boris Brezillon wrote: > > Hello Boris, > > >>>> I suspect the extra soft reset I did before "un-halted" the GPU and > >>>> allowed it to proceed. > >>> > >>> Hm, not quite. I mean, you still need to explicitly boot the MCU after > >>> a reset, which is what the write to MCU_CONTROL [1] does. What the > >>> soft-reset does though, is reset all GPU blocks, including the MCU. > >>> This means the MCU starts from a fresh state when you reach [1]. > >> > >> I have a feeling the write to MCU_CONTROL does nothing in my case. > > > > I believe it does, otherwise you wouldn't be able to kick the MCU > > and get things working until the first runtime suspend happens. I gut > > feeling is that there's something fishy in the FW or SoC integration > > that causes the FW HALT request to put the MCU/GPU in a bad state > > preventing further MCU_CONTROL(AUTO_START) from functioning correctly > > after that point. > > I wonder who at NXP could chime in ... Peng, do you know ? > > >> Is there some way to probe the MCU state before/after setting GLB_HALT, > >> and also before/after the MCU_CONTROL write, using > >> gpu_read()/gpu_write() register operations, to find out what is going on > >> with the MCU at each point ? > > > > Yes, there's an MCU_STATUS register [1]. > Is that the only register I can use , or is there something more > detailed ? This register only returns values 0..3 which is not very > informative. Not that I'm aware.