linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: ti-cpufreq: Support additional am43xx platforms
Date: Tue, 19 Sep 2017 15:38:22 -0700	[thread overview]
Message-ID: <20170919223822.GE30848@ubuntu> (raw)
In-Reply-To: <20170919200613.31625-1-d-gerlach@ti.com>

On 19-09-17, 15:06, Dave Gerlach wrote:
> Rather than letting the ti-cpufreq driver match against 'ti,am4372'
> machine compatible during probe let's match against 'ti,am43' so that we
> can support both 'ti,am4372' and 'ti,am438x' platforms which both match
> to this compatible.
> 
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
>  drivers/cpufreq/ti-cpufreq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c
> index b29cd3398463..4bf47de6101f 100644
> --- a/drivers/cpufreq/ti-cpufreq.c
> +++ b/drivers/cpufreq/ti-cpufreq.c
> @@ -190,7 +190,7 @@ static int ti_cpufreq_setup_syscon_register(struct ti_cpufreq_data *opp_data)
>  
>  static const struct of_device_id ti_cpufreq_of_match[] = {
>  	{ .compatible = "ti,am33xx", .data = &am3x_soc_data, },
> -	{ .compatible = "ti,am4372", .data = &am4x_soc_data, },
> +	{ .compatible = "ti,am43", .data = &am4x_soc_data, },
>  	{ .compatible = "ti,dra7", .data = &dra7_soc_data },
>  	{},
>  };

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

      reply	other threads:[~2017-09-19 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 20:06 [PATCH] cpufreq: ti-cpufreq: Support additional am43xx platforms Dave Gerlach
2017-09-19 22:38 ` Viresh Kumar [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=20170919223822.GE30848@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).