From: Dmitry Osipenko <digetx@gmail.com> To: Peter De Schrijver <pdeschrijver@nvidia.com> Cc: Rob Herring <robh+dt@kernel.org>, Thierry Reding <thierry.reding@gmail.com>, Jonathan Hunter <jonathanh@nvidia.com>, Mark Brown <broonie@kernel.org>, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 3/3] soc/tegra: regulators: Add regulators coupler for Tegra30 Date: Mon, 5 Aug 2019 14:03:29 +0300 [thread overview] Message-ID: <1a9464b3-6e0e-00ff-64d8-b3abf7982dfb@gmail.com> (raw) In-Reply-To: <20190805083325.GE3883@pdeschrijver-desktop.Nvidia.com> 05.08.2019 11:33, Peter De Schrijver пишет: > On Fri, Aug 02, 2019 at 05:39:23PM +0300, Dmitry Osipenko wrote: >> 02.08.2019 17:05, Peter De Schrijver пишет: >>> On Thu, Jul 25, 2019 at 06:18:32PM +0300, Dmitry Osipenko wrote: >>>> Add regulators coupler for Tegra30 SoCs that performs voltage balancing >>>> of a coupled regulators and thus provides voltage scaling functionality. >>>> >>>> There are 2 coupled regulators on all Tegra30 SoCs: CORE and CPU. The >>>> coupled regulator voltages shall be in a range of 300mV from each other >>>> and CORE voltage shall be higher than the CPU by N mV, where N depends >>>> on the CPU voltage. >>>> >>>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com> >>>> --- >>>> drivers/soc/tegra/Kconfig | 4 + >>>> drivers/soc/tegra/Makefile | 1 + >>>> drivers/soc/tegra/regulators-tegra30.c | 316 +++++++++++++++++++++++++ >>>> 3 files changed, 321 insertions(+) >>>> create mode 100644 drivers/soc/tegra/regulators-tegra30.c >>>> >>> ... >>> >>>> + >>>> +static int tegra30_core_cpu_limit(int cpu_uV) >>>> +{ >>>> + if (cpu_uV < 800000) >>>> + return 950000; >>>> + >>>> + if (cpu_uV < 900000) >>>> + return 1000000; >>>> + >>>> + if (cpu_uV < 1000000) >>>> + return 1100000; >>>> + >>>> + if (cpu_uV < 1100000) >>>> + return 1200000; >>>> + >>>> + if (cpu_uV < 1250000) { >>>> + switch (tegra_sku_info.cpu_speedo_id) { >>>> + case 0 ... 1: >>> Aren't we supposed to add /* fall through */ here now? >> >> There is no compiler warning if there is nothing in-between of the >> case-switches, so annotation isn't really necessary here. Of course it >> is possible to add an explicit annotation just to make clear the >> fall-through intention. >> > > Ah. Ok. Whatever you want then :) I'll add the comments if there will be a need to re-spin this series. >>>> + case 4: >>>> + case 7 ... 8: >>>> + return 1200000; >>>> + >>>> + default: >>>> + return 1300000; >>>> + } >>>> + } >>>> + >>> >>> Other than that, this looks ok to me. >> >> Awesome, thank you very much! Explicit ACK will be appreciated as well. > > Acked-By: Peter De Schrijver <pdeschrijver@nvidia.com> Thank you again! Could you please also clarify whether the ACK is for this patch only or for all of three patches?
next prev parent reply other threads:[~2019-08-05 11:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-25 15:18 [PATCH v2 0/3] Support regulators coupling on NVIDIA Tegra20/30 Dmitry Osipenko 2019-07-25 15:18 ` [PATCH v2 1/3] dt-bindings: regulator: Document regulators coupling of NVIDIA Tegra20/30 SoCs Dmitry Osipenko 2019-08-02 14:47 ` Dmitry Osipenko 2019-08-16 21:34 ` Rob Herring 2019-07-25 15:18 ` [PATCH v2 2/3] soc/tegra: regulators: Add regulators coupler for Tegra20 Dmitry Osipenko 2019-07-25 15:18 ` [PATCH v2 3/3] soc/tegra: regulators: Add regulators coupler for Tegra30 Dmitry Osipenko 2019-08-02 14:05 ` Peter De Schrijver 2019-08-02 14:39 ` Dmitry Osipenko 2019-08-05 8:33 ` Peter De Schrijver 2019-08-05 11:03 ` Dmitry Osipenko [this message] 2019-08-06 7:30 ` Peter De Schrijver 2019-10-29 13:02 ` [PATCH v2 0/3] Support regulators coupling on NVIDIA Tegra20/30 Thierry Reding
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=1a9464b3-6e0e-00ff-64d8-b3abf7982dfb@gmail.com \ --to=digetx@gmail.com \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=jonathanh@nvidia.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=pdeschrijver@nvidia.com \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.com \ --subject='Re: [PATCH v2 3/3] soc/tegra: regulators: Add regulators coupler for Tegra30' \ /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
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).