public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v4 05/11] initramfs-tee-{ftpm,supplicant}-hook: Move sync loop to ftpm-hook
Date: Mon, 31 Jul 2023 14:17:23 +0200	[thread overview]
Message-ID: <20230731121729.16972-6-ubely@ilbers.de> (raw)
In-Reply-To: <20230731121729.16972-1-ubely@ilbers.de>

From: Jan Kiszka <jan.kiszka@siemens.com>

There is no FTPM_DEV defined in tee-supplicant.script, and it also makes
no sense to wait for an unrelated fTPM device in the tee-supplicant
starter hook. That is better done in tee-ftpm.script.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 .../initramfs-tee-ftpm-hook/files/tee-ftpm.script        | 9 +++++++++
 .../files/tee-supplicant.script                          | 8 --------
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/meta/recipes-initramfs/initramfs-tee-ftpm-hook/files/tee-ftpm.script b/meta/recipes-initramfs/initramfs-tee-ftpm-hook/files/tee-ftpm.script
index ce321a09..6e12e6df 100644
--- a/meta/recipes-initramfs/initramfs-tee-ftpm-hook/files/tee-ftpm.script
+++ b/meta/recipes-initramfs/initramfs-tee-ftpm-hook/files/tee-ftpm.script
@@ -21,6 +21,15 @@ esac
 . /scripts/functions
 
 FTPM_DEV=/dev/tpmrm0
+
+# The tee-supplicant would take some time to be discovered, 10 seconds should be
+# enough
+wait_sec=10
+until test $wait_sec -eq 0 || test -c "${FTPM_DEV}" ; do
+	wait_sec=$((wait_sec-1))
+	sleep 1
+done
+
 if ! test -c "${FTPM_DEV}"; then
     panic "Can't discover the fTPM device ${FTPM_DEV}!"
 fi
diff --git a/meta/recipes-initramfs/initramfs-tee-supplicant-hook/files/tee-supplicant.script b/meta/recipes-initramfs/initramfs-tee-supplicant-hook/files/tee-supplicant.script
index bb6dcc16..76efc1ad 100644
--- a/meta/recipes-initramfs/initramfs-tee-supplicant-hook/files/tee-supplicant.script
+++ b/meta/recipes-initramfs/initramfs-tee-supplicant-hook/files/tee-supplicant.script
@@ -22,12 +22,4 @@ esac
 
 /usr/sbin/tee-supplicant -d
 
-# The tee-supplicant would take some time to be discovered, 10 seconds should be
-# enough
-wait_sec=10
-until test $wait_sec -eq 0 || test -c "${FTPM_DEV}" ; do
-	wait_sec=$((wait_sec-1))
-	sleep 1
-done
-
 /usr/bin/pgrep tee-supplicant > /dev/null || panic "Can't start the tee-supplicant daemon!"
-- 
2.20.1


  parent reply	other threads:[~2023-07-31 12:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 12:17 [PATCH v4 00/11] Fixes, cleanups and updates for OP-TEE and TAs Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 01/11] optee-client: Add missing runtime dependency Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 02/11] optee-client: Unbind ftpm, rather than remove its driver Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 03/11] optee-examples-stm32mp15x: Fix parsing error for non-stm32mp15x machines Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 04/11] linux-mainline: Add fTPM support Uladzimir Bely
2023-07-31 12:17 ` Uladzimir Bely [this message]
2023-07-31 12:17 ` [PATCH v4 06/11] initramfs-tee-supplicant-hook: Account for modular optee Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 07/11] initramfs-tee-ftpm-hook: Lift timeout to 30 s Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 08/11] Drop stm32mp15x-initramfs in favor of image enabling Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 09/11] optee-ftpm-stm32mp15x: Recipe cleanups Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 10/11] optee-ftpm-stm32mp15x: Update WolfSSL to 5.6.3 Uladzimir Bely
2023-07-31 12:17 ` [PATCH v4 11/11] optee-ftpm-stm32mp15x: Add patch to fix parallel build issues Uladzimir Bely
2023-08-02  4:11 ` [PATCH v4 00/11] Fixes, cleanups and updates for OP-TEE and TAs Uladzimir Bely

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=20230731121729.16972-6-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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