From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Brian Masney <bmasney@redhat.com>
Cc: linux-arm-msm@vger.kernel.org, agross@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
ahalaney@redhat.com, echanude@redhat.com
Subject: Re: [PATCH] clk: qcom: sc8280xp: add parent to gcc_ufs_phy_axi_clk for sa8540p
Date: Sat, 16 Jul 2022 09:54:43 -0500 [thread overview]
Message-ID: <YtLRM7vQhimGFimN@builder.lan> (raw)
In-Reply-To: <20220623142837.3140680-1-bmasney@redhat.com>
On Thu 23 Jun 09:28 CDT 2022, Brian Masney wrote:
> The sa8540p automotive board has the same SOC as the sc8280xp. In order
> to get the first UFS controller working on the sa8540p,
> GCC_UFS_REF_CLKREF_CLK needs to be setup as a parent to
> GCC_UFS_PHY_AXI_CLK.
>
> This clock name came from the DTS for the downstream MSM 5.4 kernel
> sources for the sa8540p. It also references GCC_UFS_CARD_CLKREF_CLK,
> however that wasn't needed to get the first UFS controller working.
>
> Signed-off-by: Brian Masney <bmasney@redhat.com>
> ---
> I originally added this under GCC_UFS_PHY_PHY_AUX_CLK since that's
> what's in the downstream DTS. I was getting errors about
> GCC_UFS_PHY_AXI_CLK being stuck at off so I moved it there.
>
> Also I don't have access to any documentation for this board so I'm
> hoping that someone with docs access can verify that this is the
> appropriate place to put this.
>
> drivers/clk/qcom/gcc-sc8280xp.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/clk/qcom/gcc-sc8280xp.c b/drivers/clk/qcom/gcc-sc8280xp.c
> index 4b894442fdf5..4639b50da418 100644
> --- a/drivers/clk/qcom/gcc-sc8280xp.c
> +++ b/drivers/clk/qcom/gcc-sc8280xp.c
> @@ -5685,6 +5685,19 @@ static struct clk_branch gcc_ufs_phy_ahb_clk = {
> },
> };
>
> +static struct clk_branch gcc_ufs_ref_clkref_clk = {
> + .halt_reg = 0x8c058,
> + .halt_check = BRANCH_HALT,
> + .clkr = {
> + .enable_reg = 0x8c058,
> + .enable_mask = BIT(0),
> + .hw.init = &(const struct clk_init_data) {
> + .name = "gcc_ufs_ref_clkref_clk",
> + .ops = &clk_branch2_ops,
> + },
> + },
> +};
> +
> static struct clk_branch gcc_ufs_phy_axi_clk = {
> .halt_reg = 0x77010,
> .halt_check = BRANCH_HALT_VOTED,
> @@ -5696,6 +5709,7 @@ static struct clk_branch gcc_ufs_phy_axi_clk = {
> .hw.init = &(const struct clk_init_data) {
> .name = "gcc_ufs_phy_axi_clk",
> .parent_hws = (const struct clk_hw*[]){
> + &gcc_ufs_ref_clkref_clk.clkr.hw,
gcc_ufs_ref_clkref_clk isn't the parent of gcc_ufs_phy_axi_clk.
But I presume that if this works, then you're just enabling the ufs
clkref clock, indirectly. Seems reasonable that you should be specifying
gcc_ufs_ref_clkref_clk as "ref_clk" instead.
Could you please give that a go?
Regards,
Bjorn
> &gcc_ufs_phy_axi_clk_src.clkr.hw,
> },
> .num_parents = 1,
> @@ -5899,19 +5913,6 @@ static struct clk_branch gcc_ufs_phy_unipro_core_hw_ctl_clk = {
> },
> };
>
> -static struct clk_branch gcc_ufs_ref_clkref_clk = {
> - .halt_reg = 0x8c058,
> - .halt_check = BRANCH_HALT,
> - .clkr = {
> - .enable_reg = 0x8c058,
> - .enable_mask = BIT(0),
> - .hw.init = &(const struct clk_init_data) {
> - .name = "gcc_ufs_ref_clkref_clk",
> - .ops = &clk_branch2_ops,
> - },
> - },
> -};
> -
> static struct clk_branch gcc_usb2_hs0_clkref_clk = {
> .halt_reg = 0x8c044,
> .halt_check = BRANCH_HALT,
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-07-16 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 14:28 [PATCH] clk: qcom: sc8280xp: add parent to gcc_ufs_phy_axi_clk for sa8540p Brian Masney
2022-06-23 15:32 ` Andrew Halaney
2022-06-23 17:13 ` Brian Masney
2022-06-24 0:20 ` Stephen Boyd
2022-06-24 16:40 ` Brian Masney
2022-06-24 20:16 ` Stephen Boyd
2022-07-16 14:54 ` Bjorn Andersson [this message]
2022-07-19 18:49 ` Brian Masney
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=YtLRM7vQhimGFimN@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=bmasney@redhat.com \
--cc=echanude@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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).