From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Arnd Bergmann <arnd@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Etienne Carriere <etienne.carriere@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmem: stm32: fix OPTEE dependency
Date: Wed, 1 Feb 2023 13:49:11 +0100 [thread overview]
Message-ID: <12172517-87d4-ad2c-536d-68b9541e9a6b@foss.st.com> (raw)
In-Reply-To: <20230127094200.2451839-1-arnd@kernel.org>
Hi
On 1/27/23 10:41, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The stm32 nvmem driver fails to link as built-in when OPTEE
> is a loadable module:
>
> aarch64-linux-ld: drivers/nvmem/stm32-bsec-optee-ta.o: in function `stm32_bsec:
> stm32-bsec-optee-ta.c:(.text+0xc8): undefined reference to `tee_client_open_session'
> aarch64-linux-ld: drivers/nvmem/stm32-bsec-optee-ta.o: in function `stm32_bsec:
> stm32-bsec-optee-ta.c:(.text+0x1fc): undefined reference to `tee_client_open_context'
>
> Change the CONFIG_NVMEM_STM32_ROMEM definition so it can only
> be built-in if OPTEE is either built-in or disabled, and
> make NVMEM_STM32_BSEC_OPTEE_TA a hidden symbol instead.
>
> Fixes: acdf68bdf2d4 ("nvmem: stm32: add OP-TEE support for STM32MP13x")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/nvmem/Kconfig | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index ed8ef7460be2..ae2c5257ed97 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -295,8 +295,7 @@ config NVMEM_SPRD_EFUSE
> will be called nvmem-sprd-efuse.
>
> config NVMEM_STM32_BSEC_OPTEE_TA
> - bool "STM32MP BSEC OP-TEE TA support for nvmem-stm32-romem driver"
> - depends on OPTEE
> + def_bool NVMEM_STM32_ROMEM && OPTEE
> help
> Say y here to enable the accesses to STM32MP SoC OTPs by the OP-TEE
> trusted application STM32MP BSEC.
> @@ -307,7 +306,7 @@ config NVMEM_STM32_BSEC_OPTEE_TA
> config NVMEM_STM32_ROMEM
> tristate "STMicroelectronics STM32 factory-programmed memory support"
> depends on ARCH_STM32 || COMPILE_TEST
> - imply NVMEM_STM32_BSEC_OPTEE_TA
> + depends on OPTEE || !OPTEE
> help
> Say y here to enable read-only access for STMicroelectronics STM32
> factory-programmed memory area.
Thanks for the fix,
I test several case....
at least the logical configurations:
OP-TEE=n and NVMEM_STM32_ROMEM=m
OP-TEE=y and NVMEM_STM32_ROMEM=m
OP-TEE=n and NVMEM_STM32_ROMEM=y
OP-TEE=y and NVMEM_STM32_ROMEM=y
but I miss this case
OP-TEE=m and NVMEM_STM32_ROMEM=y
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Thanks
Patrick
prev parent reply other threads:[~2023-02-01 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:41 Arnd Bergmann
2023-01-27 10:43 ` Srinivas Kandagatla
2023-02-01 12:49 ` Patrick DELAUNAY [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=12172517-87d4-ad2c-536d-68b9541e9a6b@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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®