From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
Taniya Das <quic_tdas@quicinc.com>, Vinod Koul <vkoul@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v4 3/3] phy: qcom-qmp-ufs: provide symbol clocks
Date: Thu, 29 Sep 2022 17:56:45 -0700 [thread overview]
Message-ID: <20220930005647.99FE7C433D6@smtp.kernel.org> (raw)
In-Reply-To: <20220916061740.87167-4-dmitry.baryshkov@linaro.org>
Quoting Dmitry Baryshkov (2022-09-15 23:17:40)
> Register three UFS symbol clocks (ufs_rx_symbol_0_clk_src,
> ufs_rx_symbol_1_clk_src ufs_tx_symbol_0_clk_src). Register OF clock
> provider to let other devices link these clocks through the DT.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
The previous two are on clk-fixed-rate branch if you want to pull it.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-09-30 0:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 6:17 [PATCH v4 0/3] phy: qcom-qmp-ufs: add symbol clocks support Dmitry Baryshkov
2022-09-16 6:17 ` [PATCH v4 1/3] clk: asm9260: use parent index to link the reference clock Dmitry Baryshkov
2022-09-24 7:33 ` Dmitry Baryshkov
2022-09-30 0:56 ` Stephen Boyd
2022-09-16 6:17 ` [PATCH v4 2/3] clk: fixed-rate: add devm_clk_hw_register_fixed_rate Dmitry Baryshkov
2022-09-30 0:56 ` Stephen Boyd
2022-09-16 6:17 ` [PATCH v4 3/3] phy: qcom-qmp-ufs: provide symbol clocks Dmitry Baryshkov
2022-09-30 0:56 ` Stephen Boyd [this message]
2022-10-28 12:48 ` Vinod Koul
2022-10-28 12:47 ` Vinod Koul
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=20220930005647.99FE7C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@ti.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_tdas@quicinc.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).