public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>, u-boot@lists.denx.de
Cc: trini@konsulko.com, venkatesh.abbarapu@amd.com, git@amd.com
Subject: Re: [PATCH v2] configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR
Date: Wed, 10 Apr 2024 08:12:19 +0200	[thread overview]
Message-ID: <164ee02a-101a-438b-bd25-4ca8acbec6ce@amd.com> (raw)
In-Reply-To: <20240409094826.4131643-1-tejas.arvind.bhumkar@amd.com>



On 4/9/24 11:48, Tejas Bhumkar wrote:
> The Kria board features a recovery application that activates
> when the FW_EN button is pressed.
> Upon power-up flash operates in 3B mode, However, the recovery
> application changes it back to 4B mode.
> Currently, after a reset, u-boot activates CONFIG_SPI_FLASH_BAR
> and assumes the flash is in 3B mode. However, there's no code
> or reset lines connected to the flash that could return it to
> 3B mode. To resolve this issue, changes were made to disable
> CONFIG_SPI_FLASH_BAR, which activates 4-byte opcodes.
> 
> Signed-off-by: Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>
> ---
> Changes in v2: Updated commit message.
> 
>   configs/xilinx_zynqmp_kria_defconfig | 1 -
>   1 file changed, 1 deletion(-)
> 
> diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig
> index 7cb8b62d32..7af8b27be9 100644
> --- a/configs/xilinx_zynqmp_kria_defconfig
> +++ b/configs/xilinx_zynqmp_kria_defconfig
> @@ -155,7 +155,6 @@ CONFIG_MMC_HS200_SUPPORT=y
>   CONFIG_MMC_SDHCI=y
>   CONFIG_MMC_SDHCI_ZYNQ=y
>   CONFIG_DM_MTD=y
> -CONFIG_SPI_FLASH_BAR=y
>   CONFIG_SPI_FLASH_STMICRO=y
>   # CONFIG_SPI_FLASH_USE_4K_SECTORS is not set
>   CONFIG_SPI_FLASH_MTD=y

Applied.
M

      reply	other threads:[~2024-04-10  6:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  9:48 [PATCH v2] configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR Tejas Bhumkar
2024-04-10  6:12 ` Michal Simek [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=164ee02a-101a-438b-bd25-4ca8acbec6ce@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@amd.com \
    --cc=tejas.arvind.bhumkar@amd.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=venkatesh.abbarapu@amd.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