From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-arm-msm@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 0/2] PCI: qcom: fix PCIe support on sm8250
Date: Tue, 26 Jan 2021 23:11:41 +0300 [thread overview]
Message-ID: <64f62684-523d-cbd5-708b-4c06e7d03954@linaro.org> (raw)
In-Reply-To: <20210117013114.441973-1-dmitry.baryshkov@linaro.org>
Rob, Lorenzo, gracious poke for this patchset.
On 17/01/2021 04:31, Dmitry Baryshkov wrote:
> SM8250 platform requires additional clock to be enabled for PCIe to
> function. In case it is disabled, PCIe access will result in IOMMU
> timeouts. Add device tree binding and driver support for this clock.
>
> Canges since v4:
> - Remove QCOM_PCIE_2_7_0_MAX_CLOCKS define and has_sf_tbu variable.
>
> Changes since v3:
> - Merge clock handling back into qcom_pcie_get_resources_2_7_0().
> Define res->num_clks to the amount of clocks used for this particular
> platform.
>
> Changes since v2:
> - Split this clock handling from qcom_pcie_get_resources_2_7_0()
> - Change comment to point that the clock is required rather than
> optional
>
> Changes since v1:
> - Added Fixes: tags, as respective patches have hit the upstream Linux
> tree.
>
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2021-01-27 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 1:31 [PATCH v5 0/2] PCI: qcom: fix PCIe support on sm8250 Dmitry Baryshkov
2021-01-17 1:31 ` [PATCH v5 1/2] dt-bindings: pci: qcom: Document ddrss_sf_tbu clock for sm8250 Dmitry Baryshkov
2021-01-17 1:31 ` [PATCH v5 2/2] PCI: qcom: add support for ddrss_sf_tbu clock Dmitry Baryshkov
2021-02-05 7:12 ` Stanimir Varbanov
2021-01-26 20:11 ` Dmitry Baryshkov [this message]
2021-02-04 15:06 ` [PATCH v5 0/2] PCI: qcom: fix PCIe support on sm8250 Dmitry Baryshkov
2021-02-04 17:02 ` Lorenzo Pieralisi
2021-02-05 17:10 ` Lorenzo Pieralisi
2021-02-05 17:12 ` Dmitry Baryshkov
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=64f62684-523d-cbd5-708b-4c06e7d03954@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@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).