From: Bjorn Andersson <andersson@kernel.org>
To: robh+dt@kernel.org, konrad.dybcio@somainline.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, kishon@kernel.org,
dmitry.baryshkov@linaro.org, devicetree@vger.kernel.org,
Christian Marangi <ansuelsmth@gmail.com>,
Andy Gross <agross@kernel.org>,
vkoul@kernel.org, linux-phy@lists.infradead.org
Cc: robimarko@gmail.com
Subject: Re: (subset) [PATCH 1/2] phy: qcom-qmp-pcie: split pcs_misc init cfg for ipq8074 pcs table
Date: Tue, 6 Dec 2022 12:18:46 -0600 [thread overview]
Message-ID: <167035076325.3155086.2621246704414752041.b4-ty@kernel.org> (raw)
In-Reply-To: <20221103212125.17156-1-ansuelsmth@gmail.com>
On Thu, 3 Nov 2022 22:21:24 +0100, Christian Marangi wrote:
> Commit af6643242d3a ("phy: qcom-qmp-pcie: split pcs_misc region for ipq6018
> pcie gen3") reworked the pcs regs values and removed the 0x400 offset
> for each pcs_misc regs.
>
> This change caused the malfunction of ipq8074 downstream since it still
> has the legacy pcs table where pcs_misc are not placed on a different
> table and instead put together assuming the offset of 0x400 for the
> related pcs_misc regs.
>
> [...]
Applied, thanks!
[2/2] arm64: dts: qcom: ipq6018: improve pcie phy pcs reg table
commit: 08f399a818b0eff552b1f23c3171950a58aea78f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-12-06 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 21:21 Christian Marangi
2022-11-03 21:21 ` [PATCH 2/2] arm64: dts: qcom: ipq6018: improve pcie phy pcs reg table Christian Marangi
2022-11-10 7:08 ` Vinod Koul
2022-11-10 7:08 ` [PATCH 1/2] phy: qcom-qmp-pcie: split pcs_misc init cfg for ipq8074 pcs table Vinod Koul
2022-12-06 18:18 ` 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=167035076325.3155086.2621246704414752041.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@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=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--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®