From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: 'Kukjin Kim' <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@arm.linux.org.uk, naushad@samsung.com, t.figa@samsung.com,
joshi@samsung.com, vikas.sajjan@samsung.com,
chow.kim@samsung.com
Subject: RE: [PATCH v6 2/6] ARM: EXYNOS: Move cpufreq and cpuidle device registration to init_machine
Date: Mon, 14 Jul 2014 09:40:59 +0530 [thread overview]
Message-ID: <000301cf9f19$9fff2110$dffd6330$@samsung.com> (raw)
In-Reply-To: <026701cf9c43$98b20860$ca161920$@samsung.com>
Hi Kukjin,
On Thursday, July 10, 2014 7:04 PM, Kukjin wrote:
> Pankaj Dubey wrote:
> >
> > Hi Kukjin,
> >
> Hi,
>
> > >
> > > On 07/07/14 12:50, Pankaj Dubey wrote:
> > > > As exynos_cpuidle_init and exynos_cpufreq_init function have just
> > > > one lines of code for registering platform devices. We can move
> > > > these lines to exynos_dt_machine_init and delete
> > > > exynos_cpuidle_init and exynos_cpufreq_init function. This will
> > > > help in reducing lines of code in exynos.c, making it more cleaner.
> > > >
> > > > Suggested-by: Tomasz Figa<t.figa@samsung.com>
> > > > Signed-off-by: Pankaj Dubey<pankaj.dubey@samsung.com>
> > > > Reviewed-by: Tomasz Figa<t.figa@samsung.com>
> > > > ---
> > > > arch/arm/mach-exynos/exynos.c | 20 ++++----------------
> > > > 1 file changed, 4 insertions(+), 16 deletions(-)
> > > >
> > > > diff --git a/arch/arm/mach-exynos/exynos.c
> > > > b/arch/arm/mach-exynos/exynos.c index ff60b4c..47170eb 100644
> > > > --- a/arch/arm/mach-exynos/exynos.c
> > > > +++ b/arch/arm/mach-exynos/exynos.c
> > > > @@ -171,19 +171,6 @@ static struct platform_device exynos_cpuidle =
{
> > > > .id = -1,
> > > > };
> > > >
> > > > -void __init exynos_cpuidle_init(void) -{
> > > > - if (soc_is_exynos5440())
> > > > - return;
> > > > -
> > > > - platform_device_register(&exynos_cpuidle);
> > > > -}
> > > > -
> > > > -void __init exynos_cpufreq_init(void) -{
> > > > - platform_device_register_simple("exynos-cpufreq", -1, NULL,
0);
> > > > -}
> > > > -
> > > > void __iomem *sysram_base_addr;
> > > > void __iomem *sysram_ns_base_addr;
> > > >
> > > > @@ -300,10 +287,11 @@ static void __init
exynos_dt_machine_init(void)
> > > > if (!IS_ENABLED(CONFIG_SMP))
> > > > exynos_sysram_init();
> > > >
> > > > - if (!of_machine_is_compatible("samsung,exynos5420"))
> > > > - exynos_cpuidle_init();
> > > > + if (!of_machine_is_compatible("samsung,exynos5420") ||
> > > > +
!of_machine_is_compatible("samsung,exynos5440"))
> > > > + platform_device_register(&exynos_cpuidle);
> > > >
> > > > - exynos_cpufreq_init();
> > > > + platform_device_register_simple("exynos-cpufreq", -1, NULL,
0);
> > > >
> > > > of_platform_populate(NULL, of_default_bus_match_table, NULL,
> NULL);
> > > > }
> > >
> > > This cannot be applied in my tree now....
> > >
> >
> > May I know what the issue is? As I am able to rebase this patch on
> > today's kgene/for-next and could not see any merge conflict.
> > If you think I need to respin this patch please let me know.
> >
>
> Pankaj, I found this is based on cpuidle related branch in my tree, BTW
this
> has a dependency with following so please respin your patch once I take
the
> patch in my tree maybe tonight.
>
> https://lkml.org/lkml/2014/6/24/286
>
Thanks. I have respinned this after resolving merge conflict.
Thanks,
Pankaj Dubey
> Thanks,
> Kukjin
next prev parent reply other threads:[~2014-07-14 4:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 3:50 [PATCH v6 0/6] Cleanup patches for mach-exynos Pankaj Dubey
2014-07-07 3:50 ` [PATCH v6 1/6] ARM: EXYNOS: Make exynos machine_ops as static Pankaj Dubey
2014-07-07 3:50 ` [PATCH v6 2/6] ARM: EXYNOS: Move cpufreq and cpuidle device registration to init_machine Pankaj Dubey
2014-07-07 22:56 ` Kukjin Kim
2014-07-08 7:35 ` Pankaj Dubey
2014-07-10 13:33 ` Kukjin Kim
2014-07-14 4:10 ` Pankaj Dubey [this message]
2014-07-07 3:50 ` [PATCH v6 3/6] ARM: EXYNOS: Move SYSREG definition into sys-reg specific file Pankaj Dubey
2014-07-07 3:50 ` [PATCH v6 4/6] ARM: EXYNOS: Remove file path from comment section Pankaj Dubey
2014-07-07 3:50 ` [PATCH v6 5/6] ARM: EXYNOS: Remove regs-pmu.h header dependency from pm_domain Pankaj Dubey
2014-07-07 3:50 ` [PATCH v6 6/6] ARM: EXYNOS: Remove "linux/bug.h" from pmu.c Pankaj Dubey
2014-07-07 22:48 ` [PATCH v6 0/6] Cleanup patches for mach-exynos Kukjin Kim
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='000301cf9f19$9fff2110$dffd6330$@samsung.com' \
--to=pankaj.dubey@samsung.com \
--cc=chow.kim@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=naushad@samsung.com \
--cc=t.figa@samsung.com \
--cc=vikas.sajjan@samsung.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