From: Kishon Vijay Abraham I <kishon@ti.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>,
<vinholikatti@gmail.com>, <jejb@linux.vnet.ibm.com>,
<martin.petersen@oracle.com>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>
Cc: <subhashj@codeaurora.org>, <bjorn.andersson@linaro.org>,
<evgreen@chromium.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 0/3] scsi: ufs-qcom: Remove all direct calls to qcom-ufs phy
Date: Tue, 25 Sep 2018 12:12:49 +0530 [thread overview]
Message-ID: <75d4820c-d154-cc5c-e7b6-72defdfdce5e@ti.com> (raw)
In-Reply-To: <20180904101719.18049-1-vivek.gautam@codeaurora.org>
Hi Vivek,
On Tuesday 04 September 2018 03:47 PM, Vivek Gautam wrote:
> Cleaning up the ufs-qcom host further to remove all direct calls
> into qcom-ufs driver.
> Only phy-qcom-ufs-qmp-20nm phy handles these direct calls from ufs host
> and this phy is not used in any supported qcom platform in current kernel.
> So, while we free up the host from all the ufs_qcom_phy_*() API calls
> we should declare 20nm phy as broken.
> For this we fork out couple of configs from PHY_QCOM_UFS -
> PHY_QCOM_UFS_14NM and PHY_QCOM_UFS_20NM out of which we declare
> PHY_QCOM_UFS_20NM as 'broken'.
>
> This series helps in a clean use of ufs phy support for sdm845
> and further SoCs that will also use phy-qcom-qmp phy driver.
I think this entire series should go via linux-phy tree. I need ACK from UFS
MAINTAINER for the second patch.
Thanks
Kishon
prev parent reply other threads:[~2018-09-25 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:17 [PATCH 0/3] scsi: ufs-qcom: Remove all direct calls to qcom-ufs phy Vivek Gautam
2018-09-04 10:17 ` [PATCH 1/3] phy: qcom-ufs: Remove stale methods that handle ref clk Vivek Gautam
2018-09-24 17:23 ` Bjorn Andersson
2018-09-25 5:40 ` Vivek Gautam
2018-09-04 10:17 ` [PATCH 2/3] scsi/ufs: qcom: Remove ufs_qcom_phy_*() calls from host Vivek Gautam
2018-09-24 17:24 ` Bjorn Andersson
2018-09-25 9:52 ` Vivek Gautam
2018-09-26 0:28 ` Martin K. Petersen
2018-09-26 6:14 ` Vivek Gautam
2018-09-04 10:17 ` [PATCH 3/3] phy: qcom-ufs: Declare 20nm qcom ufs qmp phy as Broken Vivek Gautam
2018-09-24 17:29 ` Bjorn Andersson
2018-09-24 8:14 ` [PATCH 0/3] scsi: ufs-qcom: Remove all direct calls to qcom-ufs phy Vivek Gautam
2018-09-25 6:42 ` Kishon Vijay Abraham I [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75d4820c-d154-cc5c-e7b6-72defdfdce5e@ti.com \
--to=kishon@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox