From: Marek Szyprowski <m.szyprowski@samsung.com>
Date: Wed, 14 Aug 2024 07:42:48 +0000 (+0200)
Subject: scripts: sd_fusing: Fix re-reading partition table again
X-Git-Tag: accepted/tizen/unified/20240819.150128~2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fchanges%2F73%2F316173%2F1;p=platform%2Fkernel%2Fu-boot.git

scripts: sd_fusing: Fix re-reading partition table again

Actually it turned out that any direct write access to the block device
might trigger kernel and udev to re-read partition table, so call
'udevadm settle' always after writing boot image directly to block
device.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I3caf4ea6d3b89cb333e38f7b30dcf44685d73335
---

diff --git a/scripts/tizen/sd_fusing.py b/scripts/tizen/sd_fusing.py
index 22e4816e6d..917e381a8b 100755
--- a/scripts/tizen/sd_fusing.py
+++ b/scripts/tizen/sd_fusing.py
@@ -1101,9 +1101,8 @@ def do_fuse_raw(f, name, target, sector):
     proc_dd.communicate()
     logging.info("Done")
 
-    # writing to sector zero might trigger kernel/udev to re-read partition table
-    if sector == 0:
-        wait_for_udev()
+    # direct writing to block device might trigger kernel/udev to re-read partition table
+    wait_for_udev()
 
     #TODO: verification