From: Tom Rini Date: Fri, 23 Feb 2018 07:21:11 -0500 Subject: [U-Boot] [PATCH v2 3/4] mmc: omap_hsmmc: make it possible to compile out ADMA support In-Reply-To: <1519378819-19867-4-git-send-email-jjhiblot@ti.com> References: <1519378819-19867-1-git-send-email-jjhiblot@ti.com> <1519378819-19867-4-git-send-email-jjhiblot@ti.com> Message-ID: <20180223122111.GF4311@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 Fri, Feb 23, 2018 at 10:40:18AM +0100, Jean-Jacques Hiblot wrote: > Some platforms don't have ADMA controllers. For those platforms, compiling > it out reduces the size of the binary by about 600 bytes. > Leaving the support in doesn't break things as the driver checks at runtime > if the ADMA2 controller is present. > > Signed-off-by: Jean-Jacques Hiblot > > --- > > Changes in v2: > - Use a Kconfig option to compile out the ADMA support instead of relying > on the platform architecture > > drivers/mmc/Kconfig | 9 +++++++++ > drivers/mmc/omap_hsmmc.c | 12 ++++++------ > 2 files changed, 15 insertions(+), 6 deletions(-) > > diff --git a/drivers/mmc/Kconfig b/drivers/mmc/Kconfig > index f2d8256..88a1359 100644 > --- a/drivers/mmc/Kconfig > +++ b/drivers/mmc/Kconfig > @@ -239,6 +239,15 @@ config MMC_OMAP_HS > > If unsure, say N. > > +config MMC_OMAP_HS_ADMA > + bool "ADMA support for OMAP HS MMC" > + depends on MMC_OMAP_HS && !OMAP34XX > + default y if !AM33XX Is this logic really the right restrictions? Does it work on some AM33XX platforms (AM43xx?) and just never OMAP34XX? Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: