From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 3/3] cmd: sata: Add block unbind device function
Date: Mon, 27 Jan 2020 19:56:21 -0500 [thread overview]
Message-ID: <20200128005621.GF13379@bill-the-cat> (raw)
In-Reply-To: <20191204103558.24251-3-peng.ma@nxp.com>
On Wed, Dec 04, 2019 at 10:36:47AM +0000, Peng Ma wrote:
> If we didn't unbind the sata from block device, the same devices would
> be added after sata remove,
> This patch is to resolve this issue as below:
>
> => sata info
> SATA#0:
> (3.0 Gbps)
> SATA#1:
> (3.0 Gbps)
> Device 0: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005PY30
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
> Device 1: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005VX30
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
> => sata stop
> => sata info
> SATA#0:
> (3.0 Gbps)
> SATA#1:
> (3.0 Gbps)
> Device 0: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005PY300
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
> Device 1: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005VX300
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
> Device 2: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005PY300
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
> Device 3: Model: INTEL SSDSA2BW300G3D Firm: 4PC10362 Ser#: BTPR247005VX300
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
>
> Signed-off-by: Peng Ma <peng.ma@nxp.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200127/ccdc77a2/attachment.sig>
next prev parent reply other threads:[~2020-01-28 0:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 10:36 [PATCH 1/3] ata: sata_sil: Continue probing other sata port when failed current port Peng Ma
2019-12-04 10:36 ` [PATCH 2/3] ata: fsl_sata: " Peng Ma
2019-12-28 2:26 ` Simon Glass
2019-12-30 7:32 ` [EXT] " Peng Ma
2020-01-08 20:12 ` Tom Rini
2019-12-04 10:36 ` [PATCH 3/3] cmd: sata: Add block unbind device function Peng Ma
2019-12-28 2:26 ` Simon Glass
2019-12-30 7:19 ` [EXT] " Peng Ma
2020-01-08 20:12 ` Tom Rini
2020-01-08 21:49 ` Anatolij Gustschin
2020-01-08 21:57 ` Tom Rini
2020-01-28 0:56 ` Tom Rini [this message]
2019-12-28 2:26 ` [PATCH 1/3] ata: sata_sil: Continue probing other sata port when failed current port Simon Glass
2019-12-30 7:27 ` [EXT] " Peng Ma
2020-01-08 20:12 ` Tom Rini
2020-01-09 2:22 ` [EXT] " Peng Ma
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=20200128005621.GF13379@bill-the-cat \
--to=trini@konsulko.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