From: Viresh Kumar <viresh.kumar@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linaro-kernel <linaro-kernel@lists.linaro.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-renesas-soc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/8] cpufreq: shmobile: Use generic platdev driver
Date: Fri, 22 Apr 2016 08:51:42 +0530 [thread overview]
Message-ID: <20160422032142.GN29799@vireshk-i7> (raw)
In-Reply-To: <CAMuHMdUnzgr==S86Wiz0fGk2gSWW2=j+maiq3=3x9Ozy7AoOZw@mail.gmail.com>
On 21-04-16, 15:04, Geert Uytterhoeven wrote:
> Hi Viresh,
>
> On Thu, Apr 21, 2016 at 10:43 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> > @@ -29,6 +29,18 @@ static const struct of_device_id machines[] = {
> > { .compatible = "samsung,exynos5800", },
> > #endif
> >
>
> I think an #ifdef CONFIG_ARCH_RENESAS block wouldn't hurt, likewise
> for the other SoCs.
> Soon you'll have this file filled with lots of compatible values for random\
> SoCs...
This is going to be done once per boot and this shouldn't hurt. And for new
platforms we may do things differently as they are going to use opp-v2 bindings.
And, so I am not really in favor of ifdef hackery :)
--
viresh
next prev parent reply other threads:[~2016-04-22 3:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 8:43 [PATCH 0/8] cpufreq: dt: Don't create platform-device from platform code Viresh Kumar
2016-04-21 8:43 ` [PATCH 1/8] cpufreq: berlin: Use generic platdev driver Viresh Kumar
2016-04-21 9:05 ` Antoine Tenart
2016-04-21 8:43 ` [PATCH 2/8] cpufreq: imx: " Viresh Kumar
2016-04-21 9:19 ` Lucas Stach
2016-04-21 9:46 ` Arnd Bergmann
2016-04-21 9:50 ` Viresh Kumar
2016-04-21 10:17 ` Arnd Bergmann
2016-04-21 8:43 ` [PATCH 3/8] cpufreq: omap: " Viresh Kumar
2016-04-21 8:43 ` [PATCH 4/8] cpufreq: rockchip: " Viresh Kumar
2016-04-21 8:43 ` [PATCH 5/8] cpufreq: shmobile: " Viresh Kumar
2016-04-21 13:04 ` Geert Uytterhoeven
2016-04-22 3:21 ` Viresh Kumar [this message]
2016-04-22 6:41 ` Geert Uytterhoeven
2016-04-22 6:47 ` Viresh Kumar
2016-04-21 8:43 ` [PATCH 6/8] cpufreq: sunxi: " Viresh Kumar
2016-04-21 8:54 ` Maxime Ripard
2016-04-21 8:43 ` [PATCH 7/8] cpufreq: zynq: " Viresh Kumar
2016-04-21 8:43 ` [PATCH 8/8] cpufreq: hisilicon: " Viresh Kumar
2016-04-23 17:14 ` Leo Yan
2016-04-21 9:49 ` [PATCH 0/8] cpufreq: dt: Don't create platform-device from platform code Arnd Bergmann
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=20160422032142.GN29799@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@rjwysocki.net \
/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