From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kw@linux.com, bhelgaas@google.com, 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, dmitry.baryshkov@linaro.org,
Dmitry Baryshkov <dmitry.baryshkov@gmail.com>
Subject: Re: [PATCH v2 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0
Date: Mon, 22 May 2023 10:56:19 +0200 [thread overview]
Message-ID: <ZGsuM8CAv7AtluVx@lpieralisi> (raw)
In-Reply-To: <20230519143117.23875-3-manivannan.sadhasivam@linaro.org>
On Fri, May 19, 2023 at 08:01:11PM +0530, 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>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@gmail.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> drivers/pci/controller/dwc/pcie-qcom.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> index 01795ee7ce45..391a45d1e70a 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> @@ -1136,6 +1136,7 @@ static int qcom_pcie_post_init_2_9_0(struct qcom_pcie *pcie)
> writel(0, pcie->parf + PARF_Q2A_FLUSH);
>
> dw_pcie_dbi_ro_wr_en(pci);
> +
Nit: spurious change.
Lorenzo
> writel(PCIE_CAP_SLOT_VAL, pci->dbi_base + offset + PCI_EXP_SLTCAP);
>
> val = readl(pci->dbi_base + offset + PCI_EXP_LNKCAP);
> @@ -1145,6 +1146,8 @@ static int qcom_pcie_post_init_2_9_0(struct qcom_pcie *pcie)
> writel(PCI_EXP_DEVCTL2_COMP_TMOUT_DIS, pci->dbi_base + offset +
> PCI_EXP_DEVCTL2);
>
> + dw_pcie_dbi_ro_wr_dis(pci);
> +
> for (i = 0; i < 256; i++)
> writel(0, pcie->parf + PARF_BDF_TO_SID_TABLE_N + (4 * i));
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-22 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 14:31 [PATCH v2 0/8] PCI: qcom: Do not advertise hotplug capability Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 1/8] PCI: qcom: Use DWC helpers for modifying the read-only DBI registers Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 2/8] PCI: qcom: Disable write access to read only registers for IP v2.9.0 Manivannan Sadhasivam
2023-05-22 8:56 ` Lorenzo Pieralisi [this message]
2023-05-29 8:55 ` Manivannan Sadhasivam
2023-05-22 13:00 ` Dmitry Baryshkov
2023-05-29 8:56 ` Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 3/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.7.0 and v1.9.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 4/8] PCI: qcom: Do not advertise hotplug capability for IPs v2.3.3 and v2.9.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 5/8] PCI: qcom: Do not advertise hotplug capability for IP v2.3.2 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 6/8] PCI: qcom: Use post init sequence of IP v2.3.2 for v2.4.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 7/8] PCI: qcom: Do not advertise hotplug capability for IP v1.0.0 Manivannan Sadhasivam
2023-05-19 14:31 ` [PATCH v2 8/8] PCI: qcom: Do not advertise hotplug capability for IP v2.1.0 Manivannan Sadhasivam
2023-05-22 9:01 ` [PATCH v2 0/8] PCI: qcom: Do not advertise hotplug capability Lorenzo Pieralisi
2023-05-29 8:58 ` 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=ZGsuM8CAv7AtluVx@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=dmitry.baryshkov@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--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=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