From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Shyti <andi.shyti@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Lee Jones <lee.jones@linaro.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH 0/4] mfd: max77686: Allow the driver to be built as a module
Date: Fri, 12 Feb 2016 01:30:15 -0300 [thread overview]
Message-ID: <1455251419-8919-1-git-send-email-javier@osg.samsung.com> (raw)
Hello,
The Maxim77802 PMIC driver uses a boolean Kconfig symbol but there isn't
really a reason to require the driver to be built-in.
It is true that since the PMIC provides clocks and regulators that could
be critical on a system, most integrators are not going to build it as a
module but it could be useful for multi-platform or distribution kernels
that support different systems by building as much as possible as module.
Besides this series, a patch for the max77686 regulator driver is needed
or the MFD max77686 driver module won't be installed by kbuild. I didn't
include the patch in this series to avoid cross-subsystems churn for the
maintainers and also because I don't consider that a regression since it
was not possible to build the driver as a module before anyways.
Also, all the defconfigs in mainline that enable the MFD max77686 driver
Kconfig symbol are using =y of course so it shouldn't be an issue to get
this set merged, before the max77686 regulator patch already posted [0].
[0]: https://patchwork.kernel.org/patch/8287431/
Best regards,
Javier
Javier Martinez Canillas (4):
mfd: max77686: Add max77802 to I2C device ID table
mfd: max77686: Use module_i2c_driver() instead of subsys initcall
mfd: max77686: Allow driver to be built as a module
mfd: max77686: Export OF module alias information
drivers/mfd/Kconfig | 4 ++--
drivers/mfd/max77686.c | 15 +++------------
2 files changed, 5 insertions(+), 14 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-12 4:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 4:30 Javier Martinez Canillas [this message]
2016-02-12 4:30 ` [PATCH 1/4] mfd: max77686: Add max77802 to I2C device ID table Javier Martinez Canillas
2016-02-15 5:21 ` Krzysztof Kozlowski
2016-03-08 4:24 ` Lee Jones
2016-02-12 4:30 ` [PATCH 2/4] mfd: max77686: Use module_i2c_driver() instead of subsys initcall Javier Martinez Canillas
2016-02-15 6:54 ` Krzysztof Kozlowski
2016-02-15 8:21 ` Lee Jones
2016-02-15 15:21 ` Javier Martinez Canillas
2016-02-15 23:20 ` Krzysztof Kozlowski
2016-02-16 20:45 ` Javier Martinez Canillas
2016-02-17 7:49 ` Krzysztof Kozlowski
2016-02-17 18:38 ` Javier Martinez Canillas
2016-02-17 9:27 ` Marek Szyprowski
2016-02-17 9:34 ` Krzysztof Kozlowski
2016-02-12 4:30 ` [PATCH 3/4] mfd: max77686: Allow driver to be built as a module Javier Martinez Canillas
2016-03-08 4:11 ` Lee Jones
2016-02-12 4:30 ` [PATCH 4/4] mfd: max77686: Export OF module alias information Javier Martinez Canillas
2016-02-15 6:55 ` Krzysztof Kozlowski
2016-03-08 4:24 ` Lee Jones
2016-02-15 7:04 ` [PATCH 0/4] mfd: max77686: Allow the driver to be built as a module Andi Shyti
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=1455251419-8919-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=andi.shyti@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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
all inboxes | Powered by JetHome®