u-boot.git/include/blk.h, branch u-boot-2016.09.y Unnamed repository; edit this file 'description' to name the repository. dm: blk: Add a comment as to why the bdev member is needed 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T19:52:33+00:00 b6694a33c45530e4c260c7fd6c77cc8472c9412f This member should be explained, since it is not obvious why it is needed. Add a comment. Signed-off-by: Simon Glass <sjg@chromium.org> 
This member should be explained, since it is not obvious why it is needed.
Add a comment.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: blk: Add functions to select a hardware partition 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T19:52:30+00:00 cd0fb55b640b2991c1d29122d252a360037ed903 The block device uclass does not currently support selecting a particular hardware partition but this is needed for MMC. Add it so that the blk API can support MMC properly. Signed-off-by: Simon Glass <sjg@chromium.org> 
The block device uclass does not currently support selecting a particular
hardware partition but this is needed for MMC. Add it so that the blk API
can support MMC properly.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: blk: Add a easier way to create a named block device 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T17:36:29+00:00 9107c973d32c72a6f7ac909fc4a6884a42e4e607 Add a function that automatically builds the device name given the parent and a supplied string. Most callers will want to do this, so putting this functionality in one place makes more sense. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a function that automatically builds the device name given the parent
and a supplied string. Most callers will want to do this, so putting this
functionality in one place makes more sense.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: blk: Allow blk_create_device() to allocate the device number 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T17:36:28+00:00 52138fd4072b64448855eac4c2c9815b46f5b43c Allow a devnum parameter of -1 to indicate that the device number should be alocated automatically. The next highest available device number for that interface type is used. Signed-off-by: Simon Glass <sjg@chromium.org> 
Allow a devnum parameter of -1 to indicate that the device number should be
alocated automatically. The next highest available device number for that
interface type is used.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: systemace: Add a legacy block interface 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T17:36:04+00:00 3ef85e377201c1ebe84e74bfb785c95ccbc37b13 Add a legacy block interface for systemace. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a legacy block interface for systemace.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: blk: Add a legacy block interface 2016-05-17T15:54:43+00:00 Simon Glass sjg@chromium.org 2016-05-01T17:36:03+00:00 6eef6eac1fc137c97bf1993304ed83b8e483c80a There is quite a bit of duplicated common code related to block devices in the IDE and SCSI implementations. Create some helper functions that can be used to reduce the duplication. These rely on a linker list of interface-type drivers Signed-off-by: Simon Glass <sjg@chromium.org> 
There is quite a bit of duplicated common code related to block devices
in the IDE and SCSI implementations.

Create some helper functions that can be used to reduce the duplication.
These rely on a linker list of interface-type drivers

Signed-off-by: Simon Glass <sjg@chromium.org>
drivers: block: fix placement of parameters 2016-04-11T16:44:38+00:00 Eric Nelson eric@nelint.com 2016-04-02T14:37:14+00:00 c8e4d2a8b90cfb2a19c274ba7e5525b2757dab77 Signed-off-by: Eric Nelson <eric@nelint.com> 
Signed-off-by: Eric Nelson <eric@nelint.com>
drivers: block: add block device cache 2016-04-01T21:18:27+00:00 Eric Nelson eric@nelint.com 2016-03-28T17:05:44+00:00 e40cf34a29f1b248643731a11fb1c6f0520d016c Add a block device cache to speed up repeated reads of block devices by various filesystems. This small amount of cache can dramatically speed up filesystem operations by skipping repeated reads of common areas of a block device (typically directory structures). This has shown to have some benefit on FAT filesystem operations of loading a kernel and RAM disk, but more dramatic benefits on ext4 filesystems when the kernel and/or RAM disk are spread across multiple extent header structures as described in commit fc0fc50. The cache is implemented through a minimal list (block_cache) maintained in most-recently-used order and count of the current number of entries (cache_count). It uses a maximum block count setting to prevent copies of large block reads and an upper bound on the number of cached areas. The maximum number of entries in the cache defaults to 32 and the maximum number of blocks per cache entry has a default of 2, which has shown to produce the best results on testing of ext4 and FAT filesystems. The 'blkcache' command (enabled through CONFIG_CMD_BLOCK_CACHE) allows changing these values and can be used to tune for a particular filesystem layout. Signed-off-by: Eric Nelson <eric@nelint.com> 
Add a block device cache to speed up repeated reads of block devices by
various filesystems.

This small amount of cache can dramatically speed up filesystem
operations by skipping repeated reads of common areas of a block
device (typically directory structures).

This has shown to have some benefit on FAT filesystem operations of
loading a kernel and RAM disk, but more dramatic benefits on ext4
filesystems when the kernel and/or RAM disk are spread across
multiple extent header structures as described in commit fc0fc50.

The cache is implemented through a minimal list (block_cache) maintained
in most-recently-used order and count of the current number of entries
(cache_count). It uses a maximum block count setting to prevent copies
of large block reads and an upper bound on the number of cached areas.

The maximum number of entries in the cache defaults to 32 and the maximum
number of blocks per cache entry has a default of 2, which has shown to
produce the best results on testing of ext4 and FAT filesystems.

The 'blkcache' command (enabled through CONFIG_CMD_BLOCK_CACHE) allows
changing these values and can be used to tune for a particular filesystem
layout.

Signed-off-by: Eric Nelson <eric@nelint.com>
dm: blk: Add a block-device uclass 2016-03-14T21:34:50+00:00 Simon Glass sjg@chromium.org 2016-02-29T22:25:55+00:00 09d71aac7b530f03ec29cc9d5787047460a629ca Add a uclass for block devices. These provide block-oriented data access, supporting reading, writing and erasing of whole blocks. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Stephen Warren <swarren@nvidia.com> 
Add a uclass for block devices. These provide block-oriented data access,
supporting reading, writing and erasing of whole blocks.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Stephen Warren <swarren@nvidia.com>
dm: block: Adjust device calls to go through helpers function 2016-03-14T21:34:50+00:00 Simon Glass sjg@chromium.org 2016-02-29T22:25:52+00:00 2a981dc2c62c500110aad297fa70503aec36e689 To ease conversion to driver model, add helper functions which deal with calling each block device method. With driver model we can reimplement these functions with the same arguments. Use inline functions to avoid increasing code size on some boards. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Stephen Warren <swarren@nvidia.com> 
To ease conversion to driver model, add helper functions which deal with
calling each block device method. With driver model we can reimplement these
functions with the same arguments.

Use inline functions to avoid increasing code size on some boards.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Tested-by: Stephen Warren <swarren@nvidia.com>