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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C7AC5C05027 for ; Fri, 10 Feb 2023 14:01:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232376AbjBJOBN (ORCPT ); Fri, 10 Feb 2023 09:01:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44134 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231894AbjBJOBL (ORCPT ); Fri, 10 Feb 2023 09:01:11 -0500 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 11E637498B; Fri, 10 Feb 2023 06:01:07 -0800 (PST) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id BA70466020EA; Fri, 10 Feb 2023 14:01:05 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1676037666; bh=1nACN3toSy0bL2coCaCf797kOjg0fbtFmGw0pIIjUec=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=XwIoN4XWr/LgYYvHELLcVicMRL6rH8ofiB8rPR7eIYxCvOrPnNzn0fc8GHQyEEwyP 75+9/rJn+tAKcrzp35XgjSrOFrpWZL1WYpT7uVPXrAxdoxdUdd4EDAP0GjqqRZZg08 wzfj2uRj9xTzG0WE5o7xLGXQaNFASLbbXDGYJTPFycTphEp19K66Lwx4ZBYzQoBVZk oiCrpHILMLA1I0Ngn6B4BgHzHCEooJMXfrFAWbTRjWStUHF4PpjhTkEWYftN075E0T ZTNLRyQMmeHOxvE/slcsIeQ/ZQhP1YqEZihnWC0IULBNyBHuPbdw67rPkC+bxHMYGd iM7ym8W8sp3sw== Message-ID: <2318282b-c61d-3f86-2053-ee20c7f13e7f@collabora.com> Date: Fri, 10 Feb 2023 15:01:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: [PATCH v5 10/12] remoteproc: mediatek: Handle MT8195 SCP core 1 watchdog timeout Content-Language: en-US To: Tinghan Shen , Bjorn Andersson , Mathieu Poirier , Rob Herring , Krzysztof Kozlowski , Matthias Brugger Cc: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com References: <20230210085931.8941-1-tinghan.shen@mediatek.com> <20230210085931.8941-11-tinghan.shen@mediatek.com> From: AngeloGioacchino Del Regno In-Reply-To: <20230210085931.8941-11-tinghan.shen@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 10/02/23 09:59, Tinghan Shen ha scritto: > The MT8195 SCP core 1 watchdog timeout needs to be handled in the > SCP core 0 IRQ handler because the MT8195 SCP core 1 watchdog timeout > IRQ is wired on the same IRQ entry for core 0 watchdog timeout. > MT8195 SCP has a watchdog status register to identify the watchdog > timeout source when IRQ triggered. > > Signed-off-by: Tinghan Shen Reviewed-by: AngeloGioacchino Del Regno