From: Tinghan Shen <tinghan.shen@mediatek.com> To: Bjorn Andersson <andersson@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Tinghan Shen <tinghan.shen@mediatek.com> Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org>, <Project_Global_Chrome_Upstream_Group@mediatek.com> Subject: [PATCH v8 10/11] remoteproc: mediatek: Refine ipi handler error message Date: Fri, 3 Mar 2023 16:33:54 +0800 [thread overview] Message-ID: <20230303083355.3378-11-tinghan.shen@mediatek.com> (raw) In-Reply-To: <20230303083355.3378-1-tinghan.shen@mediatek.com> The error message doesn't accurately reflect the cause of the error. The error is due to a handler not being found, not an invalid IPI ID. Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> --- drivers/remoteproc/mtk_scp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c index 056a814486a3..6094f79e9565 100644 --- a/drivers/remoteproc/mtk_scp.c +++ b/drivers/remoteproc/mtk_scp.c @@ -113,7 +113,7 @@ static void scp_ipi_handler(struct mtk_scp *scp) scp_ipi_lock(scp, id); handler = ipi_desc[id].handler; if (!handler) { - dev_err(scp->dev, "No such ipi id = %d\n", id); + dev_err(scp->dev, "No handler for ipi id = %d\n", id); scp_ipi_unlock(scp, id); return; } -- 2.18.0
WARNING: multiple messages have this Message-ID (diff)
From: Tinghan Shen <tinghan.shen@mediatek.com> To: Bjorn Andersson <andersson@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Tinghan Shen <tinghan.shen@mediatek.com> Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mediatek@lists.infradead.org>, <Project_Global_Chrome_Upstream_Group@mediatek.com> Subject: [PATCH v8 10/11] remoteproc: mediatek: Refine ipi handler error message Date: Fri, 3 Mar 2023 16:33:54 +0800 [thread overview] Message-ID: <20230303083355.3378-11-tinghan.shen@mediatek.com> (raw) In-Reply-To: <20230303083355.3378-1-tinghan.shen@mediatek.com> The error message doesn't accurately reflect the cause of the error. The error is due to a handler not being found, not an invalid IPI ID. Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> --- drivers/remoteproc/mtk_scp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c index 056a814486a3..6094f79e9565 100644 --- a/drivers/remoteproc/mtk_scp.c +++ b/drivers/remoteproc/mtk_scp.c @@ -113,7 +113,7 @@ static void scp_ipi_handler(struct mtk_scp *scp) scp_ipi_lock(scp, id); handler = ipi_desc[id].handler; if (!handler) { - dev_err(scp->dev, "No such ipi id = %d\n", id); + dev_err(scp->dev, "No handler for ipi id = %d\n", id); scp_ipi_unlock(scp, id); return; } -- 2.18.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-03 8:34 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 8:33 [PATCH v8 00/11] Add support for MT8195 SCP 2nd core Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 01/11] dt-bindings: remoteproc: mediatek: Improve the rpmsg subnode definition Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 02/11] arm64: dts: mediatek: Update the node name of SCP rpmsg subnode Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-14 10:04 ` AngeloGioacchino Del Regno 2023-03-03 8:33 ` [PATCH v8 03/11] dt-bindings: remoteproc: mediatek: Support MT8195 dual-core SCP Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 04/11] remoteproc: mediatek: Add MT8195 SCP core 1 operations Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 05/11] remoteproc: mediatek: Extract remoteproc initialization flow Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-15 17:34 ` Mathieu Poirier 2023-03-15 17:34 ` Mathieu Poirier 2023-03-15 17:35 ` Mathieu Poirier 2023-03-15 17:35 ` Mathieu Poirier 2023-03-03 8:33 ` [PATCH v8 06/11] remoteproc: mediatek: Probe multi-core SCP Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-14 9:42 ` AngeloGioacchino Del Regno 2023-03-16 21:07 ` Mathieu Poirier 2023-03-16 21:07 ` Mathieu Poirier 2023-03-23 2:02 ` TingHan Shen (沈廷翰) 2023-03-23 2:02 ` TingHan Shen (沈廷翰) 2023-03-03 8:33 ` [PATCH v8 07/11] remoteproc: mediatek: Control SCP core 1 by rproc subdevice Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 08/11] remoteproc: mediatek: Setup MT8195 SCP core 1 SRAM offset Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 09/11] remoteproc: mediatek: Handle MT8195 SCP core 1 watchdog timeout Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen [this message] 2023-03-03 8:33 ` [PATCH v8 10/11] remoteproc: mediatek: Refine ipi handler error message Tinghan Shen 2023-03-03 8:33 ` [PATCH v8 11/11] arm64: dts: mediatek: mt8195: Add SCP 2nd core Tinghan Shen 2023-03-03 8:33 ` Tinghan Shen
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=20230303083355.3378-11-tinghan.shen@mediatek.com \ --to=tinghan.shen@mediatek.com \ --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \ --cc=andersson@kernel.org \ --cc=angelogioacchino.delregno@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=mathieu.poirier@linaro.org \ --cc=matthias.bgg@gmail.com \ --cc=robh+dt@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.