[PATCH 3/4] phy: rockchip-emmc: configure default output tap delay
dianders at chromium.org
Mon May 16 08:12:57 PDT 2016
On Sun, May 15, 2016 at 9:15 PM, Shawn Lin <shawn.lin at rock-chips.com> wrote:
> Hi Doug,
> On 2016/5/14 6:25, Doug Anderson wrote:
>> On Thu, May 12, 2016 at 3:43 PM, Brian Norris <briannorris at chromium.org>
>>> The output tap delay controls helps maintain the hold requirements for
>>> eMMC. The exact value is dependent on the SoC and other factors, though
>>> it isn't really an exact science. But the default of 0 is not very good,
>>> as it doesn't give the eMMC much hold time, so let's bump up to 4
>>> (approx 90 degree phase?). If we need to configure this any further
>>> (e.g., based on board or speed factors), we may need to consider a
>>> device tree representation.
>> As I understand it, this solves much the same problem as my patch in
>> <https://patchwork.kernel.org/patch/9085581/>, but for the eMMC port
>> on rk3399 (which doesn't use dw_mmc). As argued in that patch and
>> also in the discussion from
>> <https://patchwork.kernel.org/patch/9030621/>, if we eventually end up
>> needing to put something in the device tree we need to be really
>> careful. Specifically to get the exact right value here I think you
>> need to consider the input clock, speed mode, and any SoC-specific
>> delays differences between the clock and the data lines. That would
>> imply that, if anything, the device tree data would only contain
>> information about the SoC-specific delay differences and all other
>> work to set this value would involve coordination between the PHY and
>> the SDHCI controller.
>> However, as also discussed previously, we don't appear to need to be
>> very exact about the value here. It seems like setting this to 4 (~90
>> degrees?) is a much better starting point than leaving it at the
>> default of 0.
> The value, 4, is based on real silicon test observed from the
> oscilloscope, and of course it meets the requirement of speed modes.
> For arasan't phy, its phase is very accurate, so the real timing of
> the value you set almost won't vary too much for different Socs.
> So explicitly assigning 4 here looks sane currently except for crazy
> PCB layout...
Great to hear. So we can probably just use your email as the basis of
the commit message? How about this for the commit text then:
The output tap delay controls helps maintain the hold requirements for
eMMC. The value, 4, is based on real silicon test observed from the
oscilloscope, and of course it meets the requirement of speed modes.
For arasan't phy, its phase is very accurate, so the real timing of
the value you set won't vary too much for different SoCs.
If / when we find an instance of a crazy PCB layout that needs a value
different than 4, we will figure out how to best specify that,
possibly using the device tree in some way.
More information about the Linux-rockchip