Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1400983
| From | Brian Norris <briannorris@chromium.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance |
| Date | 2016-05-13 23:10 +0200 |
| Message-ID | <rysvp-2VC-19@gated-at.bofh.it> (permalink) |
| References | <ry7AB-77L-3@gated-at.bofh.it> <ry7AC-77L-17@gated-at.bofh.it> <ry9M5-XI-1@gated-at.bofh.it> <ryqjU-Jw-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, May 13, 2016 at 11:46:33AM -0700, Doug Anderson wrote: > On Thu, May 12, 2016 at 6:02 PM, Shawn Lin <shawn.lin@rock-chips.com> wrote: > > On 2016/5/13 6:43, Brian Norris wrote: > >> @@ -154,6 +167,20 @@ static int rockchip_emmc_phy_power_on(struct phy > >> *phy) > >> struct rockchip_emmc_phy *rk_phy = phy_get_drvdata(phy); > >> int ret = 0; > >> > >> + /* DLL operation: 170 to 200 MHz */ > > > > > > What is 170 here? Should we expose them to dt instead of hardcoding > > them? > > This was probably my fault. I did some searching and found > <https://arasan.com/wp-content/media/eMMC-5-1-Total-Solution_Rev-1-3.pdf>. > It appears to be docs for a similar (but not identical) PHY. We were > looking at it to try to get more clarity on some bits that were hard > to understand in the docs we had. > > In that doc there appear to be 3 bits for selecting the DLL operation > and they have ranges defined. In Rockchip's PHY there are only 2 > bits. Thus things don't map totally properly. > > Anyway, comment should probably be removed. [...] > So overall: > > * Should re-spin and remove the comment about 170 MHz. > > * I think this could land as-is other than the comment. Right, will fix the first bullet point. Brian
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