From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com
Cc: robh@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, steev@kali.org,
quic_srichara@quicinc.com
Subject: Re: [PATCH 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0
Date: Sat, 6 May 2023 15:03:04 +0300 [thread overview]
Message-ID: <b204875e-3122-6af1-d9a4-6f57e96e5016@linaro.org> (raw)
In-Reply-To: <56da1bb2-86ea-e31e-15f3-5eb50e3000e1@linaro.org>
On 06/05/2023 14:44, Dmitry Baryshkov wrote:
> On 06/05/2023 10:31, Manivannan Sadhasivam wrote:
>> In the post init sequence of v2.9.0, write access to read only registers
>> are not disabled after updating the registers. Fix it by disabling the
>> access after register update.
>>
>> Fixes: 0cf7c2efe8ac ("PCI: qcom: Add IPQ60xx support")
>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>> ---
>> drivers/pci/controller/dwc/pcie-qcom.c | 3 +++
>> 1 file changed, 3 insertions(+)
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@gmail.com>
>
Of course:
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-05-06 12:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 7:31 [PATCH 0/8] PCI: qcom: Do not advertise hotplug capability Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 1/8] PCI: qcom: Use DWC helpers for modifying the read-only DBI registers Manivannan Sadhasivam
2023-05-06 11:43 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0 Manivannan Sadhasivam
2023-05-06 11:44 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov [this message]
2023-05-06 7:31 ` [PATCH 3/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.7.0 and v1.9.0 Manivannan Sadhasivam
2023-05-06 12:01 ` Dmitry Baryshkov
2023-05-06 12:03 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 4/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and v2.9.0 Manivannan Sadhasivam
2023-05-06 12:01 ` Dmitry Baryshkov
2023-05-06 12:07 ` Dmitry Baryshkov
2023-05-19 12:43 ` Sricharan Ramabadhran
2023-05-06 7:31 ` [PATCH 5/8] PCI: qcom: Do not advertise hotplug capability for IP v2.3.2 Manivannan Sadhasivam
2023-05-06 12:04 ` Dmitry Baryshkov
2023-05-06 14:01 ` Konrad Dybcio
2023-05-08 10:41 ` Manivannan Sadhasivam
2023-05-08 10:25 ` Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 6/8] PCI: qcom: Use post init sequence of IP v2.3.2 for v2.4.0 Manivannan Sadhasivam
2023-05-06 12:08 ` Dmitry Baryshkov
2023-05-06 7:31 ` [PATCH 7/8] PCI: qcom: Do not advertise hotplug capability for IP v1.0.0 Manivannan Sadhasivam
2023-05-06 7:31 ` [PATCH 8/8] PCI: qcom: Do not advertise hotplug capability for IP v2.1.0 Manivannan Sadhasivam
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=b204875e-3122-6af1-d9a4-6f57e96e5016@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=konrad.dybcio@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_srichara@quicinc.com \
--cc=robh@kernel.org \
--cc=steev@kali.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).