linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: pinctrl-imx: add imx35 pinctrl driver
Date: Tue, 7 Aug 2012 10:49:04 +0200	[thread overview]
Message-ID: <20120807084904.GA9888@pengutronix.de> (raw)
In-Reply-To: <CAP1dx+wRZea8o8KTGRDCMtQkt7EjDRN5EoFek80OKqJgTxbvZA@mail.gmail.com>

Hi,

On Tue, Aug 07, 2012 at 04:04:01PM +0800, Dong Aisheng wrote:
> Some minor format comment.
> On 2 August 2012 23:39, Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> wrote:
> ........
> > +Required properties:
> > +- compatible: "fsl,imx35-iomuxc"
> > +- fsl,pins: two integers array, represents a group of pins mux and config
> > +  setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
> > +  pin working on a specific function, CONFIG is the pad setting value like
> > +  pull-up for this pin. Please refer to imx53 datasheet for the valid pad
> s/imx53/imx35
obviously.

> > +See below for available PIN_FUNC_ID for imx35:
> > +# grep '   IMX_PIN_REG' drivers/pinctrl/pinctrl-imx35.c | awk '{ print NR-1 " " $8 }'
> > +0 MX35_PAD_CAPTURE__GPT_CAPIN1
> > +1 MX35_PAD_CAPTURE__GPT_CMPOUT2
> I'm not sure if you can use the format as exist IMX PIN_FUNC_ID tables as:
> MX35_PAD_CAPTURE__GPT_CAPIN1        0
> MX35_PAD_CAPTURE__GPT_CMPOUT2    1
I choosed to switch the order here to have a more column like format.
the length of the numbers is more uniform. I can switch if you want.

> Maybe the difficulty is the command (i did not know how to do it before),
> If you know, we can do like that.
> Anyway, it's not a big issue and does not block an ack.
> 
> > +enum imx35_pads {
> > +       /* sed -r -n 's@^#define MX35_PAD_([0-9A-Z_]*)__([0-9A-Z_]*)\s+IOMUX_PAD\(\s*([0-9a-fx]*),\s+([0-9a-fx]*),\s+([0-9a-fx]*),\s+([0-9a-fx]*),\s+([0-9]*),\s*NO_PAD_CTRL\)@\tMX35_PAD_\1, at p' arch/arm/plat-mxc/include/mach/iomux-mx35.h | uniq */
> > +       MX35_PAD_CAPTURE,
> > +       MX35_PAD_COMPARE,
> > +       MX35_PAD_WDOG_RST,
> > +       MX35_PAD_GPIO1_0,
> > +       MX35_PAD_GPIO1_1,
> > +       MX35_PAD_GPIO2_0,
> > +       MX35_PAD_GPIO3_0,
> Can we use the format as exist one?
> enum imx53_pads {
>         MX53_PAD_GPIO_19 = 1,
>         MX53_PAD_KEY_COL0 = 2,
>         MX53_PAD_KEY_ROW0 = 3,
>         MX53_PAD_KEY_COL1 = 4,
> .......
> }
> Then people can easy know its pin id.
> I'm wondering there may be still some debug info are using pin id
> then the above format helps.
I didn't see output referring to pin ids (which doesn't mean it doesn't
exist of course). I don't care much and wondered why you started at 1
and not 0. All it all it was just lazyness on my side not to add the
numers.
 
> > +module_exit(imx35_pinctrl_exit);
> > +MODULE_AUTHOR("Dong Aisheng <dong.aisheng@linaro.org>");
> Not your name?
No, I only did

	cp drivers/pinctrl/pinctrl-imx{51,35}.c

and fixed the tables and names for i.MX35. It's OK for me when you get
the blame. :-)

> Otherwise,
> you can add my ACK.
Thanks
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2012-08-07  8:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 15:39 [PATCH] pinctrl: pinctrl-imx: add imx35 pinctrl driver Uwe Kleine-König
2012-08-03 12:25 ` Shawn Guo
2012-08-06 14:23   ` Uwe Kleine-König
2012-08-03 20:37 ` Stephen Warren
2012-08-07  8:04 ` Dong Aisheng
2012-08-07  8:49   ` Uwe Kleine-König [this message]
2012-08-07 11:34     ` Dong Aisheng
2012-08-09 17:22 ` Uwe Kleine-König
2012-08-09 16:27   ` Uwe Kleine-König
2012-08-10 11:01     ` Linus Walleij
2012-08-10 12:18       ` Uwe Kleine-König
2012-08-10 12:29         ` Shawn Guo
2012-08-10  3:14   ` Dong Aisheng
2012-08-10  4:45     ` Uwe Kleine-König
2012-08-13 13:57   ` 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=20120807084904.GA9888@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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 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).