devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Can Guo <cang@codeaurora.org>
Subject: Re: [PATCH 0/3] arm64: dts: qcom: UFS updates
Date: Sun, 5 Jan 2020 23:35:13 -0800	[thread overview]
Message-ID: <20200106073513.GS3755841@builder> (raw)
In-Reply-To: <20200106070826.147064-1-vkoul@kernel.org>

On Sun 05 Jan 23:08 PST 2020, Vinod Koul wrote:

> We recently saw regression on UFS on SM8150 and few other boards and that
> was resolved by adding timeout and fixing the UFS phy reset sequence. That
> patches are in linux-next now.
> 
> During this we found sm8150 lacks gpio reset for ufs, so add that and fix
> the ufs phy register size.
> Also add the sdm845 ufs reset.
> 

Thanks Vinod, boot tested and merged.

> Vinod Koul (3):
>   arm64: dts: qcom: sm8150-mtp: Add UFS gpio reset
>   arm64: dts: qcom: sm8150: Fix UFS phy register size
>   arm64: dts: qcom: sdm845: add the ufs reset
> 
>  arch/arm64/boot/dts/qcom/sdm845.dtsi    | 2 ++
>  arch/arm64/boot/dts/qcom/sm8150-mtp.dts | 3 +++
>  arch/arm64/boot/dts/qcom/sm8150.dtsi    | 2 +-
>  3 files changed, 6 insertions(+), 1 deletion(-)
> 
> -- 
> 2.24.1
> 

      parent reply	other threads:[~2020-01-06  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  7:08 [PATCH 0/3] arm64: dts: qcom: UFS updates Vinod Koul
2020-01-06  7:08 ` [PATCH 1/3] arm64: dts: qcom: sm8150-mtp: Add UFS gpio reset Vinod Koul
2020-01-06  7:08 ` [PATCH 2/3] arm64: dts: qcom: sm8150: Fix UFS phy register size Vinod Koul
2020-01-06  7:08 ` [PATCH 3/3] arm64: dts: qcom: sdm845: add the ufs reset Vinod Koul
2020-01-06  7:35 ` Bjorn Andersson [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=20200106073513.GS3755841@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=cang@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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 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).