mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: Julian Braha <julianbraha@gmail.com>, jenswi@kernel.org
Cc: sumit.garg@kernel.org, arnd@arndb.de, geert+renesas@glider.be,
	amirreza.zarrabi@oss.qualcomm.org,
	op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
	quic_eberman@quicinc.com, andersson@kernel.org, brgl@kernel.org,
	harshal.dev@oss.qualcomm.com
Subject: Re: [PATCH v2] tee: remove TZMEM_MODE_GENERIC
Date: Tue, 4 Aug 2026 14:29:52 +1000	[thread overview]
Message-ID: <63cfff1e-359b-4db9-97a8-43d97abb0369@oss.qualcomm.com> (raw)
In-Reply-To: <20260729203845.387239-1-julianbraha@gmail.com>

Hi Julian,

With this change, is QCOM_TZMEM_MODE_SHMBRIDGE still needed?

I think QCOM_TZMEM_MODE_SHMBRIDGE can therefore be removed entirely,
along with the conditional declarations and stubs in qcom_tzmem.h and
the corresponding select in the qcomtee Kconfig.

Regards,
Amir

On 7/30/2026 6:38 AM, Julian Braha wrote:
> 'select' does not work on config options in a 'choice', so currently it is
> possible to enable QCOMTEE without QCOM_TZMEM_MODE_SHMBRIDGE, even though
> this is needed at runtime.
> 
> There are no users of the generic allocator option,
> QCOM_TZMEM_MODE_GENERIC, so let's remove it. Then, we can remove the
> containing choice..endchoice, which allows the 'select' to work as
> intended.
> 
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
> Changes since v1:
> - remove TZMEM_MODE_GENERIC instead of removing the dead select
> 
> Link:
> https://lore.kernel.org/all/20260715092539.18384-1-julianbraha@gmail.com/
> ---
>  drivers/firmware/qcom/Kconfig      | 26 +++++---------------------
>  drivers/firmware/qcom/qcom_tzmem.c | 21 ---------------------
>  2 files changed, 5 insertions(+), 42 deletions(-)
> 
> diff --git a/drivers/firmware/qcom/Kconfig b/drivers/firmware/qcom/Kconfig
> index c7f8413ab996..d99e09c5fa18 100644
> --- a/drivers/firmware/qcom/Kconfig
> +++ b/drivers/firmware/qcom/Kconfig
> @@ -34,33 +34,17 @@ config QCOM_TZMEM
>  	tristate
>  	select GENERIC_ALLOCATOR
>  
> -choice
> -	prompt "TrustZone interface memory allocator mode"
> -	depends on QCOM_TZMEM
> -	default QCOM_TZMEM_MODE_GENERIC
> -	help
> -	  Selects the mode of the memory allocator providing memory buffers of
> -	  suitable format for sharing with the TrustZone. If in doubt, select
> -	  'Generic'.
> -
> -config QCOM_TZMEM_MODE_GENERIC
> -	bool "Generic"
> -	help
> -	  Use the generic allocator mode. The memory is page-aligned, non-cachable
> -	  and physically contiguous.
> -
>  config QCOM_TZMEM_MODE_SHMBRIDGE
> -	bool "SHM Bridge"
> +	bool "TrustZone interface memory allocator: SHM Bridge"
> +	depends on QCOM_TZMEM
>  	help
> -	  Use Qualcomm Shared Memory Bridge. The memory has the same alignment as
> -	  in the 'Generic' allocator but is also explicitly marked as an SHM Bridge
> -	  buffer.
> +	  Use Qualcomm Shared Memory Bridge as memory allocator. The memory has the
> +	  same alignment as in the 'Generic' allocator but is also explicitly marked
> +	  as an SHM Bridge buffer.
>  
>  	  With this selected, all buffers passed to the TrustZone must be allocated
>  	  using the TZMem allocator or else the TrustZone will refuse to use them.
>  
> -endchoice
> -
>  config QCOM_QSEECOM
>  	bool "Qualcomm QSEECOM interface driver"
>  	depends on QCOM_SCM=y
> diff --git a/drivers/firmware/qcom/qcom_tzmem.c b/drivers/firmware/qcom/qcom_tzmem.c
> index 0635cbeacfc8..5b3e5a3ad1ae 100644
> --- a/drivers/firmware/qcom/qcom_tzmem.c
> +++ b/drivers/firmware/qcom/qcom_tzmem.c
> @@ -49,25 +49,6 @@ static struct device *qcom_tzmem_dev;
>  static RADIX_TREE(qcom_tzmem_chunks, GFP_ATOMIC);
>  static DEFINE_SPINLOCK(qcom_tzmem_chunks_lock);
>  
> -#if IS_ENABLED(CONFIG_QCOM_TZMEM_MODE_GENERIC)
> -
> -static int qcom_tzmem_init(void)
> -{
> -	return 0;
> -}
> -
> -static int qcom_tzmem_init_area(struct qcom_tzmem_area *area)
> -{
> -	return 0;
> -}
> -
> -static void qcom_tzmem_cleanup_area(struct qcom_tzmem_area *area)
> -{
> -
> -}
> -
> -#elif IS_ENABLED(CONFIG_QCOM_TZMEM_MODE_SHMBRIDGE)
> -
>  #include <linux/firmware/qcom/qcom_scm.h>
>  #include <linux/of.h>
>  
> @@ -189,8 +170,6 @@ static void qcom_tzmem_cleanup_area(struct qcom_tzmem_area *area)
>  	kfree(handle);
>  }
>  
> -#endif /* CONFIG_QCOM_TZMEM_MODE_SHMBRIDGE */
> -
>  static int qcom_tzmem_pool_add_memory(struct qcom_tzmem_pool *pool,
>  				      size_t size, gfp_t gfp)
>  {


  parent reply	other threads:[~2026-08-04  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 20:38 Julian Braha
2026-07-29 20:44 ` Arnd Bergmann
2026-08-04  4:29 ` Amirreza Zarrabi [this message]
2026-08-04  7:40   ` Arnd Bergmann

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=63cfff1e-359b-4db9-97a8-43d97abb0369@oss.qualcomm.com \
    --to=amirreza.zarrabi@oss.qualcomm.com \
    --cc=amirreza.zarrabi@oss.qualcomm.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=brgl@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=harshal.dev@oss.qualcomm.com \
    --cc=jenswi@kernel.org \
    --cc=julianbraha@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=quic_eberman@quicinc.com \
    --cc=sumit.garg@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®