[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVZQQXx75-0GWCFNnFqEH8S+b0TcWWUGCqgmyzNkyRtYA@mail.gmail.com>
Date: Mon, 3 Nov 2014 20:12:47 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Soren Brinkmann <soren.brinkmann@...inx.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Michal Simek <michal.simek@...inx.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Alessandro Rubini <rubini@...pv.it>,
Heiko Stuebner <heiko@...ech.de>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-rockchip@...ts.infradead.org,
Linux-sh list <linux-sh@...r.kernel.org>
Subject: Re: [PATCH 3/7] pinctrl: pinconf-generic: Allow driver to specify DT params
On Mon, Nov 3, 2014 at 8:05 PM, Soren Brinkmann
<soren.brinkmann@...inx.com> wrote:
> --- a/include/linux/pinctrl/pinctrl.h
> +++ b/include/linux/pinctrl/pinctrl.h
> @@ -117,6 +118,8 @@ struct pinctrl_ops {
> * @confops: pin config operations vtable, if you support pin configuration in
> * your driver
> * @owner: module providing the pin controller, used for refcounting
> + * @num_dt_params: Number of driver-specifid DT parameters
driver-specific
> + * @params: List of DT parameters
Missing @conf_items documentation.
> */
> struct pinctrl_desc {
> const char *name;
> @@ -126,6 +129,11 @@ struct pinctrl_desc {
> const struct pinmux_ops *pmxops;
> const struct pinconf_ops *confops;
> struct module *owner;
> +#if defined(CONFIG_GENERIC_PINCONF) && defined(CONFIG_OF)
> + unsigned int num_dt_params;
> + const struct pinconf_generic_dt_params *params;
> + const struct pin_config_item *conf_items;
> +#endif
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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