lkml.org 
[lkml]   [2018]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH V4 2/4] mmc: cqhci: DMA Configuration prior to CQE
From
Date
On 20/12/18 11:01 PM, Sowjanya Komatineni wrote:
> Hi Adrian,
>
> Thank you for the feedback.
>
>> This doesn't seem to relate to the host controller implementation.
>> "The device" means the eMMC.
>
> Yes, setting block size of 512B before enabling command queue is a device specific
> requirement not host specific. So thought to update in cqhci driver to follow this
> device specific sequence requirement. This also serves tegra sdhci host strictly
> following this device specific requirement.

Not sure what you mean. The eMMC block size is set by CMD16. In fact CMD16
is not used because 512B is the default so it never needs to be changed.

>
>> We don't want to disable and re-enable in the request function,
>> so that change is not good for controllers that don't have your problem.
>> Another thing to consider is that the block size register may not need to be changed
>> - for example when cqhci is halted to allow a manual discard, the block size register is
>> not updated, so I would expect its value to be unchanged.
>
> Once block size is set prior to enabling CQE, it stays same till command queue is
> disabled and I don’t think it needs reconfiguration.
>
>> There are ways you can solve this in your driver.
>> You could look at using SDHCI I/O accessors, and/or implement your own ->enable()
>> instead of calling sdhci_cqe_enable() directly. Would that be feasible?
>
> Sure, will provide updated patch that takes care of this inside tegra sdhci host once you
> confirm that we don’t plan to fix this device specific sequence requirement in cqhci driver.
>
> -Sowjanya
>
>

\
 
 \ /
  Last update: 2018-12-21 08:44    [W:0.052 / U:5.276 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site