From: Oliver Graute <oliver.graute@kococonnector.com>
To: shawnguo@kernel.org
Cc: oliver.graute@kococonnector.com, oliver.graute@gmail.com,
Anson.Huang@nxp.com, aisheng.dong@nxp.com,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1] linux: imx: imx-scu: increased scu message timeout
Date: Mon, 29 Aug 2022 15:58:04 +0200 [thread overview]
Message-ID: <20220829135804.12632-1-oliver.graute@kococonnector.com> (raw)
With MAX_RX_TIMEOUT = 30 ms we observed some wired behavior of
communication to scfw. After increasing the scu message timeout to
arbitrarily MAX_RX_TIMEOUT = 1s these problemes are gone.
a35_clk: failed to get clock rate -22
gpt0_clk: failed to attached the power domain -2
imx-scu scu: RPC send msg timeout
gpt2: failed to power up resource 209 ret -110
imx-scu-clk: probe of gpt2_clk failed with error -110
imx-scu scu: RPC send msg timeout
lpspi0: failed to power off resource 53 ret -110
imx-scu scu: RPC send msg timeout
enet1: failed to power up resource 252 ret -110
imx-scu-clk: probe of enet1_clk failed with error -110
mipi_csi0_core_clk: failed to attached the power domain -2
mipi_csi0_esc_clk: failed to attached the power domain -2
mipi_csi0_i2c0_clk: failed to attached the power domain -2
mipi_csi0_pwm0_clk: failed to attached the power domain -2
lvds0_i2c0_clk: failed to attached the power domain -2
lvds0_i2c1_clk: failed to attached the power domain -2
lvds0_i2c1_clk: failed to get clock rate -22
lvds1_i2c1_clk: failed to attached the power domain -2
lvds1_i2c1_clk: failed to get clock rate -22
Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
---
drivers/firmware/imx/imx-scu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/imx/imx-scu.c b/drivers/firmware/imx/imx-scu.c
index dca79caccd01..cef2bcea61e7 100644
--- a/drivers/firmware/imx/imx-scu.c
+++ b/drivers/firmware/imx/imx-scu.c
@@ -20,7 +20,7 @@
#include <linux/platform_device.h>
#define SCU_MU_CHAN_NUM 8
-#define MAX_RX_TIMEOUT (msecs_to_jiffies(30))
+#define MAX_RX_TIMEOUT (msecs_to_jiffies(1000))
struct imx_sc_chan {
struct imx_sc_ipc *sc_ipc;
--
2.26.0
reply other threads:[~2022-08-29 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220829135804.12632-1-oliver.graute@kococonnector.com \
--to=oliver.graute@kococonnector.com \
--cc=Anson.Huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.graute@gmail.com \
--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
all inboxes | Powered by JetHome®