From: Christian Marangi <ansuelsmth@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] nvmem: airoha: add ARM64 dependency
Date: Fri, 12 Jun 2026 10:13:49 +0200 [thread overview]
Message-ID: <6a2bbfc1.cf2df9a4.29e9ad.911b@mx.google.com> (raw)
In-Reply-To: <20260611125822.3386722-1-arnd@kernel.org>
On Thu, Jun 11, 2026 at 02:58:00PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The driver already depends on HAVE_ARM_SMCCC and ARCH_AIROHA, but both
> are available for 32-bit and 64-bit targets. However, the smccc invocation
> fails on thumb2 builds with clang:
>
> drivers/nvmem/airoha-smc-efuses.c:38:2: error: write to reserved register 'R7'
> 38 | arm_smccc_1_1_invoke(AIROHA_SMC_EFUSE_FID,
> | ^
> note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
> arch/arm/include/asm/opcodes.h:215:2: note: expanded from macro '__inst_arm_thumb32'
> 215 | __inst_thumb32(thumb_opcode)
> | ^
>
> Since the driver is only used on the 64-bit an7581 soc, avoid this
> problem with a stricter dependency.
>
> Fixes: 25e001fcc1e6 ("nvmem: airoha: Add support for SMC eFUSE")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Christian Marangi <ansuelsmth@gmail.com>
--
Ansuel
prev parent reply other threads:[~2026-06-12 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 12:58 [PATCH] nvmem: airoha: add ARM64 dependency Arnd Bergmann
2026-06-12 8:13 ` Christian Marangi [this message]
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=6a2bbfc1.cf2df9a4.29e9ad.911b@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=srini@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