public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: u-boot@lists.denx.de,
	Aleksandar Gerasimovski
	<aleksandar.gerasimovski@hitachi-powergrids.com>,
	Andreas Biessmann <andreas@biessmann.org>,
	Eugen Hristev <eugen.hristev@microchip.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Peng Fan <peng.fan@nxp.com>,
	Siew Chin Lim <elly.siew.chin.lim@intel.com>,
	Valentin Longchamp <valentin.longchamp@hitachi-powergrids.com>,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [RFC][PATCH] mtd: spi: Set CONFIG_SF_DEFAULT_MODE default to 0
Date: Tue, 28 Sep 2021 14:45:03 -0400	[thread overview]
Message-ID: <20210928184503.GU31748@bill-the-cat> (raw)
In-Reply-To: <20210914182824.139667-1-marex@denx.de>

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On Tue, Sep 14, 2021 at 08:28:24PM +0200, Marek Vasut wrote:

> Before e2e95e5e254 ("spi: Update speed/mode on change") most systems
> silently defaulted to SF bus mode 0. Now the mode is always updated,
> which causes breakage. It seems most SF which are used as boot media
> operate in bus mode 0, so switch that as the default.
> 
> This should fix booting at least on Altera SoCFPGA, ST STM32, Xilinx
> ZynqMP, NXP iMX and Rockchip SoCs, which recently ran into trouble
> with mode 3. Marvell Kirkwood and Xilinx microblaze need to be checked
> as those might need mode 3.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachi-powergrids.com>
> Cc: Andreas Biessmann <andreas@biessmann.org>
> Cc: Eugen Hristev <eugen.hristev@microchip.com>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: Patrice Chotard <patrice.chotard@foss.st.com>
> Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Siew Chin Lim <elly.siew.chin.lim@intel.com>
> Cc: Tom Rini <trini@konsulko.com>
> Cc: Valentin Longchamp <valentin.longchamp@hitachi-powergrids.com>
> Cc: Vignesh Raghavendra <vigneshr@ti.com>

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2021-09-28 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 18:28 [RFC][PATCH] mtd: spi: Set CONFIG_SF_DEFAULT_MODE default to 0 Marek Vasut
2021-09-14 19:19 ` Tom Rini
2021-09-14 20:10   ` Marek Vasut
2021-09-14 20:45     ` Tom Rini
2021-09-14 21:30       ` Marek Vasut
2021-09-14 21:44         ` Tom Rini
2021-09-15 17:55           ` Tom Rini
2021-09-15 18:52             ` Marek Vasut
2021-09-28 18:45 ` Tom Rini [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=20210928184503.GU31748@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=aleksandar.gerasimovski@hitachi-powergrids.com \
    --cc=andreas@biessmann.org \
    --cc=elly.siew.chin.lim@intel.com \
    --cc=eugen.hristev@microchip.com \
    --cc=marex@denx.de \
    --cc=michal.simek@xilinx.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=peng.fan@nxp.com \
    --cc=u-boot@lists.denx.de \
    --cc=valentin.longchamp@hitachi-powergrids.com \
    --cc=vigneshr@ti.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