From: patchwork-bot+linux-arm-msm@kernel.org
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v5 0/2] PCI: qcom: fix PCIe support on sm8250
Date: Mon, 01 Mar 2021 19:59:44 +0000 [thread overview]
Message-ID: <161462878430.6187.18226186591276898489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210117013114.441973-1-dmitry.baryshkov@linaro.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Sun, 17 Jan 2021 04:31:12 +0300 you 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.
>
> [...]
Here is the summary with links:
- [v5,1/2] dt-bindings: pci: qcom: Document ddrss_sf_tbu clock for sm8250
https://git.kernel.org/qcom/c/c9f04600026f
- [v5,2/2] PCI: qcom: add support for ddrss_sf_tbu clock
https://git.kernel.org/qcom/c/7081556f81f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:52 UTC|newest]
Thread overview: 10+ 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 ` [PATCH v5 0/2] PCI: qcom: fix PCIe support on sm8250 Dmitry Baryshkov
2021-02-04 15:06 ` Dmitry Baryshkov
2021-02-04 17:02 ` Lorenzo Pieralisi
2021-02-05 17:10 ` Lorenzo Pieralisi
2021-02-05 17:12 ` Dmitry Baryshkov
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878430.6187.18226186591276898489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.