From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] soc: mediatek: Add infracfg misc driver support
Date: Tue, 12 May 2015 11:24:31 +0200 [thread overview]
Message-ID: <1431422671.2398.155.camel@x220> (raw)
In-Reply-To: <1431372206-1237-2-git-send-email-s.hauer@pengutronix.de>
On Mon, 2015-05-11 at 21:23 +0200, Sascha Hauer wrote:
> --- a/drivers/soc/mediatek/Kconfig
> +++ b/drivers/soc/mediatek/Kconfig
> +config MTK_INFRACFG
> + tristate "MediaTek INFRACFG Support"
> + depends on ARCH_MEDIATEK
> + select REGMAP
> + help
> + Say yes here to add support for the MediaTek INFRACFG controller. The
> + INFRACFG controller contains various infrastructure registers not
> + directly associated to any device.
> --- a/drivers/soc/mediatek/Makefile
> +++ b/drivers/soc/mediatek/Makefile
> +obj-$(CONFIG_MTK_INFRACFG) += mtk-infracfg.o
> --- /dev/null
> +++ b/drivers/soc/mediatek/mtk-infracfg.c
> +EXPORT_SYMBOL_GPL(mtk_infracfg_set_bus_protection);
> +EXPORT_SYMBOL_GPL(mtk_infracfg_clear_bus_protection);
As I understand it, if both MTK_INFRACFG and MTK_SCPSYS (see 3/5) are m
we will get mtk-infracfg.ko and mtk-scpsys.ko (see 3/5). And loading
mtk-scpsys.ko will trigger loading mtk-infracfg.ko, right?
But since this file has no MODULE_LICENSE() that should generate a
warning and taint the kernel. (I haven't tested this. Please correct me
if I'm overlooking something here.)
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-05-12 9:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:23 [PATCH v2] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-05-12 7:12 ` Sascha Hauer
2015-05-12 9:24 ` Paul Bolle [this message]
2015-05-12 13:26 ` Sascha Hauer
2015-05-15 14:17 ` Daniel Kurtz
2015-05-18 8:16 ` Sascha Hauer
2015-05-19 6:54 ` Daniel Kurtz
2015-05-19 7:45 ` Sascha Hauer
2015-05-19 10:39 ` Daniel Kurtz
2015-05-26 23:12 ` Kevin Hilman
2015-05-27 7:33 ` Sascha Hauer
2015-05-11 19:23 ` [PATCH 2/5] dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit Sascha Hauer
2015-05-11 19:23 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-05-12 11:52 ` Matthias Brugger
2015-05-12 13:47 ` Sascha Hauer
2015-05-15 14:17 ` Daniel Kurtz
2015-05-19 10:30 ` Sascha Hauer
2015-05-19 11:06 ` Matthias Brugger
2015-05-20 14:03 ` Sascha Hauer
2015-05-20 16:06 ` Matthias Brugger
2015-05-11 19:23 ` [PATCH 4/5] ARM64: MediaTek: Add generic pm domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 14:18 [PATCH v3] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-20 14:18 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-05-21 8:09 ` Paul Bolle
2015-06-09 8:46 [PATCH v4] Mediatek SCPSYS power domain support Sascha Hauer
2015-06-09 8:46 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
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=1431422671.2398.155.camel@x220 \
--to=pebolle@tiscali.nl \
--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).