All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Rajendra Nayak" <rnayak@ti.com>,
	"Kevin Hilman" <khilman@linaro.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Rob Herring" <robherring2@gmail.com>,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	"Paul Walmsley" <paul@pwsan.com>,
	"Benoît Cousson" <b-cousson@ti.com>,
	"Jon Hunter" <jon-hunter@ti.com>, Keerthy <j-keerthy@ti.com>,
	"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
	"Shawn Guo" <shawn.guo@linaro.org>
Subject: Re: [PATCH V3 1/2] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot
Date: Fri, 5 Apr 2013 12:28:30 -0700	[thread overview]
Message-ID: <20130405192829.GE10155@atomide.com> (raw)
In-Reply-To: <20130405171750.GA7398@kahuna>

* Nishanth Menon <nm@ti.com> [130405 10:22]:
> On 10:05-20130405, Tony Lindgren wrote:
> > 
> > > diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c
> > > index afa509a..5b147ef 100644
> > > --- a/arch/arm/mach-omap2/board-generic.c
> > > +++ b/arch/arm/mach-omap2/board-generic.c
> > > @@ -49,6 +49,11 @@ static void __init omap_generic_init(void)
> > >  		omap4_panda_display_init_of();
> > >  	else if (of_machine_is_compatible("ti,omap4-sdp"))
> > >  		omap_4430sdp_display_init_of();
> > > +
> > > +	if (IS_ENABLED(CONFIG_GENERIC_CPUFREQ_CPU0)) {
> > > +		struct platform_device_info devinfo = { .name = "cpufreq-cpu0", };
> > > +		platform_device_register_full(&devinfo);
> > > +	}
> > >  }
> > 
> > Hmm why would the driver need this? Sounds like the driver is
> > missing support for DT?
> Nope, this was a long chain of discussion in previous iterations of this
> patch.. more or less started here:
> https://patchwork.kernel.org/patch/2251821/
> Suggested as the generic approach for cpufreq drivers.
> Paul questioned this approach in:
> http://marc.info/?l=linux-pm&m=136485349218809&w=2

How about just set it up in omap2_common_pm_init instead
of the board-generic?

Regards,

Tony

  reply	other threads:[~2013-04-05 19:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 21:52 [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-03-28 21:52 ` Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 1/2] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-03-28 21:52   ` Nishanth Menon
2013-04-03 18:47   ` Kevin Hilman
2013-04-03 18:47     ` Kevin Hilman
2013-04-04  2:52     ` Nishanth Menon
2013-04-04  5:13       ` Rajendra Nayak
2013-04-04 19:00         ` Nishanth Menon
2013-04-05  9:50           ` Rajendra Nayak
2013-04-05 11:26             ` Nishanth Menon
2013-04-05 16:13               ` Tony Lindgren
2013-04-05 16:32                 ` Nishanth Menon
2013-04-05 17:05                   ` Tony Lindgren
2013-04-05 17:17                     ` Nishanth Menon
2013-04-05 19:28                       ` Tony Lindgren [this message]
2013-04-05 20:02                         ` Nishanth Menon
2013-04-05 21:10                           ` Tony Lindgren
2013-04-05 21:32                             ` Nishanth Menon
2013-04-05 21:40                               ` Tony Lindgren
2013-04-05 22:10                                 ` Nishanth Menon
2013-04-05 22:17                                   ` Tony Lindgren
2013-04-05 22:23                                     ` Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 2/2] cpufreq: OMAP: instantiate omap-cpufreq as a platform_driver Nishanth Menon
2013-03-28 21:52   ` Nishanth Menon
2013-03-29  2:59   ` Viresh Kumar
2013-04-05 17:07     ` Nishanth Menon
2013-04-05 21:34       ` Kevin Hilman
2013-04-05 21:34         ` Kevin Hilman
2013-04-05 21:36         ` Nishanth Menon
2013-04-03 17:47 ` [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Kevin Hilman
2013-04-03 18:22   ` Nishanth Menon

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=20130405192829.GE10155@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=khilman@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=paul@pwsan.com \
    --cc=rnayak@ti.com \
    --cc=robherring2@gmail.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=shawn.guo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.