Re: [PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

2024-03-25 Thread Michal Simek
On 3/20/24 12:18, Michal Simek wrote: if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot mode which is 0. When 0 was used origin(HW) boot mode was used instead. That's why directly fill reg variable with requested boot mode and don't let code to read value back. "else"

Re: [PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

2024-03-22 Thread Sean Anderson
On 3/22/24 07:53, Michal Simek wrote: > > > On 3/21/24 17:20, Sean Anderson wrote: >> On 3/20/24 07:18, Michal Simek wrote: >>> if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot >>> mode which is 0. When 0 was used origin(HW) boot mode was used instead. >>> That's why

Re: [PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

2024-03-22 Thread Michal Simek
On 3/21/24 17:20, Sean Anderson wrote: On 3/20/24 07:18, Michal Simek wrote: if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot mode which is 0. When 0 was used origin(HW) boot mode was used instead. That's why directly fill reg variable with requested boot mode and

Re: [PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

2024-03-21 Thread Sean Anderson
On 3/20/24 07:18, Michal Simek wrote: > if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot > mode which is 0. When 0 was used origin(HW) boot mode was used instead. > That's why directly fill reg variable with requested boot mode and don't > let code to read value back.

[PATCH] arm64: zynqmp: Also support JTAG as alternative boot mode

2024-03-20 Thread Michal Simek
if (reg >> BOOT_MODE_ALT_SHIFT) condition rules out alternative jtag boot mode which is 0. When 0 was used origin(HW) boot mode was used instead. That's why directly fill reg variable with requested boot mode and don't let code to read value back. "else" part of code remain unchanged.