[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9988249f-53aa-e615-f64b-28c0c0641ab4@codeaurora.org>
Date: Wed, 29 Jul 2020 12:15:13 +0530
From: Sivaprakash Murugesan <sivaprak@...eaurora.org>
To: Vinod Koul <vkoul@...nel.org>
Cc: agross@...nel.org, bjorn.andersson@...aro.org, bhelgaas@...gle.com,
robh+dt@...nel.org, kishon@...com, mturquette@...libre.com,
sboyd@...nel.org, svarbanov@...sol.com, lorenzo.pieralisi@....com,
p.zabel@...gutronix.de, mgautam@...eaurora.org,
smuthayy@...eaurora.org, varada@...eaurora.org,
linux-arm-msm@...r.kernel.org, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, stable@...r.kernel.org,
Selvam Sathappan Periakaruppan <speriaka@...eaurora.org>
Subject: Re: [PATCH 5/9] phy: qcom-qmp: use correct values for ipq8074 gen2
pcie phy init
On 7/13/2020 11:25 AM, Vinod Koul wrote:
> On 05-07-20, 14:47, Sivaprakash Murugesan wrote:
>> There were some problem in ipq8074 gen2 pcie phy init sequence, fix
> Can you please describe these problems, it would help review to
> understand the issues and also for future reference to you
Hi Vinod,
As you mentioned we are updating few register values
and also adding clocks and resets.
the register values are given by the Hardware team and there
is some fine tuning values are provided by Hardware team for the
issues we faced downstream.
Also, few register values are typos for example QSERDES_RX_SIGDET_CNTRL
is a rx register it was wrongly in serdes table.
I will try to mention these details in next patch.
Powered by blists - more mailing lists