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 1C8FDC433FE for ; Fri, 4 Nov 2022 15:36:38 +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-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: 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=4jFmqIMhnFXc58Uwb6FzPU1YE25mmkcZ3Qw25elPr/o=; b=j1hYb5Moqu81Gf JN/RaxXW8VQklU8kW1xahm1lDXp74DXtMnZUTzyJ9g4i45xOboEGj9VLWi3MfGW/BKvhOqTNJQHjt PSbyAEeB0agV0mAVx7AgM2QTohjlKa9Yh+q23ZhEwXlrs7SRSoige1idC24v+ALTrUyoxqBnVW0kH hkDRZe4I2aRosXIaK+nlQSVI9vkbY6/HSCjmZH4jNM05+AmB27Gu9Utd0uzTfnD0LsAHjNdP+8NU6 LTdnMTCMPUULBlW96AxAlU7dedDnSWc63gPTQg+DDKhoEM4z26kteFFudvb3B7zqVyPVV01Uvp/Um ynuE0PzLJDAukGkRbxbw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oqyj4-004FzR-E7; Fri, 04 Nov 2022 15:35:23 +0000 Received: from mail-pj1-x1036.google.com ([2607:f8b0:4864:20::1036]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oqygu-004F5M-S0 for linux-arm-kernel@lists.infradead.org; Fri, 04 Nov 2022 15:33:10 +0000 Received: by mail-pj1-x1036.google.com with SMTP id m14-20020a17090a3f8e00b00212dab39bcdso8586300pjc.0 for ; Fri, 04 Nov 2022 08:33:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=fwuTjqh5pt+T/yYu3FHsWOz2YtfUvi8Iieag/ZSiRiI=; b=mUGHyoC6q0AXBVQqWwsb32J2056BLwrKl4y7GwDajJHCUtjvfbwRFnqKRnFA1xr7RB v63EqXCwpiveM3wF3wyelzhFz/2rC9ZGb1cVRjjI0udOf9pVtxWu2V6t/AxwEStkLlFM Hdf2j8e3uQWAdke63x6t9s7Fw3ODFkC1jGHzMcpo4SHdNYpeUy0h23e5YCROwxsfszMA VNP3XVVDtvY3oTmKVjF81d61hn5manpCmKspE6DfmFzubsUmkW3+O9Tnhje6cIQjHyW1 ckq5QODV+iGkwaI2kLOq+o53YPPVAoMNSaMMQ2ONUV+ckA/F7+HNYLS0TEHWkacuJUgb 7dAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=fwuTjqh5pt+T/yYu3FHsWOz2YtfUvi8Iieag/ZSiRiI=; b=l9MtBKD8RJJpSSgXt0oO33Pk6V0U0d3wY4b/exTqApptEnEpUQ5rmsa14VuUcydb7P qV+ifb2piqsw4z2GpD5n3TcqWm6hAQqLRbYH0mOrb/XgaFzPz4RqgHN6yogDPw59xERx qHMMWWPnjl+qeEL+XYHvO00gWYJbauRM0tW90Z939jSfUuHT4Isrmh8NONEp1Lj7gstz jrZOTeH7j5UnGvh1bFqEX+MqxgKYWPDcd9NMxGvhN+jXefvhCOjeR9Uv7jGKba06HVeJ flhRY9hPLysZbJxtSdhbjG4oJROUzQuyWcj6oe3VCRbixsIBvCgQSzaSGkuDqFJFL9lQ NT2w== X-Gm-Message-State: ACrzQf1iNwtAZyip9/xUdd6BDHCpiCz1V5IjPego+8OnFm2VBK6neFJH MDkxc8hSCRSeHnPM+9A7bAgBMQ== X-Google-Smtp-Source: AMsMyM7JAkk+7adsv1QrArHLc7M40uX5VtZ5DcNDHDmI2vsZJDwFKlnpmjGImj3BDo+hl+pG+d3Dgw== X-Received: by 2002:a17:902:e54b:b0:188:4c74:300e with SMTP id n11-20020a170902e54b00b001884c74300emr12478917plf.45.1667575986981; Fri, 04 Nov 2022 08:33:06 -0700 (PDT) Received: from p14s (S0106889e681aac74.cg.shawcable.net. [68.147.0.187]) by smtp.gmail.com with ESMTPSA id n6-20020a170902e54600b00186b280a441sm2784224plf.239.2022.11.04.08.33.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Nov 2022 08:33:06 -0700 (PDT) Date: Fri, 4 Nov 2022 09:33:03 -0600 From: Mathieu Poirier To: Peng Fan Cc: "Peng Fan (OSS)" , "andersson@kernel.org" , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" , "robh+dt@kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "kernel@pengutronix.de" , "festevam@gmail.com" , dl-linux-imx , "linux-remoteproc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" Subject: Re: [PATCH V2 0/2] remoteproc: imx: add start up delay Message-ID: <20221104153303.GB1873068@p14s> References: <20221102112451.128110-1-peng.fan@oss.nxp.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221104_083308_954649_6F81D669 X-CRM114-Status: GOOD ( 28.98 ) 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Nov 03, 2022 at 05:08:15AM +0000, Peng Fan wrote: > > Subject: Re: [PATCH V2 0/2] remoteproc: imx: add start up delay > > > > On Wed, 2 Nov 2022 at 05:23, Peng Fan (OSS) > > wrote: > > > > > > From: Peng Fan > > > > > > V2: > > > Rebased on linux-next > > > > > > V1: > > > > > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore > > > .kernel.org%2Flkml%2F20220609123500.3492475-1- > > peng.fan%40oss.nxp.com%2 > > > > > F&data=05%7C01%7Cpeng.fan%40nxp.com%7Cf14584bdef9349e744ca > > 08dabcf7 > > > > > e1be%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63803007007 > > 2451509%7 > > > > > CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ > > BTiI6Ik1 > > > > > haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ck73gkOPpNVT > > kcZL8olCZP8B > > > %2BrIpZHV48uZBl2R8HdM%3D&reserved=0 > > > > > > There is case that after remoteproc start remote processor[M4], the M4 > > > runs slow and before M4 finish its own rpmsg framework initialization, > > > linux sends out vring kick message, then M4 firmware drops the kick > > > message. Some NXP released Cortex-M[x] images has such limitation that > > > it requires linux sends out vring kick message after M4 firmware > > > finish its rpmsg framework initialization. > > > > > > The best case is to use a method to let M4 notify Linux that M4 has > > > finished initialization, but we could not patch released firmware, > > > then update driver to detect notification. > > > > > > So add delay before linux send out vring kick message. It is not good > > > to use a fixed time delay in driver, so I choose to get that from > > > device tree. > > > > > > > From where I stand this is a hack to hide the lack of motivation to enact the > > real solution that is outlined above. I also wonder how these problems > > were not caught during the testing phase. Either find a way to upgrade your > > firmware or keep this in your internal tree. > In the beginning, i.mx not migrated to use remoteproc, i.MX release only support > uboot kick Cortex-M core and use downstream imx_rpmsg driver to > communicate with remote core. There is no runtime stop/start. > > After migrated to remoteproc, we do see some issue, but old firmware was > there. You could also attach() to that remote processor, if the HW supports it. But my position remains the same - either find a way to work with this situation that is not a hack or keep this patch in your internal tree. > > Thanks, > Peng. > > > > > > Peng Fan (2): > > > dt-bindings: remoteproc: imx_rproc: add fsl,startup-delay-ms > > > remoteproc: imx_rproc: delay after kick remote processor > > > > > > .../devicetree/bindings/remoteproc/fsl,imx-rproc.yaml | 4 ++++ > > > drivers/remoteproc/imx_rproc.c | 9 +++++++++ > > > 2 files changed, 13 insertions(+) > > > > > > -- > > > 2.37.1 > > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel