From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 15 Feb 2016 17:37:18 -0500 Subject: [U-Boot] [PATCH 00/30] dm: Add driver-model support for block drivers In-Reply-To: <1455502619-16093-1-git-send-email-sjg@chromium.org> References: <1455502619-16093-1-git-send-email-sjg@chromium.org> Message-ID: <20160215223718.GK23166@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sun, Feb 14, 2016 at 07:16:29PM -0700, Simon Glass wrote: > Recent additions of the MMC and DISK uclasses have indicated that it is time > to look at adding a uclass for block devices. This series does this and > includes a few clean-ups to the partition code also. > > A block device is typically a child device of its storage parent. For > example an MMC device will have a block-device child. A USB storage device > may have multiple block-device children, one for each LUN. > > With this series only USB storage and 'host' are converted over to use the > new support. Several more remain, including SCSI, IDE and MMC. Each of these > should get its own uclass. > > The uclass implements only a few basic features. A few tests are added to > check that things work as expected. > > The code size impact of switching to driver model for block devices is > small. One benefit is that it becomes possible to enumerate all block > devices, regardless of their type. Things generally make sense. I've tossed out a few Reviewed-by's for some things but I looked over everything. My only question is have you run buildman -S and compared the numbers, especially for things that aren't opting in yet? A few oddballs have been spotted by that already :) -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: