From: Viresh Kumar <viresh.kumar@linaro.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH] cpufreq: ti-cpufreq: Add support for OPP_PLUS
Date: Mon, 2 Mar 2020 09:49:33 +0530 [thread overview]
Message-ID: <20200302041933.uuoa5kbvgtde37oq@vireshk-i7> (raw)
In-Reply-To: <20200228144529.14548-1-t-kristo@ti.com>
On 28-02-20, 16:45, Tero Kristo wrote:
> From: Lokesh Vutla <lokeshvutla@ti.com>
>
> DRA762 SoC introduces OPP_PLUS which runs at 1.8GHz. Add
> support for this OPP in ti-cpufreq driver.
>
> Acked-by: Dave Gerlach <d-gerlach@ti.com>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> drivers/cpufreq/ti-cpufreq.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c
> index 557cb513bf7f..d62b6b21325a 100644
> --- a/drivers/cpufreq/ti-cpufreq.c
> +++ b/drivers/cpufreq/ti-cpufreq.c
> @@ -25,11 +25,14 @@
>
> #define DRA7_EFUSE_HAS_OD_MPU_OPP 11
> #define DRA7_EFUSE_HAS_HIGH_MPU_OPP 15
> +#define DRA76_EFUSE_HAS_PLUS_MPU_OPP 18
> #define DRA7_EFUSE_HAS_ALL_MPU_OPP 23
> +#define DRA76_EFUSE_HAS_ALL_MPU_OPP 24
>
> #define DRA7_EFUSE_NOM_MPU_OPP BIT(0)
> #define DRA7_EFUSE_OD_MPU_OPP BIT(1)
> #define DRA7_EFUSE_HIGH_MPU_OPP BIT(2)
> +#define DRA76_EFUSE_PLUS_MPU_OPP BIT(3)
>
> #define OMAP3_CONTROL_DEVICE_STATUS 0x4800244C
> #define OMAP3_CONTROL_IDCODE 0x4830A204
> @@ -80,6 +83,9 @@ static unsigned long dra7_efuse_xlate(struct ti_cpufreq_data *opp_data,
> */
>
> switch (efuse) {
> + case DRA76_EFUSE_HAS_PLUS_MPU_OPP:
> + case DRA76_EFUSE_HAS_ALL_MPU_OPP:
> + calculated_efuse |= DRA76_EFUSE_PLUS_MPU_OPP;
> case DRA7_EFUSE_HAS_ALL_MPU_OPP:
> case DRA7_EFUSE_HAS_HIGH_MPU_OPP:
> calculated_efuse |= DRA7_EFUSE_HIGH_MPU_OPP;
This is already merged, why sending it again ?
--
viresh
next prev parent reply other threads:[~2020-03-02 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 14:45 [PATCH] cpufreq: ti-cpufreq: Add support for OPP_PLUS Tero Kristo
2020-03-02 4:19 ` Viresh Kumar [this message]
2020-03-02 9:22 ` Tero Kristo
-- strict thread matches above, loose matches on Subject: below --
2020-02-11 7:23 Lokesh Vutla
2020-02-12 4:11 ` Viresh Kumar
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=20200302041933.uuoa5kbvgtde37oq@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=rjw@rjwysocki.net \
--cc=t-kristo@ti.com \
/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).