From: Liu Ying <victor.liu@nxp.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
jassisinghbrar@gmail.com, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V2 2/2] mailbox: imx: support RST channel
Date: Wed, 24 Aug 2022 17:36:01 +0800 [thread overview]
Message-ID: <4fdef6f22ba6fe734ee11601aacc884da2b9820b.camel@nxp.com> (raw)
In-Reply-To: <20220615130009.1457986-3-peng.fan@oss.nxp.com>
Hi,
On Wed, 2022-06-15 at 21:00 +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX generic MU supports MU-A/B reset feature.
>
> When stop/start remotecore, MU is not reset. So when Linux stop
> remotecore, the MU-B side BCR may contain valid configuration,
> because MU-B is not reset. So when linux start Mcore
> again and notify Mcore, Mcore is not ready to handle MU interrupt
> and cause issues. So need reset MU when stop Mcore.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
It looks like this patch causes i.MX8qxp MEK boot failure with v6.0-
rc1. After reverting commit 82ab513baed5895c8b0e991557a12fd38d5f25f0,
it boots ok.
There are a lot imx_mu and imx-scu error logs:
----------------------------8<------------------------------------
[ 1.166567] imx-scu system-controller: RPC send msg timeout
[ 1.171843] imx_scu_soc_id: get soc info failed, ret -110
[ 1.177221] imx-scu system-controller: failed to initialize SoC
info: -22
[ 1.184019] imx-scu system-controller: NXP i.MX SCU Initialized
[ 1.230605] imx-scu system-controller: RPC send msg timeout
[ 1.270559] imx-scu system-controller: RPC send msg timeout
[ 1.310561] imx-scu system-controller: RPC send msg timeout
[ 1.350560] imx-scu system-controller: RPC send msg timeout
[ 1.390560] imx-scu system-controller: RPC send msg timeout
[ 1.430561] imx-scu system-controller: RPC send msg timeout
[ 1.470559] imx-scu system-controller: RPC send msg timeout
[ 1.510559] imx-scu system-controller: RPC send msg timeout
[ 1.550559] imx-scu system-controller: RPC send msg timeout
[ 1.590559] imx-scu system-controller: RPC send msg timeout
[ 1.630561] imx-scu system-controller: RPC send msg timeout
[ 1.670558] imx-scu system-controller: RPC send msg timeout
[ 1.710559] imx-scu system-controller: RPC send msg timeout
[ 1.750558] imx-scu system-controller: RPC send msg timeout
[ 1.790559] imx-scu system-controller: RPC send msg timeout
[ 1.830562] imx-scu system-controller: RPC send msg timeout
[ 1.870559] imx-scu system-controller: RPC send msg timeout
[ 1.910559] imx-scu system-controller: RPC send msg timeout
[ 1.950561] imx-scu system-controller: RPC send msg timeout
[ 1.990592] imx-scu system-controller: RPC send msg timeout
[ 1.995838] imx_mu 5d1c0000.mailbox: Try increasing
MBOX_TX_QUEUE_LEN
[ 2.002262] imx-scu system-controller: RPC send msg failed: -105
[ 2.008260] imx_mu 5d1c0000.mailbox: Try increasing
MBOX_TX_QUEUE_LEN
[ 2.014682] imx-scu system-controller: RPC send msg failed: -105
[ 2.020681] imx_mu 5d1c0000.mailbox: Try increasing
MBOX_TX_QUEUE_LEN
[ 2.027103] imx-scu system-controller: RPC send msg failed: -105
[ 2.033105] imx_mu 5d1c0000.mailbox: Try increasing
MBOX_TX_QUEUE_LEN
[ 2.039526] imx-scu system-controller: RPC send msg failed: -105
[ 2.045526] imx_mu 5d1c0000.mailbox: Try increasing
MBOX_TX_QUEUE_LEN
[ 2.051949] imx-scu system-controller: RPC send msg failed: -105
----------------------------8<------------------------------------
Regards,
Liu Ying
next prev parent reply other threads:[~2022-08-24 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 13:00 [PATCH V2 0/2] mailbox: imx: support RST channel Peng Fan (OSS)
2022-06-15 13:00 ` [PATCH V2 1/2] dt-bindings: mailbox: imx-mu: add " Peng Fan (OSS)
2022-06-15 13:00 ` [PATCH V2 2/2] mailbox: imx: support " Peng Fan (OSS)
2022-08-24 9:36 ` Liu Ying [this message]
2022-08-29 0:41 ` Peng Fan
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=4fdef6f22ba6fe734ee11601aacc884da2b9820b.camel@nxp.com \
--to=victor.liu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@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=peng.fan@nxp.com \
--cc=peng.fan@oss.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).