From: sashiko-bot@kernel.org
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: conor+dt@kernel.org, wsa+renesas@sang-engineering.com,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: renesas: r8a78000-ironhide: enable to use SCMI
Date: Tue, 19 May 2026 08:17:17 +0000 [thread overview]
Message-ID: <20260519081718.4F790C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519074702.3308-6-wsa+renesas@sang-engineering.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch adds an include directive for `<dt-bindings/soc/renesas,r8a78000-mfis.h>`, but this header is not included in the commit and does not exist in the repository.
--
commit 12e4bb3b81767937e835c191fd20007f6b57db69
Author: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
arm64: renesas: r8a78000-ironhide: enable to use SCMI
This commit enables SCMI via MFIS-SCP and the STCM transport area to manage
clocks on the r8a78000-ironhide platform.
> diff --git a/arch/arm64/boot/dts/renesas/r8a78000-ironhide.dts b/arch/arm64/boot/dts/renesas/r8a78000-ironhide.dts
> index a721734fbd5d0..86bbe5fbb118a 100644
> --- a/arch/arm64/boot/dts/renesas/r8a78000-ironhide.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a78000-ironhide.dts
> @@ -6,6 +6,7 @@
> */
>
> /dts-v1/;
> +#include <dt-bindings/soc/renesas,r8a78000-mfis.h>
Is the dt-bindings/soc/renesas,r8a78000-mfis.h header missing from this
patch? The file doesn't seem to be included in the commit or currently
present in the repository, which causes a build failure during the C
preprocessing step.
[ ... ]
> @@ -20,6 +21,23 @@ chosen {
> stdout-path = "serial0:1843200n8";
> };
>
> + firmware {
> + scmi: scmi {
> + compatible = "arm,scmi";
> + mboxes = <&mfis_scp 2 MFIS_CHANNEL_TX>, <&mfis_scp 2 MFIS_CHANNEL_RX>;
Are MFIS_CHANNEL_TX and MFIS_CHANNEL_RX defined anywhere else? Without the
header file included above, these macros remain undefined.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519074702.3308-4-wsa+renesas@sang-engineering.com?part=2
next prev parent reply other threads:[~2026-05-19 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:47 [PATCH v2 0/2] arm64: renesas: r8a78000-ironhide: enable SCMI Wolfram Sang
2026-05-19 7:47 ` [PATCH v2 1/2] arm64: renesas: r8a78000: add MFIS, MFIS SCP and transport nodes Wolfram Sang
2026-05-19 8:05 ` sashiko-bot
2026-05-19 8:38 ` Wolfram Sang
2026-05-19 7:47 ` [PATCH v2 2/2] arm64: renesas: r8a78000-ironhide: enable to use SCMI Wolfram Sang
2026-05-19 8:17 ` sashiko-bot [this message]
2026-05-19 8:39 ` Wolfram Sang
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=20260519081718.4F790C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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