From: Vinod Koul <vkoul@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/16] phy: qcom-qmp-pcie: add support for sc8280xp
Date: Thu, 10 Nov 2022 12:35:13 +0530 [thread overview]
Message-ID: <Y2yiqflyAXgVgZXG@matsya> (raw)
In-Reply-To: <20221105145939.20318-1-johan+linaro@kernel.org>
On 05-11-22, 15:59, Johan Hovold wrote:
> This series adds support for the PCIe PHYs on SC8280XP including its
> four-lane PHYs.
>
> The first half of the series clean up the driver in preparation for
> supporting SC8280XP and its new devicetree bindings that drops the
> legacy child node and the (incomplete) description of register
> subregions.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-11-10 7:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 14:59 [PATCH v5 00/16] phy: qcom-qmp-pcie: add support for sc8280xp Johan Hovold
2022-11-05 14:59 ` [PATCH v5 01/16] phy: qcom-qmp-pcie: sort device-id table Johan Hovold
2022-11-05 14:59 ` [PATCH v5 02/16] phy: qcom-qmp-pcie: move " Johan Hovold
2022-11-05 14:59 ` [PATCH v5 03/16] phy: qcom-qmp-pcie: merge driver data Johan Hovold
2022-11-05 14:59 ` [PATCH v5 04/16] phy: qcom-qmp-pcie: clean up device-tree parsing Johan Hovold
2022-11-05 14:59 ` [PATCH v5 05/16] phy: qcom-qmp-pcie: clean up probe initialisation Johan Hovold
2022-11-05 14:59 ` [PATCH v5 06/16] phy: qcom-qmp-pcie: rename PHY ops structure Johan Hovold
2022-11-05 14:59 ` [PATCH v5 07/16] phy: qcom-qmp-pcie: clean up PHY lane init Johan Hovold
2022-11-05 14:59 ` [PATCH v5 08/16] phy: qcom-qmp-pcie: use shorter tables identifiers Johan Hovold
2022-11-05 21:39 ` Dmitry Baryshkov
2022-11-05 14:59 ` [PATCH v5 09/16] phy: qcom-qmp-pcie: add register init helper Johan Hovold
2022-11-05 14:59 ` [PATCH v5 10/16] dt-bindings: phy: qcom,qmp-pcie: rename current bindings Johan Hovold
2022-11-05 14:59 ` [PATCH v5 11/16] dt-bindings: phy: qcom,qmp-pcie: add sc8280xp bindings Johan Hovold
2022-11-05 14:59 ` [PATCH v5 12/16] phy: qcom-qmp-pcie: restructure PHY creation Johan Hovold
2022-11-05 14:59 ` [PATCH v5 13/16] phy: qcom-qmp-pcie: fix initialisation reset Johan Hovold
2022-11-05 14:59 ` [PATCH v5 14/16] phy: qcom-qmp-pcie: add support for pipediv2 clock Johan Hovold
2022-11-05 14:59 ` [PATCH v5 15/16] phy: qcom-qmp-pcie: add support for sc8280xp Johan Hovold
2022-11-05 14:59 ` [PATCH v5 16/16] phy: qcom-qmp-pcie: add support for sc8280xp 4-lane PHYs Johan Hovold
2022-11-10 7:05 ` Vinod Koul [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=Y2yiqflyAXgVgZXG@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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).