From: Light Hsieh <light.hsieh@mediatek.com>
To: Sean Wang <sean.wang@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, <kuohong.wang@mediatek.com>
Subject: Re: [PATCH v4 2/2] pinctrl: make MediaTek MT6765 pinctrl ready for buidling loadable module
Date: Tue, 17 Mar 2020 17:28:44 +0800 [thread overview]
Message-ID: <1584437324.12211.10.camel@mtkswgap22> (raw)
In-Reply-To: <CAGp9Lzo-HkmiitBBJF9Mybbrdgy-Kphfyi2wf0SwMGXTeuWGVA@mail.gmail.com>
On Sun, 2020-03-15 at 14:15 -0700, Sean Wang wrote:
> Hi, Light
>
> On Tue, Mar 10, 2020 at 12:39 AM <light.hsieh@mediatek.com> wrote:
> >
> > From: Light Hsieh <light.hsieh@mediatek.com>
> >
> > This patch make pinctrl-mt6765 ready for building as loadable module.
> s/building/building/
>
> I got build error after when those two patches are being applied
> ../drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c:529:1: error:
> 'mtk_pinconf_bias_set_gev1' undeclared here (not in a function)
>
OK. I will fix it.
> >
> > Signed-off-by: Light Hsieh <light.hsieh@mediatek.com>
> > Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> > ---
> > drivers/pinctrl/mediatek/Kconfig | 2 +-
> > drivers/pinctrl/mediatek/pinctrl-mt6765.c | 4 ++++
> > 2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pinctrl/mediatek/Kconfig b/drivers/pinctrl/mediatek/Kconfig
> > index 4cd1109..c645fdb 100644
> > --- a/drivers/pinctrl/mediatek/Kconfig
> > +++ b/drivers/pinctrl/mediatek/Kconfig
> > @@ -89,7 +89,7 @@ config PINCTRL_MT2712
> > select PINCTRL_MTK
> >
> > config PINCTRL_MT6765
> > - bool "Mediatek MT6765 pin control"
> > + tristate "Mediatek MT6765 pin control"
> > depends on OF
> > depends on ARM64 || COMPILE_TEST
> > default ARM64 && ARCH_MEDIATEK
> > diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6765.c b/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> > index 905dae8c..2c59d39 100644
> > --- a/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> > +++ b/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> > @@ -6,6 +6,7 @@
> > *
> > */
> >
> > +#include <linux/module.h>
> > #include "pinctrl-mtk-mt6765.h"
> > #include "pinctrl-paris.h"
> >
> > @@ -1103,3 +1104,6 @@ static int __init mt6765_pinctrl_init(void)
> > return platform_driver_register(&mt6765_pinctrl_driver);
> > }
> > arch_initcall(mt6765_pinctrl_init);
> > +
> > +MODULE_LICENSE("GPL v2");
> > +MODULE_DESCRIPTION("MediaTek MT6765 Pinctrl Driver");
> > --
> > 1.8.1.1.dirty
prev parent reply other threads:[~2020-03-17 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 7:39 [PATCH v4 0/2] pinctrl: make MediaTek pinctrl v2 driver and MT6765 pinctrl driver ready for building loadable module light.hsieh
2020-03-10 7:39 ` [PATCH v4 1/2] pinctrl: make MediaTek pinctrl v2 driver ready for buidling " light.hsieh
2020-03-15 21:35 ` Sean Wang
2020-03-17 9:28 ` Light Hsieh
2020-03-17 19:57 ` Sean Wang
2020-03-10 7:39 ` [PATCH v4 2/2] pinctrl: make MediaTek MT6765 pinctrl " light.hsieh
2020-03-15 21:15 ` Sean Wang
2020-03-17 9:28 ` Light Hsieh [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=1584437324.12211.10.camel@mtkswgap22 \
--to=light.hsieh@mediatek.com \
--cc=kuohong.wang@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=sean.wang@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;
as well as URLs for NNTP newsgroup(s).