public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/5] cmd: sf Drop reassignment of new into flash
Date: Thu, 14 May 2020 17:41:42 +0530	[thread overview]
Message-ID: <20200514121145.28737-3-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20200514121145.28737-1-jagan@amarulasolutions.com>

The new pointer points to flash found and that would
assign it to global 'flash' pointer for further flash
operations and also keep track of old flash pointer.

This would happen if the probe is successful or even
failed, but current code assigning new into flash before
and after checking the new.

So, drop the assignment after new checks so flash always
latest new pointer even if probe failed or succeed.

Cc: Simon Glass <sjg@chromium.org>
Cc: Vignesh R <vigneshr@ti.com>
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
 cmd/sf.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/cmd/sf.c b/cmd/sf.c
index e993b3e5ad..302201c2b0 100644
--- a/cmd/sf.c
+++ b/cmd/sf.c
@@ -141,13 +141,10 @@ static int do_spi_flash_probe(int argc, char * const argv[])
 
 	new = spi_flash_probe(bus, cs, speed, mode);
 	flash = new;
-
 	if (!new) {
 		printf("Failed to initialize SPI flash at %u:%u\n", bus, cs);
 		return 1;
 	}
-
-	flash = new;
 #endif
 
 	return 0;
-- 
2.20.1

  parent reply	other threads:[~2020-05-14 12:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 12:11 [PATCH 0/5] sf: Cleanup Jagan Teki
2020-05-14 12:11 ` [PATCH 1/5] mtd: spi: Call sst_write in _write ops Jagan Teki
2020-05-19 19:15   ` Jagan Teki
2020-05-14 12:11 ` Jagan Teki [this message]
2020-05-19 19:25   ` [PATCH 2/5] cmd: sf Drop reassignment of new into flash Jagan Teki
2020-05-14 12:11 ` [PATCH 3/5] env: sf: Preserve and free the previous flash Jagan Teki
2020-05-15  7:24   ` Pratyush Yadav
2020-05-15  7:44     ` Jagan Teki
2020-05-15  8:49       ` Pratyush Yadav
2020-05-18 12:06         ` Jagan Teki
2020-05-18 15:41           ` Pratyush Yadav
2020-05-14 12:11 ` [PATCH 4/5] mtd: sf: Drop plat from sf_probe Jagan Teki
2020-05-15  7:17   ` Pratyush Yadav
2020-05-19 19:32     ` Jagan Teki
2020-05-14 12:11 ` [PATCH 5/5] mtd: spi: Use IS_ENABLED to prevent ifdef Jagan Teki
2020-05-14 16:31   ` Daniel Schwierzeck
2020-05-15  4:27     ` Stefan Roese
2020-05-15  7:22       ` Rasmus Villemoes
2020-05-15  7:33         ` Rasmus Villemoes

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=20200514121145.28737-3-jagan@amarulasolutions.com \
    --to=jagan@amarulasolutions.com \
    --cc=u-boot@lists.denx.de \
    /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