From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: MSM <linux-arm-msm@vger.kernel.org>,
SCSI <linux-scsi@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
LKML <linux-kernel@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v5 0/3] UFS on APQ8098/MSM8998
Date: Tue, 26 Mar 2019 23:16:56 -0700 [thread overview]
Message-ID: <20190327061656.GL27005@builder> (raw)
In-Reply-To: <43768d77-80b7-9cdc-b6e0-08ec4a026c21@free.fr>
On Mon 25 Feb 04:16 PST 2019, Marc Gonzalez wrote:
> Hello,
>
> This series adds support for the UFS host controller on APQ8098/MSM8998-based boards.
>
> This should be the final rev ;-)
>
> Differences between v4 and v5:
> - Drop patches that have already been accepted or spun off
>
> Differences between v3 and v4:
> - Rebase on top of -next
> - Pick up Douglas Anderson's UFSHC doc fix
> - Document 8998 UFSHC binding
> - Improve UFS PHY binding doc
> - Put the UFS DT patch at the end of the series
>
> Difference between v2 and v3:
> - Add qcom,msm8998-qmp-ufs-phy compat string and match it in the PHY driver
> - Drop vdd-hba-fixed-regulator
> - Write the reg addresses with full 32-bit width
> - Set regulator-allow-set-load only on the 3 rails used by UFS.
> - Revert the patch introducing ufshcd_set_vccq_rail_unused
>
> Difference between v1 and v2:
> - New patch to add 'regulator-allow-set-load' prop to all vreg nodes
> - Rename rpmcc node to 'clock-controller' + Add Review tags
> - Drop UFS pinctrl gymnastics (not required, probably left enabled in bootloader)
> - Delete GCC_UFS_ICE_CORE_CLK (ICE not used upstream, I think)
> - Fix sizes of ufsphy register areas based on Jeffrey's feedback
> - Hack ufshcd_set_vccq_rail_unused into a NOP to work around lock up + reboot
>
>
> Marc Gonzalez (3):
> dt-bindings: ufs: Add msm8998 compatible string
> arm64: dts: qcom: msm8998: Allow UFSHC driver to set-load
> arm64: dts: qcom: msm8998: Add UFS nodes
>
Picked up with Lee's tested-by.
Thanks,
Bjorn
> .../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 1 +
> arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 22 +++++++
> arch/arm64/boot/dts/qcom/msm8998.dtsi | 65 +++++++++++++++++++
> 3 files changed, 88 insertions(+)
>
> --
> 2.17.1
next prev parent reply other threads:[~2019-03-27 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 12:16 [PATCH v5 0/3] UFS on APQ8098/MSM8998 Marc Gonzalez
2019-02-25 12:17 ` [PATCH v5 1/3] dt-bindings: ufs: Add msm8998 compatible string Marc Gonzalez
2019-02-25 12:17 ` [PATCH v5 2/3] arm64: dts: qcom: msm8998: Allow UFSHC driver to set-load Marc Gonzalez
2019-02-25 12:18 ` [PATCH v5 3/3] arm64: dts: qcom: msm8998: Add UFS nodes Marc Gonzalez
2019-02-26 8:22 ` [PATCH v5 0/3] UFS on APQ8098/MSM8998t Lee Jones
2019-03-25 12:05 ` [PATCH v5 0/3] UFS on APQ8098/MSM8998 Marc Gonzalez
2019-03-27 6:16 ` Bjorn Andersson [this message]
2019-03-28 9:37 ` Sibi Sankar
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=20190327061656.GL27005@builder \
--to=bjorn.andersson@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andy.gross@linaro.org \
--cc=avri.altman@wdc.com \
--cc=david.brown@linaro.org \
--cc=jhugo@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=pedrom.sousa@synopsys.com \
/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;
as well as URLs for NNTP newsgroup(s).