From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com> To: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, linux-remoteproc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com> Subject: [PATCH 0/2] remoteproc: imx: add start up delay Date: Thu, 9 Jun 2022 20:34:58 +0800 [thread overview] Message-ID: <20220609123500.3492475-1-peng.fan@oss.nxp.com> (raw) From: Peng Fan <peng.fan@nxp.com> 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. 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.25.1
WARNING: multiple messages have this Message-ID (diff)
From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com> To: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, linux-remoteproc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com> Subject: [PATCH 0/2] remoteproc: imx: add start up delay Date: Thu, 9 Jun 2022 20:34:58 +0800 [thread overview] Message-ID: <20220609123500.3492475-1-peng.fan@oss.nxp.com> (raw) From: Peng Fan <peng.fan@nxp.com> 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. 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.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-06-09 12:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 12:34 Peng Fan (OSS) [this message] 2022-06-09 12:34 ` [PATCH 0/2] remoteproc: imx: add start up delay Peng Fan (OSS) 2022-06-09 12:34 ` [PATCH 1/2] dt-bindings: remoteproc: imx_rproc: add fsl,startup-delay-ms Peng Fan (OSS) 2022-06-09 12:34 ` Peng Fan (OSS) 2022-06-09 15:23 ` Rob Herring 2022-06-09 15:23 ` Rob Herring 2022-06-10 2:10 ` Peng Fan 2022-06-10 2:10 ` Peng Fan 2022-06-09 12:35 ` [PATCH 2/2] remoteproc: imx_rproc: delay after kick remote processor Peng Fan (OSS) 2022-06-09 12:35 ` Peng Fan (OSS)
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=20220609123500.3492475-1-peng.fan@oss.nxp.com \ --to=peng.fan@oss.nxp.com \ --cc=bjorn.andersson@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=mathieu.poirier@linaro.org \ --cc=peng.fan@nxp.com \ --cc=robh+dt@kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=shawnguo@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.