u-boot.git/drivers/block, branch v2018.03

SystemACE: Remove

2018-02-14T04:24:22+00:00

This driver is no longer used on any supported platform in U-Boot and
there is no interest in maintaining it further from people that have
used it historically.

Cc: Simon Glass 
Cc: Michal Simek 
c: Alexey Brodkin 
Signed-off-by: Tom Rini 
Acked-by: Michal Simek

Move most CONFIG_HAVE_BLOCK_DEVICE to Kconfig

2018-02-09T00:09:03+00:00

config_fallbacks.h has some logic that sets HAVE_BLOCK_DEVICE
based on a list of enabled options.  Moving HAVE_BLOCK_DEVICE to
Kconfig allows us to drastically shrink the logic in
config_fallbacks.h

Signed-off-by: Adam Ford 
[trini: Rename HAVE_BLOCK_DEVICE to CONFIG_BLOCK_DEVICE]
Signed-off-by: Tom Rini

block: Migrate SystemACE chip to Kconfig

2018-02-09T00:08:41+00:00

Migrate the base and sub-options to Kconfig.  Note that we only enable
this in the base sandbox config now.

Cc: Alexey Brodkin 
Cc: Michal Simek 
Signed-off-by: Tom Rini 
---
Is this driver still used anywhere?  It's fishy that it's only enabled
in sandbox anymore.

efi_driver: EFI block driver

2018-01-22T22:09:14+00:00

This patch provides
* a uclass for EFI drivers
* a EFI driver for block devices

For each EFI driver the uclass
* creates a handle
* adds the driver binding protocol

The uclass provides the bind, start, and stop entry points for the driver
binding protocol.

In bind() and stop() it checks if the controller implements the protocol
supported by the EFI driver. In the start() function it calls the bind()
function of the EFI driver. In the stop() function it destroys the child
controllers.

The EFI block driver binds to controllers implementing the block io
protocol.

When the bind function of the EFI block driver is called it creates a
new U-Boot block device. It installs child handles for all partitions and
installs the simple file protocol on these.

The read and write functions of the EFI block driver delegate calls to the
controller that it is bound to.

A usage example is as following:

U-Boot loads the iPXE snp.efi executable. iPXE connects an iSCSI drive and
exposes a handle with the block IO protocol. It calls ConnectController.

Now the EFI block driver installs the partitions with the simple file
protocol.

iPXE uses the simple file protocol to load Grub or the Linux Kernel.

Signed-off-by: Heinrich Schuchardt 
[agraf: add comment on calloc len]
Signed-off-by: Alexander Graf

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: Don't bother to create BLK device if no CDROM inserted

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

When there is no CDROM inserted, the block size is zero hence there
is no need to create a BLK device for it.

Signed-off-by: Bin Meng 
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

block: Drop the ftide020 driver

2017-09-03T19:30:35+00:00

This is not used in U-Boot.

Signed-off-by: Bin Meng