From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
praithatha-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] pinctrl: tegra114: add pinctrl driver for NVIDIA's Tegra114 SoC
Date: Mon, 07 Jan 2013 09:58:15 -0700 [thread overview]
Message-ID: <50EAFEA7.90201@wwwdotorg.org> (raw)
In-Reply-To: <1357387375-25919-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 01/05/2013 05:02 AM, Laxman Dewangan wrote:
> From: Pritesh Raithatha <praithatha-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> This adds a driver for the Tegra114 pinmux, and required
> parameterization data for Tegra114.
>
> The driver uses the common Tegra pincontrol driver utility
> functions to implement the majority of the driver.
>
> This driver is not compatible with the earlier NVIDIA's SoCs,
> hence add new compatibile as "nvidia,tegra114-pinmux".
>
> Originally written by Pritesh.
> ldewangan: cleanup the patches, remove non-require tables.
> +static struct platform_driver tegra114_pinctrl_driver = {
> + .driver = {
> + .name = "tegra114-pinctrl",
> + .owner = THIS_MODULE,
> + .of_match_table = tegra114_pinctrl_of_match,
> + },
> + .probe = tegra114_pinctrl_probe,
> + .remove = tegra_pinctrl_remove,
> +};
> +
> +static int __init tegra114_pinctrl_init(void)
> +{
> + return platform_driver_register(&tegra114_pinctrl_driver);
> +}
> +arch_initcall(tegra114_pinctrl_init);
> +
> +static void __exit tegra114_pinctrl_exit(void)
> +{
> + platform_driver_unregister(&tegra114_pinctrl_driver);
> +}
> +module_exit(tegra114_pinctrl_exit);
I believe that last chunk should be
module_platform_driver(tegra114_pinctrl_driver), since now that
everything is instantiated purely from DT, I don't believe there's any
probe ordering advantage to be gained from using arch_initcall() rather
than module_init().
Aside from that, the series,
Reviewed-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
I didn't check the content of all the tables, but the structure looks good!
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: linus.walleij@linaro.org, linux-doc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
praithatha@nvidia.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: tegra114: add pinctrl driver for NVIDIA's Tegra114 SoC
Date: Mon, 07 Jan 2013 09:58:15 -0700 [thread overview]
Message-ID: <50EAFEA7.90201@wwwdotorg.org> (raw)
In-Reply-To: <1357387375-25919-2-git-send-email-ldewangan@nvidia.com>
On 01/05/2013 05:02 AM, Laxman Dewangan wrote:
> From: Pritesh Raithatha <praithatha@nvidia.com>
>
> This adds a driver for the Tegra114 pinmux, and required
> parameterization data for Tegra114.
>
> The driver uses the common Tegra pincontrol driver utility
> functions to implement the majority of the driver.
>
> This driver is not compatible with the earlier NVIDIA's SoCs,
> hence add new compatibile as "nvidia,tegra114-pinmux".
>
> Originally written by Pritesh.
> ldewangan: cleanup the patches, remove non-require tables.
> +static struct platform_driver tegra114_pinctrl_driver = {
> + .driver = {
> + .name = "tegra114-pinctrl",
> + .owner = THIS_MODULE,
> + .of_match_table = tegra114_pinctrl_of_match,
> + },
> + .probe = tegra114_pinctrl_probe,
> + .remove = tegra_pinctrl_remove,
> +};
> +
> +static int __init tegra114_pinctrl_init(void)
> +{
> + return platform_driver_register(&tegra114_pinctrl_driver);
> +}
> +arch_initcall(tegra114_pinctrl_init);
> +
> +static void __exit tegra114_pinctrl_exit(void)
> +{
> + platform_driver_unregister(&tegra114_pinctrl_driver);
> +}
> +module_exit(tegra114_pinctrl_exit);
I believe that last chunk should be
module_platform_driver(tegra114_pinctrl_driver), since now that
everything is instantiated purely from DT, I don't believe there's any
probe ordering advantage to be gained from using arch_initcall() rather
than module_init().
Aside from that, the series,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
I didn't check the content of all the tables, but the structure looks good!
next prev parent reply other threads:[~2013-01-07 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 12:02 [PATCH 1/2] pinctrl: tegra: add support for rcv-sel and drive type Laxman Dewangan
2013-01-05 12:02 ` Laxman Dewangan
[not found] ` <1357387375-25919-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-05 12:02 ` [PATCH 2/2] pinctrl: tegra114: add pinctrl driver for NVIDIA's Tegra114 SoC Laxman Dewangan
2013-01-05 12:02 ` Laxman Dewangan
[not found] ` <1357387375-25919-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-07 16:58 ` Stephen Warren [this message]
2013-01-07 16:58 ` Stephen Warren
2013-01-17 8:30 ` [PATCH 1/2] pinctrl: tegra: add support for rcv-sel and drive type Linus Walleij
2013-01-17 8:36 ` Laxman Dewangan
[not found] ` <50F7B801.4020704-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-17 9:58 ` Linus Walleij
2013-01-17 9:58 ` Linus Walleij
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=50EAFEA7.90201@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=praithatha-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.