Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1401018
| From | Doug Anderson <dianders@chromium.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay |
| Date | 2016-05-14 00:30 +0200 |
| Message-ID | <rytKO-417-15@gated-at.bofh.it> (permalink) |
| References | <ry7AB-77L-3@gated-at.bofh.it> <ry7AB-77L-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi, On Thu, May 12, 2016 at 3:43 PM, Brian Norris <briannorris@chromium.org> wrote: > 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. ...so I'd be all for landing this patch. Perhaps Shawn can chime in and confirm that our understanding is correct and possibly we can update the commit message. Then presumably someone at Rockchip can keep working to find a better way to set this long term. Sound good? -Doug
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/4] phy: rockchip-emmc: give DLL some extra time to be ready Brian Norris <briannorris@chromium.org> - 2016-05-13 00:50 +0200
[PATCH 3/4] phy: rockchip-emmc: configure default output tap delay Brian Norris <briannorris@chromium.org> - 2016-05-13 00:50 +0200
Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay Doug Anderson <dianders@chromium.org> - 2016-05-14 00:30 +0200
Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay Shawn Lin <shawn.lin@rock-chips.com> - 2016-05-16 06:20 +0200
Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay Doug Anderson <dianders@chromium.org> - 2016-05-16 17:20 +0200
[PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Brian Norris <briannorris@chromium.org> - 2016-05-13 00:50 +0200
Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Shawn Lin <shawn.lin@rock-chips.com> - 2016-05-13 03:10 +0200
Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Doug Anderson <dianders@chromium.org> - 2016-05-13 20:50 +0200
Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Brian Norris <briannorris@chromium.org> - 2016-05-13 23:10 +0200
Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Doug Anderson <dianders@chromium.org> - 2016-05-24 07:00 +0200
[PATCH v2 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Brian Norris <briannorris@chromium.org> - 2016-05-13 23:10 +0200
Re: [PATCH v2 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Doug Anderson <dianders@chromium.org> - 2016-05-14 00:10 +0200
[PATCH 4/4] phy: rockchip-emmc: reindent the register definitions Brian Norris <briannorris@chromium.org> - 2016-05-13 00:50 +0200
Re: [PATCH 4/4] phy: rockchip-emmc: reindent the register definitions Doug Anderson <dianders@chromium.org> - 2016-05-14 00:30 +0200
Re: [PATCH 1/4] phy: rockchip-emmc: give DLL some extra time to be ready Doug Anderson <dianders@chromium.org> - 2016-05-14 00:10 +0200
csiph-web