devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "A.S. Dong" <aisheng.dong@nxp.com>
Cc: jmondi <jacopo@jmondi.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"stefan@agner.ch" <stefan@agner.ch>, Jacky Bai <ping.bai@nxp.com>,
	Andy Duan <fugang.duan@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V3 1/2] dt-bindings: pinctrl: add imx7ulp pinctrl binding doc
Date: Mon, 29 May 2017 10:50:35 +0200	[thread overview]
Message-ID: <CACRpkdaQ0xn8mm6mCemf+dEtOqYgR5eLd296+8CfOOLy9CJ4BA@mail.gmail.com> (raw)
In-Reply-To: <AM3PR04MB3065626F1B45C8459E5765580FE0@AM3PR04MB306.eurprd04.prod.outlook.com>

On Wed, May 24, 2017 at 5:10 AM, A.S. Dong <aisheng.dong@nxp.com> wrote:

>> > +   NOTE: i.MX7ULP PIN_FUNC_ID consists of 4 integers as it shares one
>> mux
>> > +   and config register as follows:
>> > +   <mux_conf_reg input_reg mux_mode input_val>
>>
>> As your PIN_FUNC_ID specifies both the pin ids and their mux settings,
>> shouldn't you use the newly documented 'pinmux' property in place of
>> 'pins'?
>>
>> Please see
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
>> ?id=8d5e7c5df0a6c442373628be5221321172b1badf
>>
>> The current documentation specifies pin ids and mux settings have to be
>> assembled in one single integer, which is not your case, but that can be
>> changed to make it accept an array of integers values if needed.
>>
>
> Thanks for the info.
> Looks good to me.
>
> Shawn & Linus,
> Are you okay with this?
>
> If yes, I can extend the standard 'pinmux' property to support integer array
> and renew the patch series to use it.

After reading Jacopo's commit it seems to make a lot of sense indeed,
so please do this.

Yours,
Linus Walleij

      parent reply	other threads:[~2017-05-29  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 11:43 [PATCH V3 1/2] dt-bindings: pinctrl: add imx7ulp pinctrl binding doc Dong Aisheng
2017-05-23 18:24 ` jmondi
2017-05-24  3:10   ` A.S. Dong
2017-05-25  5:06     ` A.S. Dong
     [not found]       ` <AM3PR04MB306BB77DD89C680DC42636D80FF0-f56W/S9L6NSIzFHTN1kKrAfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2017-05-25  7:42         ` Shawn Guo
2017-05-29  8:50     ` Linus Walleij [this message]

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=CACRpkdaQ0xn8mm6mCemf+dEtOqYgR5eLd296+8CfOOLy9CJ4BA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fugang.duan@nxp.com \
    --cc=jacopo@jmondi.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ping.bai@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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;
as well as URLs for NNTP newsgroup(s).