Re: [PATCH v2 09/24] blk: Rename HAVE_BLOCK_DEVICE

2022-09-14 Thread Simon Glass
Hi Heinrich, On Wed, 14 Sept 2022 at 01:40, Heinrich Schuchardt wrote: > > On 9/14/22 03:42, AKASHI Takahiro wrote: > > On Thu, Aug 11, 2022 at 07:34:48PM -0600, Simon Glass wrote: > >> This option is fact really related to SPL. For U-Boot proper we always use > >> driver model for block devices,

Re: [PATCH v2 09/24] blk: Rename HAVE_BLOCK_DEVICE

2022-09-14 Thread Heinrich Schuchardt
On 9/14/22 03:42, AKASHI Takahiro wrote: On Thu, Aug 11, 2022 at 07:34:48PM -0600, Simon Glass wrote: This option is fact really related to SPL. For U-Boot proper we always use driver model for block devices, so CONFIG_BLK is enabled if block devices are in use. It is only for SPL that we have

Re: [PATCH v2 09/24] blk: Rename HAVE_BLOCK_DEVICE

2022-09-13 Thread AKASHI Takahiro
On Thu, Aug 11, 2022 at 07:34:48PM -0600, Simon Glass wrote: > This option is fact really related to SPL. For U-Boot proper we always use > driver model for block devices, so CONFIG_BLK is enabled if block devices > are in use. > > It is only for SPL that we have two cases: > > - SPL_BLK is enabl

[PATCH v2 09/24] blk: Rename HAVE_BLOCK_DEVICE

2022-08-11 Thread Simon Glass
This option is fact really related to SPL. For U-Boot proper we always use driver model for block devices, so CONFIG_BLK is enabled if block devices are in use. It is only for SPL that we have two cases: - SPL_BLK is enabled, in which case we use driver model and blk-uclass.c - SPL_BLK is not ena