[U-Boot] MMC_DAVINCI not compliant with CONFIG_BLK

[Peter Howard]

>From: Adam Ford <aford173 at gmail.com> 
>Sent: Tuesday, 7 August 2018 9:12 AM
>To: Peter Howard <phoward at gme.net.au>
>Cc: U-Boot Mailing List <u-boot at lists.denx.de>; David Lechner <david at lechnology.com>; Stefano Babic <sbabic at denx.de>; Heiko Schocher <hs at denx.de>; Christoph Rüdisser <christoph.ruedisser at omicronenergy.com>; Manfred Rudigier <manfred.rudigier at omicronenergy.com>
>Subject: Re: MMC_DAVINCI not compliant with CONFIG_BLK
>
>
>> On Mon, Aug 6, 2018, 5:22 PM Peter Howard <mailto:phoward at gme.net.au> wrote:
>> Sorry a clarification - my main focus is the LCDK board - it's that one which has the 4K overrun.
>> 
>> -----Original Message-----
>> From: Peter Howard 
>> Sent: Tuesday, 7 August 2018 8:22 AM
>> To: 'Adam Ford' <mailto:aford173 at gmail.com>; U-Boot Mailing List <mailto:u-boot at lists.denx.de>
>> Cc: David Lechner <mailto:david at lechnology.com>; Stefano Babic <mailto:sbabic at denx.de>; Heiko Schocher <mailto:hs at denx.de>; Christoph Rüdisser <mailto:christoph.ruedisser at omicronenergy.com>; Manfred Rudigier  <mailto:manfred.rudigier at omicronenergy.com>
>> Subject: RE: MMC_DAVINCI not compliant with CONFIG_BLK
>>
>> Hi Adam,
>>
>> My normal email is broken at the moment sorry for inflicting Outlook on you ☹
>>
>>
>> I've been working on this for a few weeks and at this stage I have a u-boot that builds.  The only problem is that introducing the DM into the SPL build (for NAND) currently overruns the SRAM area by 4K or so.  
>>
>
> Is DM required in SPL?
>
> There are a variety of drivers with #ifdef around various parts of the code.

That's a question I'm not sure about.  However . . . MMC is enabled in the SPL.  So, even if DM isn't mandated, you have to either use it or maintain both the old and new form of the driver.  Or disable MMC.  The only other config I could find which definitely combines MMC in the SPL with the DM is configs/stm32mp15_basic_defconfig - and it uses the DM form (as far as I can see  - I could be wrong).

>
>
>> If you want to have a look I'm happy to send you my changes so-far.
>>
>> PJH
>>
>> -----Original Message-----
>> From: Adam Ford <mailto:aford173 at gmail.com> 
>> Sent: Monday, 6 August 2018 10:11 PM
>> To: U-Boot Mailing List <mailto:u-boot at lists.denx.de>
>> Cc: Peter Howard <mailto:phoward at gme.net.au>; David Lechner <mailto:david at lechnology.com>; Stefano Babic <mailto:sbabic at denx.de>; Heiko Schocher <mailto:hs at denx.de>; Christoph Rüdisser <mailto:christoph.ruedisser at omicronenergy.com>;  Manfred Rudigier <mailto:manfred.rudigier at omicronenergy.com>
>> Subject: MMC_DAVINCI not compliant with CONFIG_BLK
>>
>> From what I gathered over the weekend, the MMC_DAVINCI hasn't migrated to DM_MMC nor does CONFIG_BLK successfully build on ARCH_DAVINCI boards that enable MMC_DAVINCI.
>>
>> I started work to attempt to make it DM_MMC and OF_CONTROL compliant using the da850evm.
>>
>> Before I go too far, I just want to make sure nobody else is doing this work.  I don't want to duplicate an effort or waste time if it's been done or is in the works.
>>
>> If someone is interesting in testing the patch when I am done, it would be very helpful, because I only have the da850evm.  If someone has a patch and wants me to test it, I would also be willing to try it.
>>
>> adam




______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________