[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYb+f1OnH5Tdy62gw=0g_3+S0Un0NTTGj1Jodv+wE5jKA@mail.gmail.com>
Date: Thu, 16 Jul 2015 09:22:48 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/7] pinctrl: UniPhier: add UniPhier PH1-LD4 pinctrl driver
On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
> Add pin configuration and pinmux support for UniPhier PH1-LD4 SoC.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
> ---
>
> Changes in v2:
> - sort groups and funcs alphabetically
> - add missing "emmc_dat8" group
> - add i2c pin-mux settings
> - sort members of platform_driver
> - change to tristate
> - add THIS_MODULE to pinctrl_desc
> - use module_platform_driver
Patch applied.
> +static const struct of_device_id ph1_ld4_pinctrl_match[] = {
> + { .compatible = "socionext,ph1-ld4-pinctrl" },
> + { /* sentinel */ }
> +};
I didn't see any device tree bindings in this patch series.
That is OK, send them separate, I see only compatible strings
and standard bindings.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists