From: cang@codeaurora.org
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: dianders@chromium.org, subhashj@codeaurora.org,
asutoshd@codeaurora.org, vivek.gautam@codeaurora.org,
evgreen@chromium.org, rnayak@codeaurora.org,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Venkat Gopalakrishnan <venkatg@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/1] scsi: ufs: make UFS Tx lane1 clock optional for QCOM platforms
Date: Tue, 16 Oct 2018 12:05:00 +0800 [thread overview]
Message-ID: <98938b7462e2a90e1b2089d6c6706c52@codeaurora.org> (raw)
In-Reply-To: <yq1ftx6wqeh.fsf@oracle.com>
Hi Martin,
On 2018-10-16 10:56, Martin K. Petersen wrote:
> Can,
>
>> Per Qcom's UFS host controller HW design, the UFS Tx lane1 clock could
>> be muxed with Tx lane0 clock, hence keep Tx lane1 clock optional by
>> ignoring it if it is not provided in device tree. This change also
>> performs some cleanup to lanes per direction checks when
>> enable/disable lane clocks just for symmetry.
>
> Applied to 4.20/scsi-queue, thanks!
Thanks a lot!
-Can Guo
prev parent reply other threads:[~2018-10-16 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 2:25 [PATCH v5 1/1] scsi: ufs: make UFS Tx lane1 clock optional for QCOM platforms Can Guo
2018-10-13 2:25 ` Can Guo
2018-10-16 2:56 ` Martin K. Petersen
2018-10-16 2:56 ` Martin K. Petersen
2018-10-16 4:05 ` cang [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=98938b7462e2a90e1b2089d6c6706c52@codeaurora.org \
--to=cang@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--cc=dianders@chromium.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=rnayak@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=venkatg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.