From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@rjwysocki.net, Mian Yousaf Kaukab <ykaukab@suse.de>
Cc: linux-pm@vger.kernel.org, andy.tang@nxp.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, shawnguo@kernel.org,
leoyang.li@nxp.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] cpufreq: qoriq: convert to a platform driver
Date: Tue, 28 Apr 2020 16:31:25 +0530 [thread overview]
Message-ID: <20200428110125.lobyrsbma6astfmq@vireshk-i7> (raw)
In-Reply-To: <20200421083000.16740-1-ykaukab@suse.de>
On 21-04-20, 10:29, Mian Yousaf Kaukab wrote:
> The driver has to be manually loaded if it is built as a module. It
> is neither exporting MODULE_DEVICE_TABLE nor MODULE_ALIAS. Moreover,
> no platform-device is created (and thus no uevent is sent) for the
> clockgen nodes it depends on.
>
> Convert the module to a platform driver with its own alias. Moreover,
> drop whitelisted SOCs. Platform device will be created only for the
> compatible platforms.
>
> Reviewed-by: Yuantian Tang <andy.tang@nxp.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Mian Yousaf Kaukab <ykaukab@suse.de>
> ---
> v2:
> +Rafael, Stephen, linux-clk
> Add Reviewed-by and Acked-by tags
>
> drivers/cpufreq/qoriq-cpufreq.c | 76 ++++++++++++++++-------------------------
> 1 file changed, 29 insertions(+), 47 deletions(-)
@Rafael,
Though this looks to be PPC stuff, but it is used on both ARM and PPC. Do you
want to pick them up or should I do that ?
--
viresh
next prev parent reply other threads:[~2020-04-28 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 8:29 [PATCH v2 1/2] cpufreq: qoriq: convert to a platform driver Mian Yousaf Kaukab
2020-04-21 8:30 ` [PATCH v2 2/2] clk: qoriq: add cpufreq platform device Mian Yousaf Kaukab
2020-05-05 6:11 ` Stephen Boyd
2020-04-28 11:01 ` Viresh Kumar [this message]
2020-05-07 5:18 ` [PATCH v2 1/2] cpufreq: qoriq: convert to a platform driver Viresh Kumar
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=20200428110125.lobyrsbma6astfmq@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andy.tang@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ykaukab@suse.de \
/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).