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 B97D8C4167B for ; Fri, 8 Dec 2023 11:22:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:CC:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=fj+l+bgwPtE21GRWkNP2zrFP1UKJSfqCfHQ3AHjjB3s=; b=QclwWsDQD+O3Gy 0AIrw4A7sD5Ln0QnnGmEbCwLsndlViE0YYm4TFObU1JWPwQTh7bUw9tnzTDU9xFlX5r/M6Ap/zwz3 6q5UMeEBqBMwpzULYqsAmFldMxC6zRCLq3kd4hXNgGBg32Oj90FOreog8j8ynoVJcl1KK+sHNQF0c pVquXJr9We2AY5yEPOUzPiguC8CE8TeX7rMtd8KqOyMkRfDTXQMhLgsBKWcgdQY1htOHzOOynrGV3 o99n2K4oEH4T0ytRf9ykgbFbNCJGccg6l6wnF8WvyTGSN2GadN+AMp/ZHgVMaueCQhHFAkaqWzazq 7u8HtWIoZ9LNFvUpFPsg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rBYvW-00FShE-1f; Fri, 08 Dec 2023 11:21:50 +0000 Received: from fllv0016.ext.ti.com ([198.47.19.142]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rBYvT-00FSbh-0U for linux-arm-kernel@lists.infradead.org; Fri, 08 Dec 2023 11:21:49 +0000 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 3B8BLh2e002284; Fri, 8 Dec 2023 05:21:43 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1702034503; bh=oLg0AisyamUAtVSfksyGAW5Md+GYqQaIkcHjjDZN0+M=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=JBo6OQEaEjo4IiHFUd8QMeejBINXQLmQfVF8diQajDCYn8bBY/vkw5b6xry6uqAmB /4xKovFzdv8OPaPiW6Aukip5ZvsgHoTaj5Bnosqe0Kefv6VRoKTLJM4+lFQq+RC9A/ e74XqpXBO4g5ECzxGFxNdEkHuQeF177X2DAh+Zec= Received: from DLEE114.ent.ti.com (dlee114.ent.ti.com [157.170.170.25]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 3B8BLgs7015127 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 8 Dec 2023 05:21:43 -0600 Received: from DLEE107.ent.ti.com (157.170.170.37) by DLEE114.ent.ti.com (157.170.170.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Fri, 8 Dec 2023 05:21:42 -0600 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DLEE107.ent.ti.com (157.170.170.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Fri, 8 Dec 2023 05:21:42 -0600 Received: from [10.249.48.175] ([10.249.48.175]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 3B8BLgjq055436; Fri, 8 Dec 2023 05:21:42 -0600 Message-ID: Date: Fri, 8 Dec 2023 05:21:42 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH v3 3/5] remoteproc: k3-r5: Add support for IPC-only mode for all R5Fs Content-Language: en-US To: Jan Kiszka , Mathieu Poirier CC: Suman Anna , Bjorn Andersson , Praneeth Bajjuri , , , , Nishanth Menon , "Su, Bao Cheng (RC-CN DF FA R&D)" References: <20220213201246.25952-1-s-anna@ti.com> <20220213201246.25952-4-s-anna@ti.com> <106f3a36-16d8-4272-ad7a-287e6a3acfb5@siemens.com> From: Hari Nagalla In-Reply-To: <106f3a36-16d8-4272-ad7a-287e6a3acfb5@siemens.com> X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231208_032147_379000_8C07133E X-CRM114-Status: GOOD ( 11.85 ) 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: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 11/2/23 11:43, Jan Kiszka wrote: >>> RTI1 watchdog also powers up R5F core 1. And this could happen either in >> When writing "... also powers up...", other than R5F core 1, what else is being >> powered? > Would be a question for the SoC vendor - I assumed that only mcu_rti1 > [1] goes on when enabling it. But also mcu_r5fss0_core1 is enabled after > that, at least according to the respective TI-SCI query that the is_on > handler is performing. I've tested that under Linux and in U-Boot. > As described in section 12.5.2.1 of AM64x TRM (https://www.ti.com/lit/pdf/SPRUIM2) -There is a RTI for each CPU core. And it is not intended to be use RTI provisioned for a particular CPU core with a different core. And also as shown in section (5.2.2.2.1.3.1) the CPU core and corresponding RTI share the same power sub module (LPSC), so enabling one powers on the other. As Suman suggested, it seems more appropriate to enable the RTI watchdog timers in the remoteproc driver. Legacy omap remoteproc drivers have this support and needs to be extended to k3 remoteproc drivers. Another option could be to DEFER RTI probe until corresponding remoteproc driver is probed. Any other solutions to maintain this order of enabling remote core and the corresponding RTI/WDT? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel