From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: MSM <linux-arm-msm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <andy.gross@linaro.org>
Subject: [RFC PATCH v2 0/4] UFS on APQ8098
Date: Wed, 16 Jan 2019 11:50:20 +0100 [thread overview]
Message-ID: <88e04336-723f-c157-0384-c5054a73e0a4@free.fr> (raw)
Hello,
After weeks (literally!) of poking the system at random, Jeffrey found why UFS
refused to work on APQ8098: we were not setting the load on the vregs.
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 (4):
arm64: dts: qcom: msm8998: Add rpmcc node
arm64: dts: qcom: msm8998: Add UFS nodes
Add regulator-allow-set-load
ufshcd_set_vccq_rail_unused locks up the board
arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 52 +++++++++++++++++
arch/arm64/boot/dts/qcom/msm8998.dtsi | 69 +++++++++++++++++++++++
drivers/scsi/ufs/ufshcd.c | 1 +
3 files changed, 122 insertions(+)
--
2.17.1
next reply other threads:[~2019-01-16 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 10:50 Marc Gonzalez [this message]
2019-01-16 10:53 ` [RFC PATCH v2 1/4] arm64: dts: qcom: msm8998: Add rpmcc node Marc Gonzalez
2019-01-16 10:56 ` [RFC PATCH v2 2/4] arm64: dts: qcom: msm8998: Add UFS nodes Marc Gonzalez
2019-01-16 15:36 ` Jeffrey Hugo
2019-01-21 17:15 ` Marc Gonzalez
2019-01-16 10:58 ` [RFC PATCH v2 3/4] Add regulator-allow-set-load Marc Gonzalez
2019-01-16 11:00 ` [RFC PATCH v2 4/4] ufshcd_set_vccq_rail_unused locks up the board Marc Gonzalez
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=88e04336-723f-c157-0384-c5054a73e0a4@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.