u-boot.git/drivers/block/blk-uclass.c, branch v2018.01

dm: blk: Use uclass_find_first/next_device() in blk_first/next_device()

2017-12-13T02:53:45+00:00

This patch changes the calls to uclass_first/next_device() in blk_first/
next_device() to use uclass_find_first/next_device() instead. These functions
don't prepare the devices, which is correct in this case.

With this patch applied, the "usb storage" command now works again as
expected:

=> usb storage
  Device 0: Vendor: SanDisk Rev: 1.00 Prod: Ultra
  Type: Removable Hard Disk
  Capacity: 58656.0 MB = 57.2 GB (120127488 x 512)

Without this patch, it used to generate this buggy output:

=> usb storage
Card did not respond to voltage select!
mmc_init: -95, time 26
No storage devices, perhaps not 'usb start'ed..?

Signed-off-by: Stefan Roese 
Suggested-by: Simon Glass 
Cc: Simon Glass 
Cc: Bin Meng 
Reviewed-by: Bin Meng 
Reviewed-by: Simon Glass

blk: Remove various places that do flush cache after read

2017-09-15T12:05:10+00:00

All these places seem to inherit the codes from the MMC driver where
a FIXME was put in the comment. However the correct operation after
read should be cache invalidate, not flush.

The underlying drivers should be responsible for the cache operation.
Remove these codes completely.

Signed-off-by: Bin Meng 
Reviewed-by: Stefan Roese 
Reviewed-by: York Sun 
Reviewed-by: Joe Hershberger 
Reviewed-by: Simon Glass 
Tested-by: York Sun

blk: dm: make blk_create_device() take a number of block instead of a size

2017-09-12T03:43:58+00:00

There is an overflow problem when taking the size instead of the number
of blocks in blk_create_device(). This results in a wrong device size: the
device apparent size is its real size  modulo 4GB.
Using the number of blocks instead of the device size fixes the problem and
is more coherent with the internals of the block layer.

Signed-off-by: Jean-Jacques Hiblot 
Reviewed-by: Simon Glass

block: ide: Fix block read/write with driver model

2017-09-10T16:27:37+00:00

This converts the IDE driver to driver model so that block read and
write are fully functional.

Fixes: b7c6baef ("x86: Convert MMC to driver model")
Reported-by: Heinrich Schuchardt 
Signed-off-by: Bin Meng 
Reviewed-by: Simon Glass 
Tested-by: Heinrich Schuchardt

dm: blk: Update return value in blk_create_devicef()

2017-08-17T07:44:16+00:00

This returns 'ret' but the value is always zero. Update it to simply
return 0, for clarity.

Signed-off-by: Simon Glass

dm: blk: Add a function to find an interface-type name

2017-08-17T07:44:16+00:00

Add a function to find the name of an interface type (e.g. "sata", "scsi")
from the interface type enum.

This is useful for generic code (not specific to SATA or SCSI, for
example) that wants to display the type of interface it is dealing with.

Signed-off-by: Simon Glass

dm: blk: part: Add UCLASS_NVME and IF_TYPE_NVME

2017-08-13T19:17:30+00:00

This adds a new uclass id and block interface type for NVMe.

Signed-off-by: Zhikang Zhang 
Signed-off-by: Wenbin Song 
Signed-off-by: Bin Meng 
Signed-off-by: Jon Nettleton 
Reviewed-by: Tom Rini

dm: blk: Add a way to obtain a block device from its parent

2017-06-09T11:25:16+00:00

Many devices support a child block device (e.g. MMC, USB). Add a
convenient way to get this device given the parent device.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini

dm: blk: Improve block device claiming

2017-06-01T13:03:05+00:00

The intention with block devices is that the device number (devnum field
in its descriptor) matches the alias of its parent device. For example,
with:

	aliases {
		mmc0 = "/sdhci@700b0600";
		mmc1 = "/sdhci@700b0400";
	}

we expect that the block devices for mmc0 and mmc1 would have device
numbers of 0 and 1 respectively.

Unfortunately this does not currently always happen. If there is another
MMC device earlier in the driver model data structures its block device
will be created first. It will therefore get device number 0 and mmc0
will therefore miss out. In this case the MMC device will have sequence
number 0 but its block device will not.

To avoid this, allow a device to request a device number and bump any
existing device number that is using it. This all happens during the
binding phase so it is safe to change these numbers around. This allows
device numbers to match the aliases in all circumstances.

Add a test to verify the behaviour.

Signed-off-by: Simon Glass

dm: blk: Add a function to find the next block device number

2017-06-01T13:03:05+00:00

At present this code is inline. Move it into a function to allow it to
be used elsewhere.

Signed-off-by: Simon Glass