dm: spi: Move the per-child data size to the uclass
This is common to all SPI drivers and specifies a structure used by the uclass. It makes more sense to define it in the uclass. Reviewed-by:Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by:
Simon Glass <sjg@chromium.org>
Showing
- drivers/spi/cadence_qspi.c 0 additions, 1 deletiondrivers/spi/cadence_qspi.c
- drivers/spi/designware_spi.c 0 additions, 1 deletiondrivers/spi/designware_spi.c
- drivers/spi/exynos_spi.c 0 additions, 1 deletiondrivers/spi/exynos_spi.c
- drivers/spi/sandbox_spi.c 0 additions, 1 deletiondrivers/spi/sandbox_spi.c
- drivers/spi/soft_spi.c 0 additions, 1 deletiondrivers/spi/soft_spi.c
- drivers/spi/spi-uclass.c 1 addition, 0 deletionsdrivers/spi/spi-uclass.c
- drivers/spi/tegra114_spi.c 0 additions, 1 deletiondrivers/spi/tegra114_spi.c
- drivers/spi/tegra20_sflash.c 0 additions, 1 deletiondrivers/spi/tegra20_sflash.c
- drivers/spi/tegra20_slink.c 0 additions, 1 deletiondrivers/spi/tegra20_slink.c
Loading
Please register or sign in to comment