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>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org
Subject: [PATCH v6 0/4] qcom: add support for PCIe on SM8450 platform
Date: Wed, 23 Feb 2022 13:14:31 +0300 [thread overview]
Message-ID: <20220223101435.447839-1-dmitry.baryshkov@linaro.org> (raw)
There are two different PCIe controllers and PHYs on SM8450, one having
one lane and another with two lanes. Add support for both PCIe
controllers
Changes since v5:
- Rebase on 5.17-rc1
- Drop external dependencies. The pipe_clk rework takes too much time
to be reviewed. SM8450 works with the current pipe_clk multiplexing
code. Fixing pipe_clk will be handled separately.
- Drop interconnect support. It will be handled separately for all
generations requiring interconnect usage.
Changes since v4:
- Add PCIe1 support
- Change binding accordingly, to use qcom,pcie-sm8450-pcie0 and
qcom,pcie-sm8450-pcie1 compatibility strings
- Rebase on top of (pending) pipe_clock cleanup/rework patchset
Changes since v3:
- Fix pcie gpios to follow defined schema as noted by Rob
- Fix commit message according to Bjorn's suggestions
Changes since v2:
- Remove unnecessary comment in struct qcom_pcie_cfg
Changes since v1:
- Fix capitalization/wording of PCI patch subjects
- Add missing gen3x1 specification to PHY table names
Dmitry Baryshkov (4):
dt-bindings: pci: qcom: Document PCIe bindings for SM8450
PCI: qcom: Remove redundancy between qcom_pcie and qcom_pcie_cfg
PCI: qcom: Add ddrss_sf_tbu flag
PCI: qcom: Add SM8450 PCIe support
.../devicetree/bindings/pci/qcom,pcie.txt | 22 ++++-
drivers/pci/controller/dwc/pcie-qcom.c | 93 ++++++++++++-------
2 files changed, 83 insertions(+), 32 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-23 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:14 Dmitry Baryshkov [this message]
2022-02-23 10:14 ` [PATCH v6 1/4] dt-bindings: pci: qcom: Document PCIe bindings for SM8450 Dmitry Baryshkov
2022-02-23 10:14 ` [PATCH v6 2/4] PCI: qcom: Remove redundancy between qcom_pcie and qcom_pcie_cfg Dmitry Baryshkov
2022-02-23 10:14 ` [PATCH v6 3/4] PCI: qcom: Add ddrss_sf_tbu flag Dmitry Baryshkov
2022-02-23 10:14 ` [PATCH v6 4/4] PCI: qcom: Add SM8450 PCIe support Dmitry Baryshkov
2022-02-23 10:37 ` [PATCH v6 0/4] qcom: add support for PCIe on SM8450 platform Stanimir Varbanov
2022-02-23 10:57 ` Lorenzo Pieralisi
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=20220223101435.447839-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.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;
as well as URLs for NNTP newsgroup(s).