| Message ID | 1411738864-26549-6-git-send-email-l.stach@pengutronix.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Fri, Sep 26, 2014 at 03:41:04PM +0200, Lucas Stach wrote: > Instanciate device for the generic cpufreq-dt driver. > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de> I assume that I should only apply this patch after the cpufreq-dt change gets merged and shows up on my base. Shawn > --- > v2: > - new patch, split out from DTS changes and rebased > with new name for cpufreq driver > --- > arch/arm/mach-imx/mach-imx53.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm/mach-imx/mach-imx53.c b/arch/arm/mach-imx/mach-imx53.c > index 03dd6ea13acc..7587cf0cba3e 100644 > --- a/arch/arm/mach-imx/mach-imx53.c > +++ b/arch/arm/mach-imx/mach-imx53.c > @@ -41,6 +41,8 @@ static void __init imx53_dt_init(void) > static void __init imx53_init_late(void) > { > imx53_pm_init(); > + > + platform_device_register_simple("cpufreq-dt", -1, NULL, 0); > } > > static const char * const imx53_dt_board_compat[] __initconst = { > -- > 2.1.0 >
Am Sonntag, den 28.09.2014, 12:15 +0800 schrieb Shawn Guo: > On Fri, Sep 26, 2014 at 03:41:04PM +0200, Lucas Stach wrote: > > Instanciate device for the generic cpufreq-dt driver. > > > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de> > > I assume that I should only apply this patch after the cpufreq-dt change > gets merged and shows up on my base. > > Shawn > I would think its safe to merge this patch. The cpufreq-dt change will be merged with 3.18. Until then the worst that could happen is that the cpufreq driver doesn't bind to the mx5 cpu device. > > --- > > v2: > > - new patch, split out from DTS changes and rebased > > with new name for cpufreq driver > > --- > > arch/arm/mach-imx/mach-imx53.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/arch/arm/mach-imx/mach-imx53.c b/arch/arm/mach-imx/mach-imx53.c > > index 03dd6ea13acc..7587cf0cba3e 100644 > > --- a/arch/arm/mach-imx/mach-imx53.c > > +++ b/arch/arm/mach-imx/mach-imx53.c > > @@ -41,6 +41,8 @@ static void __init imx53_dt_init(void) > > static void __init imx53_init_late(void) > > { > > imx53_pm_init(); > > + > > + platform_device_register_simple("cpufreq-dt", -1, NULL, 0); > > } > > > > static const char * const imx53_dt_board_compat[] __initconst = { > > -- > > 2.1.0 > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-pm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Sep 29, 2014 at 10:33:48AM +0200, Lucas Stach wrote: > Am Sonntag, den 28.09.2014, 12:15 +0800 schrieb Shawn Guo: > > On Fri, Sep 26, 2014 at 03:41:04PM +0200, Lucas Stach wrote: > > > Instanciate device for the generic cpufreq-dt driver. > > > > > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de> > > > > I assume that I should only apply this patch after the cpufreq-dt change > > gets merged and shows up on my base. > > > > Shawn > > > I would think its safe to merge this patch. The cpufreq-dt change will > be merged with 3.18. Until then the worst that could happen is that the > cpufreq driver doesn't bind to the mx5 cpu device. Ah, right. The device will not bind on my tree, so it's safe to apply it right away. Applied, thanks.
diff --git a/arch/arm/mach-imx/mach-imx53.c b/arch/arm/mach-imx/mach-imx53.c index 03dd6ea13acc..7587cf0cba3e 100644 --- a/arch/arm/mach-imx/mach-imx53.c +++ b/arch/arm/mach-imx/mach-imx53.c @@ -41,6 +41,8 @@ static void __init imx53_dt_init(void) static void __init imx53_init_late(void) { imx53_pm_init(); + + platform_device_register_simple("cpufreq-dt", -1, NULL, 0); } static const char * const imx53_dt_board_compat[] __initconst = {
Instanciate device for the generic cpufreq-dt driver. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> --- v2: - new patch, split out from DTS changes and rebased with new name for cpufreq driver --- arch/arm/mach-imx/mach-imx53.c | 2 ++ 1 file changed, 2 insertions(+)