From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Johan Hovold <johan@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v8 0/4] phy: qcom-qmp-ufs: add symbol clocks support
Date: Wed, 23 Nov 2022 12:43:45 +0200 [thread overview]
Message-ID: <e7635cc4-a436-11f0-1ea6-46f0056e403c@linaro.org> (raw)
In-Reply-To: <20221123104215.3414528-1-dmitry.baryshkov@linaro.org>
On 23/11/2022 12:42, Dmitry Baryshkov wrote:
> Register UFS symbol clocks in the Qualcomm QMP PHY driver. Some of the
> platforms (msm8996, sc7280, sm8350/sm8450) expect them to be defined (to
> be used as GCC clock parents).
>
> Changes since v7:
> - Rebased on top of phy/next
> - Renamed the clock registration function (Johan)
> - Dropped rogue qcom_qmp_ufs_ops (Johan)
> - Fixed the comment following Johan's suggestion.
Ugh, this went total crazy with me sending the patches from the wrong
commit. Please excuse me, I'll send v9 instead.
--
With best wishes
Dmitry
prev parent reply other threads:[~2022-11-23 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 10:42 [PATCH v8 0/4] phy: qcom-qmp-ufs: add symbol clocks support Dmitry Baryshkov
2022-11-23 10:42 ` [PATCH v8 1/4] dt-bindings: phy: renesas: Document Renesas Ethernet SERDES Dmitry Baryshkov
2022-11-23 10:42 ` [PATCH v8 2/4] phy: renesas: Add Renesas Ethernet SERDES driver for R-Car S4-8 Dmitry Baryshkov
2022-11-23 10:42 ` [PATCH v8 3/4] dt-bindings: phy: qcom,*-qmp-ufs-phy: add clock-cells property Dmitry Baryshkov
2022-11-23 10:42 ` [PATCH v8 4/4] phy: qcom-qmp-ufs: provide symbol clocks Dmitry Baryshkov
2022-11-23 10:43 ` Dmitry Baryshkov [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=e7635cc4-a436-11f0-1ea6-46f0056e403c@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--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).