From: Bjorn Andersson <andersson@kernel.org>
To: johan+linaro@kernel.org
Cc: dmitry.baryshkov@linaro.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, vkoul@kernel.org,
konrad.dybcio@somainline.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>
Subject: Re: [PATCH 0/4] arm64: dts: qcom: fix UFS PHY registers
Date: Sun, 6 Nov 2022 21:12:07 -0600 [thread overview]
Message-ID: <166779074265.500303.10223051049432517680.b4-ty@kernel.org> (raw)
In-Reply-To: <20221024091507.20342-1-johan+linaro@kernel.org>
On Mon, 24 Oct 2022 11:15:03 +0200, Johan Hovold wrote:
> When working on the updated QMP binding for SC8280XP, I noticed that the
> UFS PHY register definitions for most platforms are wrong. Apparently
> the register region sizes have just been copied verbatim from the
> original SDM845.
>
> As Linux maps these regions as full pages this is currently not an issue
> on Linux, but let's update the sizes to match the vendor drivers.
>
> [...]
Applied, thanks!
[1/4] arm64: dts: qcom: sm8150: fix UFS PHY registers
commit: 36a31b3a8d9ba1707a23de8d8dc1ceaef4eda695
[2/4] arm64: dts: qcom: sm8250: fix UFS PHY registers
commit: 7f8b37dd4e7bf50160529530d9789b846153df71
[3/4] arm64: dts: qcom: sm8350: fix UFS PHY registers
commit: b3c7839b698cc617e97dd2e4f1eeb4adc280fe58
[4/4] arm64: dts: qcom: sm8450: fix UFS PHY registers
commit: 7af949211a0554bbc06163b081fc2cb516674880
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-11-07 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:15 Johan Hovold
2022-10-24 9:15 ` [PATCH 1/4] arm64: dts: qcom: sm8150: " Johan Hovold
2022-10-24 9:15 ` [PATCH 2/4] arm64: dts: qcom: sm8250: " Johan Hovold
2022-10-24 9:15 ` [PATCH 3/4] arm64: dts: qcom: sm8350: " Johan Hovold
2022-10-24 9:15 ` [PATCH 4/4] arm64: dts: qcom: sm8450: " Johan Hovold
2022-11-07 3:12 ` 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=166779074265.500303.10223051049432517680.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®