From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] cpufreq: mediatek: Add MT8173 cpufreq driver
Date: Thu, 9 Jul 2015 10:47:04 +0530 [thread overview]
Message-ID: <20150709051704.GL1805@linux> (raw)
In-Reply-To: <CALx668Xp051A-BBGwwNxpiQCt318Bh5fnA5jcAXBg-9vPcqpvg@mail.gmail.com>
On 09-07-15, 09:55, Pi-Cheng Chen wrote:
> That's what I did in previous version. But the reason I use the device-
> driver model is to handle the defer probing issue. Since there's no
> arch/arm64/mach-mediatek/ directory to hold the device registration
> code anymore, no device tree way to match cpufreq driver
> (please correct me if there's any), and initcall seems not handle
> defer probing either, therefore I put both device and driver
> registration in this function. I know it's crappy. :(
> Do you have any suggestion to do it right and handle defer probing
> properly?
Sounds reasonable. Just add proper comment in code to explain that.
--
viresh
prev parent reply other threads:[~2015-07-09 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 2:16 [PATCH v5 0/2] Add Mediatek MT8173 cpufreq driver Pi-Cheng Chen
2015-07-01 2:16 ` [PATCH v5 1/2] dt-bindings: mediatek: Add MT8173 cpufreq driver binding Pi-Cheng Chen
2015-07-08 11:19 ` Viresh Kumar
2015-07-09 15:04 ` Michael Turquette
2015-07-01 2:16 ` [PATCH v5 2/2] cpufreq: mediatek: Add MT8173 cpufreq driver Pi-Cheng Chen
2015-07-01 21:24 ` Alexey Klimov
2015-07-02 1:31 ` Pi-Cheng Chen
2015-07-08 11:34 ` Viresh Kumar
2015-07-09 1:55 ` Pi-Cheng Chen
2015-07-09 5:17 ` Viresh Kumar [this message]
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=20150709051704.GL1805@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).