From: Viresh Kumar <viresh.kumar@linaro.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 1/4] cpufreq: pxa: use generic platdev driver for device-tree
Date: Thu, 20 Oct 2016 09:04:35 +0530 [thread overview]
Message-ID: <20161020033435.GD11766@vireshk-i7> (raw)
In-Reply-To: <87bmyg3xzh.fsf@belgarion.home>
On 19-10-16, 22:06, Robert Jarzmik wrote:
> Viresh Kumar <viresh.kumar@linaro.org> writes:
>
> >> >> + { .compatible = "marvell,pxa250", },
> >> >> + { .compatible = "marvell,pxa270", },
> >> >>
> >> >> { .compatible = "samsung,exynos3250", },
> >> >> { .compatible = "samsung,exynos4210", },
> >> >
> >> > Isn't there a race between cpufreq-dt and the platform driver to
> >> > register first ?
> >> Ah, could you be more specific about the race you're talking of ?
> >>
> >> My understanding was that cpufreq-dt-platdev does create the device, and
> >> cpufreq-dt is a driver for it, so there is no race but a direct relationship
> >> AFAIU.
> >
> > I mean that both the driver may try to register to the cpufreq core if
> > they are both compiled in a single image.
> Euh I still don't follow you. The only driver that can register to the cpufreq
> core is cpufreq-dt.
I was wondering on what will happen if both cpufreq-dt and your pxa2xx-cpufreq
driver are present in the same kernel image. In that case the init routines of
both of them will try to call cpufreq_register_driver().
--
viresh
next prev parent reply other threads:[~2016-10-20 3:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 19:57 [PATCH v2 0/4] PXA cpufreq conversion to clock API Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 1/4] cpufreq: pxa: use generic platdev driver for device-tree Robert Jarzmik
[not found] ` <1476561450-28407-2-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:38 ` Viresh Kumar
2016-10-18 15:35 ` Robert Jarzmik
2016-10-19 13:52 ` Viresh Kumar
2016-10-19 20:06 ` Robert Jarzmik
2016-10-20 3:34 ` Viresh Kumar [this message]
2016-10-21 15:17 ` Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 2/4] ARM: dts: pxa: add pxa25x cpu operating points Robert Jarzmik
[not found] ` <1476561450-28407-3-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:39 ` Viresh Kumar
2016-10-18 15:30 ` Robert Jarzmik
2016-10-19 13:51 ` Viresh Kumar
2016-10-15 19:57 ` [PATCH v2 3/4] ARM: dts: pxa: add pxa27x " Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 4/4] cpufreq: pxa: convert to clock API Robert Jarzmik
[not found] ` <1476561450-28407-5-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:40 ` Viresh Kumar
2016-10-22 21:37 ` Robert Jarzmik
2016-10-24 3:33 ` Viresh Kumar
[not found] ` <1476561450-28407-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-15 20:34 ` [PATCH v2 0/4] PXA cpufreq conversion " Russell King - ARM Linux
2016-10-15 21:17 ` Robert Jarzmik
2016-10-15 21:38 ` WARNING: SOMEONE RECEIVING THIS HAS BEEN HACKED (was: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API) Russell King - ARM Linux
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=20161020033435.GD11766@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.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).