Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dimi Tomov <dimi@tpm.dev>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v5, 1/1] package/wolftpm: Add config options for TPM 2.0 extra capabilities
Date: Sat, 18 Jun 2022 07:57:48 +0300	[thread overview]
Message-ID: <12968eeabd209ead5eec34e099c93ff4@tpm.dev> (raw)
In-Reply-To: <20220618044659.4800-1-dimi@tpm.dev>

Hi Thomas,

This patch is ready for review. Thanks to Fabrice for the good feedback.

ps: I am unable to enter patchwork after password reset, so v4 still 
holds new status.

Regards,
Dimi
-- 
Founder of TPM.dev

On 2022-06-18 07:46 AM, Dimi Tomov wrote:
> From: Dimitar Tomov <dimi@tpm.dev>
> 
> Some TPM 2.0 chips offer extra capabilities. This patch adds additional
> configuration options to the wolftpm package, so such capabilities can
> be available to the user. For example, the STMicroelectronics ST33 and
> Nuvoton NPCT750 both offer secure GPIO. Due to chip differences, 
> wolfTPM
> requires explicit configuration options to enable the extra 
> capabilities.
> 
> Signed-off-by: Dimitar Tomov <dimi@tpm.dev>
> ---
> Changes v4 -> v5:
> - Style: Fix some lines in Config.in that were longer than 72 
> characters
> Changes v3 -> v4:
> - Fix commit message. For some reason the update was not included in 
> patch v3.
> Changes v2 -> v3:
> - Better commit message
> Changes v1 -> v2:
> - Remove a not needed package description change
> ---
>  package/wolftpm/Config.in  | 14 ++++++++++++++
>  package/wolftpm/wolftpm.mk | 12 ++++++++++++
>  2 files changed, 26 insertions(+)
> 
> diff --git a/package/wolftpm/Config.in b/package/wolftpm/Config.in
> index 0b964c3d7e..52a9005d66 100644
> --- a/package/wolftpm/Config.in
> +++ b/package/wolftpm/Config.in
> @@ -23,6 +23,20 @@ config BR2_PACKAGE_WOLFTPM_WOLFCRYPT
>  	  encryption. Disabling this option is not recommended as it
>  	  could create a security breach in most environments.
> 
> +config BR2_PACKAGE_WOLFTPM_ST33
> +	bool "st33"
> +	default n
> +	help
> +	  Enable support of TPM 2.0 extra functionality offered by the
> +	  STMicroelectronics ST33 chip.
> +
> +config BR2_PACKAGE_WOLFTPM_NUVOTON
> +	bool "npct750"
> +	default n
> +	help
> +	  Enable support of TPM 2.0 extra functionality offered by the
> +	  Nuvoton NPCT750 chip.
> +
>  comment "wolfCrypt hooks need a toolchain w/ threads, dynamic library"
>  	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> 
> diff --git a/package/wolftpm/wolftpm.mk b/package/wolftpm/wolftpm.mk
> index a4a9edce85..d0423cd06b 100644
> --- a/package/wolftpm/wolftpm.mk
> +++ b/package/wolftpm/wolftpm.mk
> @@ -35,4 +35,16 @@ else
>  WOLFTPM_CONF_OPTS += --disable-wolfcrypt
>  endif
> 
> +ifeq ($(BR2_PACKAGE_WOLFTPM_ST33),y)
> +WOLFTPM_CONF_OPTS += --enable-st33
> +else
> +WOLFTPM_CONF_OPTS += --disable-st33
> +endif
> +
> +ifeq ($(BR2_PACKAGE_WOLFTPM_NPCT750),y)
> +WOLFTPM_CONF_OPTS += --enable-nuvoton
> +else
> +WOLFTPM_CONF_OPTS += --disable-nuvoton
> +endif
> +
>  $(eval $(autotools-package))
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-06-18  4:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  7:30 [Buildroot] [PATCH 1/1] package/wolftpm: Add TPM 2.0 extra options and fix one bad typo Dimi Tomov
2022-06-15  7:36 ` [Buildroot] [PATCH v2 " Dimi Tomov
2022-06-15  7:45   ` [Buildroot] [PATCH v3 1/1] package/wolftpm: Add config options for TPM 2.0 extra capabilities Dimi Tomov
2022-06-15  7:50     ` [Buildroot] [PATCH v4 " Dimi Tomov
2022-06-15  7:52       ` Dimi Tomov
2022-06-15  8:34         ` Fabrice Fontaine
2022-06-15 10:56           ` Dimi Tomov
2022-06-15 11:51             ` Fabrice Fontaine
2022-06-18  4:46       ` [Buildroot] [PATCH v5, " Dimi Tomov
2022-06-18  4:57         ` Dimi Tomov [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=12968eeabd209ead5eec34e099c93ff4@tpm.dev \
    --to=dimi@tpm.dev \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.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