From: Kishon Vijay Abraham I <kishon@ti.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: <martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <subhashj@codeaurora.org>,
<bjorn.andersson@linaro.org>, <devicetree@vger.kernel.org>,
<jejb@linux.vnet.ibm.com>, <vinholikatti@gmail.com>,
<linux-arm-msm-owner@vger.kernel.org>
Subject: Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code
Date: Wed, 9 Aug 2017 11:18:26 +0530 [thread overview]
Message-ID: <d49316e0-8ccc-21b3-e952-ddb0a941f3b3@ti.com> (raw)
In-Reply-To: <b69ecef93852cf5a7bf342550de16f19@codeaurora.org>
Vivek,
On Tuesday 08 August 2017 09:20 PM, Vivek Gautam wrote:
> Hi Koshon,
>
> On 2017-08-08 17:39, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 04 August 2017 12:18 PM, Vivek Gautam wrote:
>>> Refactoring the qcom-ufs phy and host controller code to move
>>> further towards the generic phy usage. Right now the qcom-ufs exports
>>> a bunch of APIs that are used by the host controller to initialize
>>> the phy.
>>> With this patch series, we populate the phy_init() which was a no-op
>>> earlier. The host controller then calls the phy_init() at the designated
>>> place rather than doing it invariably in ufs_hcd_init().
>>>
>>> As part of this series, we introduce phy modes for ufs phy.
>>> The M-PHY has two data rates defined for each generations (Gears) -
>>> Rate A and Rate B. These can serve as the two modes of ufs HS phy.
>>> Host controller can direct the phy to set the respective configurations
>>> based on the phy modes.
>>>
>>> The patch-series has been tested with necessary dt patches on db820c.
>>
>> Can the first 3 patches go independently of the other 2 or should all this be
>> merged together?
>
> The first 3 patches are independent, but the next 2 patches depend on those 3
> for functionality.
> I would prefer all to go in one tree. If you want to pull these in the phy tree,
> I will request Subhash/Martin to ack the patches.
sure, that should be fine!
Thanks
Kishon
next prev parent reply other threads:[~2017-08-09 5:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 6:48 Vivek Gautam
2017-08-04 6:48 ` [PATCH 1/5] dt-bindings: phy: Add PHY_TYPE_UFS definition Vivek Gautam
2017-08-04 6:48 ` [PATCH 2/5] phy: Add UFS PHY modes Vivek Gautam
2017-08-04 6:48 ` [PATCH 3/5] phy: qcom-ufs: Add support to set phy mode Vivek Gautam
2017-08-04 6:48 ` [PATCH 4/5] scsi/ufs: qcom: Set phy mode based on the controllers HS MODE Vivek Gautam
2017-09-26 22:44 ` Subhash Jadavani
2017-09-27 6:31 ` Vivek Gautam
2017-08-04 6:48 ` [PATCH 5/5] ufs/phy: qcom: Refactor to use phy_init call Vivek Gautam
2017-09-26 23:13 ` Subhash Jadavani
2017-09-27 6:21 ` Vivek Gautam
2017-08-08 12:09 ` [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code Kishon Vijay Abraham I
2017-08-08 15:50 ` Vivek Gautam
2017-08-09 5:48 ` Kishon Vijay Abraham I [this message]
2017-08-09 6:44 ` Vivek Gautam
2017-08-11 0:03 ` Martin K. Petersen
2017-08-11 7:12 ` Vivek Gautam
2017-08-14 5:17 ` Asutosh Das (asd)
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=d49316e0-8ccc-21b3-e952-ddb0a941f3b3@ti.com \
--to=kishon@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-arm-msm-owner@vger.kernel.org \
--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=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®