From: Lina Iyer <lina.iyer@linaro.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: andy.gross@linaro.org, sboyd@codeaurora.org,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] drivers: qcom: spm: avoid module usage in non-modular SPM driver
Date: Mon, 4 Jan 2016 11:02:39 -0700 [thread overview]
Message-ID: <20160104180239.GH3342@linaro.org> (raw)
In-Reply-To: <20160104175233.GN12458@windriver.com>
On Mon, Jan 04 2016 at 10:52 -0700, Paul Gortmaker wrote:
>[Re: [PATCH] drivers: qcom: spm: avoid module usage in non-modular SPM driver] On 04/01/2016 (Mon 10:40) Lina Iyer wrote:
>
>> On Mon, Jan 04 2016 at 10:30 -0700, Paul Gortmaker wrote:
>> >[[PATCH] drivers: qcom: spm: avoid module usage in non-modular SPM driver] On 04/01/2016 (Mon 10:15) Lina Iyer wrote:
>> >
>> >>SPM driver provides cpuidle support on some QC SoC's. The functionality
>> >>is non-modular and there is no need for module support. Convert module
>> >>platform init to builtin platform driver init. The driver functionality
>> >>is not affected by this change.
>> >>
>> >>Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
>> >
>> >I have a similar patch locally that I'd not sent yet, the only
>> >difference is that I moved the description tag to the top of the file
>> >since there wasn't a description there, i.e. this chunk:
>> >
>> >diff --git a/drivers/soc/qcom/spm.c b/drivers/soc/qcom/spm.c
>> >index b04b05a0904e..9e06a241257f 100644
>> >--- a/drivers/soc/qcom/spm.c
>> >+++ b/drivers/soc/qcom/spm.c
>> >@@ -2,6 +2,8 @@
>> > * Copyright (c) 2011-2014, The Linux Foundation. All rights reserved.
>> > * Copyright (c) 2014,2015, Linaro Ltd.
>> > *
>> >+ * SAW power controller driver
>> >+ *
>> Makes sense.
>>
>> I can add this to my patch and resend if thats OK with you?
>
>Sure, go ahead and add an Acked by if you want to. I'll just drop it
>from my queue when I see yours added and appear in linux-next.
>
>Looking at my queue, there are still two others in SOC I'll need to send
>eventually:
>
>drivers-soc-make-sunxi_sram.c-explicitly-non-modular.patch
>drivers-soc-tegra-make-fuse-tegra.c-explicitly-non-m.patch
>
>...and there are lots of others that I need to do a final review and test
>on before sending, so one less here and there is definitely welcome.
>
I figured if you are making changes to drivers, then you would do it for
SPM but it needs to be tested out. I tested it out on a IFC6540 Dragonboard.
Thanks.
-- Lina
>Thanks,
>Paul.
>--
>
>>
>> -- Lina
>>
>> > * This program is free software; you can redistribute it and/or modify
>> > * it under the terms of the GNU General Public License version 2 and
>> > * only version 2 as published by the Free Software Foundation.
>> >
>> >
>> >Paul.
>> >--
>> >
>> >>Signed-off-by: Lina Iyer <lina.iyer@linaro.org>
>> >>---
>> >> drivers/soc/qcom/spm.c | 7 +------
>> >> 1 file changed, 1 insertion(+), 6 deletions(-)
>> >>
>> >>diff --git a/drivers/soc/qcom/spm.c b/drivers/soc/qcom/spm.c
>> >>index b04b05a..199c085 100644
>> >>--- a/drivers/soc/qcom/spm.c
>> >>+++ b/drivers/soc/qcom/spm.c
>> >>@@ -12,7 +12,6 @@
>> >> * GNU General Public License for more details.
>> >> */
>> >>
>> >>-#include <linux/module.h>
>> >> #include <linux/kernel.h>
>> >> #include <linux/init.h>
>> >> #include <linux/io.h>
>> >>@@ -378,8 +377,4 @@ static struct platform_driver spm_driver = {
>> >> .of_match_table = spm_match_table,
>> >> },
>> >> };
>> >>-module_platform_driver(spm_driver);
>> >>-
>> >>-MODULE_LICENSE("GPL v2");
>> >>-MODULE_DESCRIPTION("SAW power controller driver");
>> >>-MODULE_ALIAS("platform:saw");
>> >>+builtin_platform_driver(spm_driver);
>> >>--
>> >>2.1.4
>> >>
next prev parent reply other threads:[~2016-01-04 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 17:15 [PATCH] drivers: qcom: spm: avoid module usage in non-modular SPM driver Lina Iyer
2016-01-04 17:30 ` Paul Gortmaker
2016-01-04 17:40 ` Lina Iyer
2016-01-04 17:52 ` Paul Gortmaker
2016-01-04 18:02 ` Lina Iyer [this message]
2016-01-04 18:30 ` Paul Gortmaker
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=20160104180239.GH3342@linaro.org \
--to=lina.iyer@linaro.org \
--cc=andy.gross@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sboyd@codeaurora.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).