From: Mikko Perttunen <mperttunen@nvidia.com>
To: Brian Masney <bmasney@redhat.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: Fix Tegra114 MIPI calibration clock parent
Date: Sat, 03 Oct 2026 12:22:48 +0900 [thread overview]
Message-ID: <encGrolPTXOOvSimmmZLIQ@nvidia.com> (raw)
In-Reply-To: <ar_QXessqHKkVAHi@redhat.com>
On Saturday, October 3, 2026 12:40 AM Brian Masney wrote:
> Hi Mikko,
>
> On Wed, Sep 30, 2026 at 02:18:34PM +0900, Mikko Perttunen wrote:
> > CLK_MIPI_CAL on Tegra114 is a plain clock gate with no source mux; the
> > fixed parent is PLL_P_OUT3, which is specified to run at 72 MHz. The
> > clock driver currently registers the gate with clk_m as its parent, so
> > the clock framework never enables PLL_P_OUT3 when MIPI_CAL is enabled,
> > and reports the wrong rate for it.
> >
> > Register the gate with pll_p_out3 as its parent. Also drop
> > CLK_SET_RATE_PARENT at the same time: the parent canonically runs at
> > 72 MHz so we shouldn't change the rate.
> >
> > Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
>
> Should there be a Fixes tag? I see that Thierry made a change to this
> same clock 11 years ago:
>
> commit 07314fc108e195044c074f4b443974b5aaa2d5d7
> Author: Thierry Reding <treding@nvidia.com>
> Date: Wed Apr 8 16:48:26 2015 +0200
>
> clk: tegra: Special-case mipi-cal parent on Tegra114
>
> Starting with Tegra124, the mipi-cal clock uses the 72 MHz clock as its
> source. On Tegra114 this clock's parent was clk_m, so it is the one-off
> chip.
>
> Brian
True, technically this is a fix for that patch. I don't think this patch
warrants any backporting, though, that the tag may trigger. If you'd
prefer I can add the below (or if easier, you can add when applying):
Fixes: 07314fc108e1 ("clk: tegra: Special-case mipi-cal parent on Tegra114")
Thanks
Mikko
>
>
> > ---
> > drivers/clk/tegra/clk-tegra114.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/clk/tegra/clk-tegra114.c b/drivers/clk/tegra/clk-tegra114.c
> > index f1bca81b7776..97f5500b13b5 100644
> > --- a/drivers/clk/tegra/clk-tegra114.c
> > +++ b/drivers/clk/tegra/clk-tegra114.c
> > @@ -1050,8 +1050,8 @@ static __init void tegra114_periph_clk_init(void __iomem *clk_base,
> > &emc_lock);
> > clks[TEGRA114_CLK_MC] = clk;
> >
> > - clk = tegra_clk_register_periph_gate("mipi-cal", "clk_m", 0, clk_base,
> > - CLK_SET_RATE_PARENT, 56,
> > + clk = tegra_clk_register_periph_gate("mipi-cal", "pll_p_out3", 0,
> > + clk_base, 0, 56,
> > periph_clk_enb_refcnt);
> > clks[TEGRA114_CLK_MIPI_CAL] = clk;
> >
> >
> > ---
> > base-commit: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
> > change-id: 20260930-b4-dalmore-fixes-mipical-clk-eb375008dd66
> >
>
>
prev parent reply other threads:[~2026-10-03 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 5:18 Mikko Perttunen
2026-10-02 15:40 ` Brian Masney
2026-10-03 3:22 ` Mikko Perttunen [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=encGrolPTXOOvSimmmZLIQ@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=bmasney+clk@redhat.com \
--cc=bmasney@redhat.com \
--cc=jbrunet+clk@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®