[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8BNQZ/CFljuxsSL@matsya>
Date: Thu, 12 Jan 2023 23:41:13 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: martin.petersen@...cle.com, jejb@...ux.ibm.com,
andersson@...nel.org, quic_cang@...cinc.com,
quic_asutoshd@...cinc.com, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-phy@...ts.infradead.org,
linux-scsi@...r.kernel.org, dmitry.baryshkov@...aro.org,
ahalaney@...hat.com, abel.vesa@...aro.org, alim.akhtar@...sung.com,
avri.altman@....com, bvanassche@....org
Subject: Re: [PATCH v5 00/23] ufs: qcom: Add HS-G4 support
On 22-12-22, 19:39, Manivannan Sadhasivam wrote:
> Hello,
>
> This series adds HS-G4 support to the Qcom UFS driver and PHY driver.
> The newer Qcom platforms support configuring the UFS controller and PHY
> in dual gears (i.e., controller/PHY can be configured to run in two gear
> speeds). This is accomplished by adding two different PHY init sequences
> to the PHY driver and the UFS driver requesting the one that's required
> based on the platform configuration.
>
> Initially the ufs-qcom driver will use the default gear G2 for enumerating
> the UFS device. Afer enumeration, the max gear supported by both the
> controller and device would be found out and that will be used thereafter.
> But for using the max gear after enumeration, the ufs-qcom driver requires
> the UFS device to be reinitialized. For this purpose, a separate quirk has
> been introduced in the UFS core along with a callback and those will be used
> by the ufs-qcom driver.
The series lgtm. This fails for me to apply though due to other patches
I have picked up.
Can you please rebase the phy patches and send those
--
~Vinod
Powered by blists - more mailing lists