From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-clk <linux-clk@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Russell King <linux@armlinux.org.uk>,
Jiri Slaby <jslaby@suse.com>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH 11/14] pinctrl: milbeaut: Add Milbeaut M10V pinctrl
Date: Wed, 5 Dec 2018 14:03:48 +0900 [thread overview]
Message-ID: <5dcbde7f-8458-8630-9f7e-115a9c8364e4@socionext.com> (raw)
In-Reply-To: <CAK7LNASnBobLm51VL=EVt+97-KBX3vEqXGjTH-L-q1Qn8_GUQA@mail.gmail.com>
Hi
Thank you for your comments.
On 2018/12/04 20:23, Masahiro Yamada wrote:
> Hi Sugaya-san
>
> On Mon, Nov 19, 2018 at 10:01 AM Sugaya Taichi
> <sugaya.taichi@socionext.com> wrote:
>>
>> Add Milbeaut M10V pinctrl.
>> The M10V has the pins that can be used GPIOs or take multiple other
>> functions.
>>
>> Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
>
>
> This patch was sent to:
>
> linux-clk@vger.kernel.org,
> devicetree@vger.kernel.org,
> linux-arm-kernel@lists.infradead.org,
> linux-kernel@vger.kernel.org,
> linux-serial@vger.kernel.org
>
>
>
>
> Unfortunately, the most important ML
>
> linux-gpio@vger.kernel.org
>
> was not addressed.
>
>
> The pinctrl maintainer may not notice this patch.
Ah I took a critical mistake...
>
>
>
>
>
>
>
>> diff --git a/drivers/pinctrl/pinctrl-m10v.c b/drivers/pinctrl/pinctrl-m10v.c
>> new file mode 100644
>> index 0000000..d4ca713
>> --- /dev/null
>> +++ b/drivers/pinctrl/pinctrl-m10v.c
>> @@ -0,0 +1,765 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Copyright (C) 2018 Socionext Ltd.
>> + * Copyright (C) 2015 Linaro Ltd.
>> + * Author: Jassi Brar <jaswinder.singh@linaro.org>
>
>
> My company name is "Socionext Inc." instead of "Socionext Ltd."
Yes, modify it.
>
>
>
>
>
>
>
>> +static struct platform_driver m10v_pinctrl_driver = {
>> + .probe = m10v_pinctrl_probe,
>> + .driver = {
>> + .name = "m10v-pinctrl",
>> + .of_match_table = m10v_pmatch,
>> + },
>> +};
>> +
>> +static int __init m10v_pinctrl_init(void)
>> +{
>> + return platform_driver_register(&m10v_pinctrl_driver);
>> +}
>> +arch_initcall(m10v_pinctrl_init);
>
>
> Can't it be builtin_platform_driver()?
I think using builtin_platform_driver() is no problem.
>
> Which device requires this to be arch_initcall()?
This driver was originally a module, so no need to be arch_initcall().
I will use arch_initcall() instead.
Thanks
Sugaya Taichi
>
>
>
>
>
> --
> Best Regards
> Masahiro Yamada
>
next prev parent reply other threads:[~2018-12-05 5:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 1:02 [PATCH 10/14] dt-bindings: pinctrl: milbeaut: Add Milbeaut M10V pinctrl description Sugaya Taichi
2018-11-19 1:02 ` [PATCH 11/14] pinctrl: milbeaut: Add Milbeaut M10V pinctrl Sugaya Taichi
2018-12-04 11:23 ` Masahiro Yamada
2018-12-05 5:03 ` Sugaya, Taichi [this message]
2018-11-19 1:02 ` [PATCH 12/14] ARM: dts: milbeaut: Add device tree set for the Milbeaut M10V board Sugaya Taichi
2018-11-19 15:46 ` Rob Herring
2018-11-21 2:36 ` sugaya.taichi
2018-11-19 1:02 ` [PATCH 13/14] ARM: configs: Add Milbeaut M10V defconfig Sugaya Taichi
2018-11-19 1:02 ` [PATCH 14/14] MAINTAINERS: Add entry to MAINTAINERS for Milbeaut Sugaya Taichi
2018-12-04 23:11 ` [PATCH 10/14] dt-bindings: pinctrl: milbeaut: Add Milbeaut M10V pinctrl description Rob Herring
2018-12-06 8:29 ` Sugaya, Taichi
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=5dcbde7f-8458-8630-9f7e-115a9c8364e4@socionext.com \
--to=sugaya.taichi@socionext.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaswinder.singh@linaro.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
/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®