Hi, On Mon, Apr 9, 2018 at 11:36 PM, Manu Gautam <mgautam@xxxxxxxxxxxxxx> wrote: > Hi, > > > On 3/30/2018 2:24 AM, Doug Anderson wrote: >> Hi, >> >> On Thu, Mar 29, 2018 at 11:44 AM, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: >>> Hi, >>> >>> On Thu, Mar 29, 2018 at 4:04 AM, Manu Gautam <mgautam@xxxxxxxxxxxxxx> wrote: >>>> QMP PHY for USB/PCIE requires pipe_clk for locking of >>>> retime buffers at the pipe interface. Driver checks for >>>> PHY_STATUS without enabling pipe_clk due to which >>>> phy_init() fails with initialization timeout. >>>> Though pipe_clk is output from PHY (after PLL is programmed >>>> during initialization sequence) to GCC clock_ctl and then fed >>>> back to PHY but for PHY_STATUS register to reflect successful >>>> initialization pipe_clk from GCC must be present. >>>> Since, clock driver now ignores status_check for pipe_clk on >>>> clk_enable/disable, driver can safely enable/disable pipe_clk >>>> from phy_init/exit. >>>> >>>> Signed-off-by: Manu Gautam <mgautam@xxxxxxxxxxxxxx> >>>> --- >>>> drivers/phy/qualcomm/phy-qcom-qmp.c | 22 ++++++++-------------- >>>> 1 file changed, 8 insertions(+), 14 deletions(-) >>> Overall this looks much better than the previous version. Thanks! :) >>> >>> I wonder one thing though. You describe the original problem as this: >>> >>> 1. If you don't turn the clock on in qcom_qmp_phy_init() then the PHY >>> never sets the "ready" status. >>> >>> 2. If you don't have the PHY powered on / out of reset (which happens >>> in qcom_qmp_phy_init()) then when you enable/disable the clock it >>> doesn't properly update the status. That's why you needed patch #1 in >>> this series. >>> >>> >>> I wonder: could you solve the above _without_ needing to use >>> BRANCH_HALT_DELAY in the clock driver? Specifically, can you tell me >>> what happens if you put the clk_prepare_enable() after you've powered >>> on the PHY and taken it out of reset but before you check the status? >>> Said another way, put the "clk_prepare_enable(qphy->pipe_clk)" call >>> right before the "readl_poll_timeout" of the ready status? >>> >>> >>> If you do that, you'll turn everything on. Then you'll check that the >>> clock's status is OK and then that the PHY's status is OK. >> Oh! This is what you did in the previous version of the patch, then you said: >> >> "That is still needed as PHY might take some time to generate pipe_clk >> after its PLL is locked". >> >> It's really going to take more than the 200 us that the clock driver >> is giving it? If so, I'd prefer to increase the amount of time waited >> in the clock driver, or adding a fixed delay _before_ the clk_enable() >> so that the 200 us that the clock driver gives it would be enough. >> >> I'm just not a fan of ignoring status bits if it can be helped. > > I too would want to do that but it is not just about the delay. > As per QMP PHY hardware designers, pipe_clk should be enabled in GCC > as first thing in the PHY initialization sequence. Same sequence also has > been used in downstream phy driver always. > Changing the sequence might work but I would like to stick to the HPG > recommendation and avoid any deviation as PHY issues are very hard to > debug. So hardware guys tell you that you're _supposed to_ ignore the clock ready bit for that clock and just hope it turns on and settles in time once power comes on for the clock? That doesn't seem ideal. My guess is that it's a bug in the specification that the QMP PHY hardware designers gave you. Stephen can feel free to override me if he disagrees since he's in charge of the clock part of this, but IMHO we should get the specification fixed and turn things on in the order that lets us check the status bits. -Doug -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
