Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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>
From:   Marc Gonzalez <marc.w.gonzalez@free.fr>
Subject: [RFC PATCH v2 0/4] UFS on APQ8098
Message-ID: <88e04336-723f-c157-0384-c5054a73e0a4@free.fr>
Date:   Wed, 16 Jan 2019 11:50:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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