All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH 1/2] pinctrl: bindings: pinctrl: Add support for TI's IODelay configuration
Date: Wed, 18 Mar 2015 02:30:54 +0100	[thread overview]
Message-ID: <CACRpkdZ1faucps07jaT9kOyviC+Sw6gPkbF=cAGCUj+DiaEgTA@mail.gmail.com> (raw)
In-Reply-To: <54FF38F3.2030703@ti.com>

On Tue, Mar 10, 2015 at 7:33 PM, Nishanth Menon <nm@ti.com> wrote:
> On 03/10/2015 12:31 PM, Tony Lindgren wrote:

>> Yes except I'd make use of some kind of #pinctrl-cells here just like
>> interrupt controller has #interrupt-cells. Then you can have the values
>> seprate and the controller knows what to do with them based on the
>> compatible flag and #pinctrl-cells.
>
> Something like the following I suppose, where pinctrl-cells is optional?
>
> dra7_pmx_core: pinmux@4a003400 {
>         compatible = "ti,dra7-padconf", "pinctrl-single";
>         reg = <0x4a003400 0x0464>;
>         #address-cells = <1>;
>         #size-cells = <0>;
>         #interrupt-cells = <1>;
>         interrupt-controller;
>         pinctrl-single,register-width = <32>;
>         pinctrl-single,function-mask = <0x3fffffff>;
> };
>
> dra7_iodelay_core: padconf@4844a000 {
>         compatible = "ti,dra7-iodelay";
>         reg = <0x4844a000 0x0d1c>;
>         #address-cells = <1>;
>         #size-cells = <0>;
>         #pinctrl-cells = <2>;
> };
>
> Linus,
>
> I hope you are ok with the above?

Hm depends on where the documentation hits I guess?

Such a generic cell count property has to be to the generic
pinctrl-bindings.txt document if I read it right.

Overall I guess this will be acceptable but you really need to
reuse some more code between this driver and pinctrl-single.c
if I read it right.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] pinctrl: bindings: pinctrl: Add support for TI's IODelay configuration
Date: Wed, 18 Mar 2015 02:30:54 +0100	[thread overview]
Message-ID: <CACRpkdZ1faucps07jaT9kOyviC+Sw6gPkbF=cAGCUj+DiaEgTA@mail.gmail.com> (raw)
In-Reply-To: <54FF38F3.2030703@ti.com>

On Tue, Mar 10, 2015 at 7:33 PM, Nishanth Menon <nm@ti.com> wrote:
> On 03/10/2015 12:31 PM, Tony Lindgren wrote:

>> Yes except I'd make use of some kind of #pinctrl-cells here just like
>> interrupt controller has #interrupt-cells. Then you can have the values
>> seprate and the controller knows what to do with them based on the
>> compatible flag and #pinctrl-cells.
>
> Something like the following I suppose, where pinctrl-cells is optional?
>
> dra7_pmx_core: pinmux at 4a003400 {
>         compatible = "ti,dra7-padconf", "pinctrl-single";
>         reg = <0x4a003400 0x0464>;
>         #address-cells = <1>;
>         #size-cells = <0>;
>         #interrupt-cells = <1>;
>         interrupt-controller;
>         pinctrl-single,register-width = <32>;
>         pinctrl-single,function-mask = <0x3fffffff>;
> };
>
> dra7_iodelay_core: padconf at 4844a000 {
>         compatible = "ti,dra7-iodelay";
>         reg = <0x4844a000 0x0d1c>;
>         #address-cells = <1>;
>         #size-cells = <0>;
>         #pinctrl-cells = <2>;
> };
>
> Linus,
>
> I hope you are ok with the above?

Hm depends on where the documentation hits I guess?

Such a generic cell count property has to be to the generic
pinctrl-bindings.txt document if I read it right.

Overall I guess this will be acceptable but you really need to
reuse some more code between this driver and pinctrl-single.c
if I read it right.

Yours,
Linus Walleij

  parent reply	other threads:[~2015-03-18  1:30 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  0:00 [PATCH 0/2] pinctrl: Introduce support for iodelay module in TI SoCs Nishanth Menon
2015-03-04  0:00 ` Nishanth Menon
2015-03-04  0:00 ` Nishanth Menon
2015-03-04  0:00 ` [PATCH 1/2] pinctrl: bindings: pinctrl: Add support for TI's IODelay configuration Nishanth Menon
2015-03-04  0:00   ` Nishanth Menon
2015-03-04  0:00   ` Nishanth Menon
2015-03-10 10:39   ` Linus Walleij
2015-03-10 10:39     ` Linus Walleij
2015-03-10 10:39     ` Linus Walleij
2015-03-10 15:06     ` Nishanth Menon
2015-03-10 15:06       ` Nishanth Menon
2015-03-10 15:06       ` Nishanth Menon
2015-03-10 15:33     ` Tony Lindgren
2015-03-10 15:33       ` Tony Lindgren
2015-03-10 15:33       ` Tony Lindgren
2015-03-10 17:25       ` Nishanth Menon
2015-03-10 17:25         ` Nishanth Menon
2015-03-10 17:25         ` Nishanth Menon
2015-03-10 17:31         ` Tony Lindgren
2015-03-10 17:31           ` Tony Lindgren
2015-03-10 17:31           ` Tony Lindgren
2015-03-10 18:33           ` Nishanth Menon
2015-03-10 18:33             ` Nishanth Menon
2015-03-10 18:33             ` Nishanth Menon
2015-03-10 19:20             ` Nishanth Menon
2015-03-10 19:20               ` Nishanth Menon
2015-03-10 19:20               ` Nishanth Menon
2015-03-18  1:30             ` Linus Walleij [this message]
2015-03-18  1:30               ` Linus Walleij
2015-03-18  1:30               ` Linus Walleij
2015-03-18  1:41               ` Tony Lindgren
2015-03-18  1:41                 ` Tony Lindgren
2015-03-18  1:41                 ` Tony Lindgren
2015-04-15  1:29                 ` Lennart Sorensen
2015-04-15  1:29                   ` Lennart Sorensen
2015-04-15  1:29                   ` Lennart Sorensen
     [not found]                   ` <20150415012910.GA29560-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys@public.gmane.org>
2015-04-15 16:51                     ` Nishanth Menon
2015-04-15 16:51                       ` Nishanth Menon
2015-04-15 16:51                       ` Nishanth Menon
2015-04-15 18:44                       ` Lennart Sorensen
2015-04-15 18:44                         ` Lennart Sorensen
2015-04-15 18:44                         ` Lennart Sorensen
2015-04-15 18:53                         ` Nishanth Menon
2015-04-15 18:53                           ` Nishanth Menon
2015-04-15 18:53                           ` Nishanth Menon
2015-03-04  0:00 ` [PATCH 2/2] pinctrl: Introduce TI IOdelay configuration driver Nishanth Menon
2015-03-04  0:00   ` Nishanth Menon
2015-03-04  0:00   ` Nishanth Menon
2015-03-04 22:58   ` Paul Bolle
2015-03-04 22:58     ` Paul Bolle
2015-03-04 22:58     ` Tony Lindgren
2015-03-04 22:58       ` Tony Lindgren
2015-03-05  2:22       ` Nishanth Menon
2015-03-05  2:22         ` Nishanth Menon
2015-03-05  2:22         ` Nishanth Menon
2015-03-10 11:03   ` Linus Walleij
2015-03-10 11:03     ` Linus Walleij
2015-03-10 11:03     ` Linus Walleij
2015-03-11 12:39     ` Nishanth Menon
2015-03-11 12:39       ` Nishanth Menon
2015-03-11 12:39       ` Nishanth Menon

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='CACRpkdZ1faucps07jaT9kOyviC+Sw6gPkbF=cAGCUj+DiaEgTA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=tony@atomide.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 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.