Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: Svyatoslav <clamor95@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 3/3] ARM: tegra: Add DFLL clock support on Tegra 4
Date: Tue, 26 Aug 2025 10:42:04 +0900	[thread overview]
Message-ID: <12734451.O9o76ZdvQC@senjougahara> (raw)
In-Reply-To: <9139A302-ADF6-4E2C-917E-0E0E1D6CBA0A@gmail.com>

On Monday, August 25, 2025 1:26 PM Svyatoslav wrote:
> 25 серпня 2025 р. 07:20:10 GMT+03:00, Mikko Perttunen 
<mperttunen@nvidia.com> пише:
> >On Friday, August 22, 2025 2:19 PM Svyatoslav Ryhel wrote:
> >> пт, 22 серп. 2025 р. о 06:05 Mikko Perttunen <mperttunen@nvidia.com> 
пише:
> >> > On Friday, March 21, 2025 6:55 PM Svyatoslav Ryhel wrote:
> >> > > Add DFLL clock node to common Tegra114 device tree along with clocks
> >> > > property to cpu node.
> >> > > 
> >> > > Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> >> > > ---
> >> > > 
> >> > >  arch/arm/boot/dts/nvidia/tegra114.dtsi | 34
> >> > >  ++++++++++++++++++++++++++
> >> > >  1 file changed, 34 insertions(+)
> >> > > 
> >> > > diff --git a/arch/arm/boot/dts/nvidia/tegra114.dtsi
> >> > > b/arch/arm/boot/dts/nvidia/tegra114.dtsi index
> >> > > 341ec0962460..25d063a47ca5
> >> > > 100644
> >> > > --- a/arch/arm/boot/dts/nvidia/tegra114.dtsi
> >> > > +++ b/arch/arm/boot/dts/nvidia/tegra114.dtsi
> >> > > @@ -4,6 +4,7 @@
> >> > > 
> >> > >  #include <dt-bindings/memory/tegra114-mc.h>
> >> > >  #include <dt-bindings/pinctrl/pinctrl-tegra.h>
> >> > >  #include <dt-bindings/interrupt-controller/arm-gic.h>
> >> > > 
> >> > > +#include <dt-bindings/reset/tegra114-car.h>
> >> > > 
> >> > >  #include <dt-bindings/soc/tegra-pmc.h>
> >> > >  
> >> > >  #include "tegra114-peripherals-opp.dtsi"
> >> > > 
> >> > > @@ -710,6 +711,30 @@ mipi: mipi@700e3000 {
> >> > > 
> >> > >               #nvidia,mipi-calibrate-cells = <1>;
> >> > >       
> >> > >       };
> >> > > 
> >> > > +     dfll: clock@70110000 {
> >> > > +             compatible = "nvidia,tegra114-dfll";
> >> > > +             reg = <0x70110000 0x100>, /* DFLL control */
> >> > > +                   <0x70110000 0x100>, /* I2C output control */
> >> > > +                   <0x70110100 0x100>, /* Integrated I2C controller
> >> > > */
> >> > > +                   <0x70110200 0x100>; /* Look-up table RAM */
> >> > > +             interrupts = <GIC_SPI 62 IRQ_TYPE_LEVEL_HIGH>;
> >> > > +             clocks = <&tegra_car TEGRA114_CLK_DFLL_SOC>,
> >> > > +                      <&tegra_car TEGRA114_CLK_DFLL_REF>,
> >> > > +                      <&tegra_car TEGRA114_CLK_I2C5>;
> >> > > +             clock-names = "soc", "ref", "i2c";
> >> > > +             resets = <&tegra_car TEGRA114_RST_DFLL_DVCO>;
> >> > > +             reset-names = "dvco";
> >> > > +             #clock-cells = <0>;
> >> > > +             clock-output-names = "dfllCPU_out";
> >> > > +             nvidia,sample-rate = <11500>;
> >> > 
> >> > Should this be 12500? That would match Tegra124 and a downstream kernel
> >> > for
> >> > Tegra114 I have.
> >> 
> >> I referred to tegratab and macallan boards in 3.4 kernel which give
> >> 11500, maybe sample-rate was changed to 12500 later with tegra124
> >> addition?
> >
> >That's interesting. I was looking at the public roth (Shield Portable)
> >kernel, which does not support Tegra124. I checked the L4T r17 release
> >now, and it seems it's a newer version, where the sample rate has been
> >changed to 11500 on some boards due to a voltage undershoot issue with
> >vdd_cpu on macallan/ tegratab [1].
> >
> >So on macallan/tegratab, the vdd_cpu (smps123) ramp rate should be set to
> >2.5mV/us and sample-rate to 11500, while on other boards it can be 5mV/us
> >with 12500 for faster ramping.
> >
> >[1] https://nv-tegra.nvidia.com/r/plugins/gitiles/linux-2.6/+/
> >b92cab2d4cb6379aeded80adc4c5d0708c3f038e%5E%21/#F0
> >
> >Cheers,
> >Mikko
> 
> So should I stick with 11500 as a safer, acceptable for every t114 option?

I think it'd make sense to just put it in each board file separately. T124 DTs 
already seem to be doing that in addition to the main file.

> 
> >> > > +             nvidia,droop-ctrl = <0x00000f00>;
> >> > > +             nvidia,force-mode = <1>;
> >> > > +             nvidia,cf = <10>;
> >> > > +             nvidia,ci = <0>;
> >> > > +             nvidia,cg = <2>;
> >> > > +             status = "disabled";
> >> > > +     };
> >> > > +
> >> > > 
> >> > >       mmc@78000000 {
> >> > >       
> >> > >               compatible = "nvidia,tegra114-sdhci";
> >> > >               reg = <0x78000000 0x200>;
> >> > > 
> >> > > @@ -841,6 +866,15 @@ cpu@0 {
> >> > > 
> >> > >                       device_type = "cpu";
> >> > >                       compatible = "arm,cortex-a15";
> >> > >                       reg = <0>;
> >> > > 
> >> > > +
> >> > > +                     clocks = <&tegra_car TEGRA114_CLK_CCLK_G>,
> >> > > +                              <&tegra_car TEGRA114_CLK_CCLK_LP>,
> >> > > +                              <&tegra_car TEGRA114_CLK_PLL_X>,
> >> > > +                              <&tegra_car TEGRA114_CLK_PLL_P>,
> >> > > +                              <&dfll>;
> >> > > +                     clock-names = "cpu_g", "cpu_lp", "pll_x",
> >> > > "pll_p",
> >> > 
> >> > "dfll";
> >> > 
> >> > > +                     /* FIXME: what's the actual transition time? */
> >> > > +                     clock-latency = <300000>;
> >> > > 
> >> > >               };
> >> > >               
> >> > >               cpu@1 {





      reply	other threads:[~2025-08-26  1:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  9:55 [PATCH v1 0/3] clk: tegra: add DFLL support for Tegra 4 Svyatoslav Ryhel
2025-03-21  9:55 ` [PATCH v1 1/3] drivers: cpufreq: add Tegra 4 support Svyatoslav Ryhel
2025-06-10 11:09   ` Thierry Reding
2025-08-11  8:08     ` Svyatoslav Ryhel
2025-08-22  2:58   ` Mikko Perttunen
2025-08-22  5:21     ` Svyatoslav Ryhel
2025-08-25  3:56       ` Mikko Perttunen
2025-03-21  9:55 ` [PATCH v1 2/3] drivers: clk: tegra: add DFLL support for Tegra 4 Svyatoslav Ryhel
2025-03-21 20:50   ` Krzysztof Kozlowski
2025-05-03  8:54     ` Svyatoslav Ryhel
2025-05-04 16:23       ` Krzysztof Kozlowski
2025-05-04 16:25         ` Svyatoslav Ryhel
2025-05-04 17:11           ` Krzysztof Kozlowski
2025-05-04 17:30             ` Svyatoslav Ryhel
2025-05-04 17:33               ` Krzysztof Kozlowski
2025-06-10 11:07     ` Thierry Reding
2025-06-18  9:13       ` Krzysztof Kozlowski
2025-07-09 15:10         ` Thierry Reding
2025-03-25 18:56   ` Stephen Boyd
2025-03-25 19:00     ` Svyatoslav Ryhel
2025-08-22  2:53   ` Mikko Perttunen
2025-03-21  9:55 ` [PATCH v1 3/3] ARM: tegra: Add DFLL clock support on " Svyatoslav Ryhel
2025-08-22  3:05   ` Mikko Perttunen
2025-08-22  5:19     ` Svyatoslav Ryhel
2025-08-25  4:20       ` Mikko Perttunen
2025-08-25  4:26         ` Svyatoslav
2025-08-26  1:42           ` 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=12734451.O9o76ZdvQC@senjougahara \
    --to=mperttunen@nvidia.com \
    --cc=clamor95@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=rafael@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=viresh.kumar@linaro.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