From: Pali Rohár Date: Thu, 22 Sep 2022 11:43:46 +0000 (+0200) Subject: arm: mvebu: turris_omnia: Specify VHV gpio for eFUSE programming X-Git-Tag: v2023.07~311^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3bb0458fa0ef127718ed1c47c33279f9ef03238d;p=platform%2Fkernel%2Fu-boot.git arm: mvebu: turris_omnia: Specify VHV gpio for eFUSE programming VHV gpio is connected to MCU and only on updated board design. Without it eFUSE programming does not work. Omnia MCU driver exports this GPIO to U-Boot under name mcu_56 and only when it is supported by MCU. So U-Boot fuse command refuse eFUSE programming on older board design when VHV gpio is not available. We tested that Armada 385 without connected VHV gpio can do eFUSE programming but only for some bits and only sometimes - it is unstable. And better to be disabled on older board design without VHV gpio support. Signed-off-by: Pali Rohár --- diff --git a/configs/turris_omnia_defconfig b/configs/turris_omnia_defconfig index 6698f23..639c68c 100644 --- a/configs/turris_omnia_defconfig +++ b/configs/turris_omnia_defconfig @@ -10,6 +10,8 @@ CONFIG_NR_DRAM_BANKS=2 CONFIG_TARGET_TURRIS_OMNIA=y CONFIG_DDR_RESET_ON_TRAINING_FAILURE=y CONFIG_MVEBU_EFUSE=y +CONFIG_MVEBU_EFUSE_VHV_GPIO="mcu_56" +CONFIG_MVEBU_EFUSE_VHV_GPIO_ACTIVE_LOW=y CONFIG_ENV_SIZE=0x10000 CONFIG_ENV_OFFSET=0xF0000 CONFIG_ENV_SECT_SIZE=0x10000