public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: zonque@gmail•com (Daniel Mack)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 6/6] ARM: dts: add pinctrl in PXA DT files
Date: Mon, 06 Aug 2012 12:32:23 +0200	[thread overview]
Message-ID: <501F9D37.9030809@gmail.com> (raw)
In-Reply-To: <201208060844.29333.arnd@arndb.de>

On 06.08.2012 10:44, Arnd Bergmann wrote:
> On Saturday 28 July 2012, Haojian Zhuang wrote:
>> +Required subnode-properties:
>> +- marvell,pins : An array of strings. Each string contains the name of a pin
>> +                 or group.
>> +- marvell,function     : A string containing the name of the function to mux to the
>> +                 pin or group.
>> +- marvell,drive-strength : An integer value that means the drive strength of a
>> +                        pin.
>> +- marvell,pull-up      : The property means a pin is pull up for input.
>> +- marvell,pull-down : The property means a pin is pull down for input.
>> +- marvell,lowpower-pull-up : The property means a pin is pull up for input in
>> +                         sleep state.
>> +- marvell,lowpower-pull-down : The property means a pin is pull down for input
>> +                           in sleep state.
>> +- marvell,lowpower-drive-high : The property means a pin is driving high for
>> +                            output in sleep state.
>> +- marvell,lowpower-drive-low : The property means a pin is driving low for
>> +                           output in sleep state.
>> +- marvell,lowpower-float : The property means a pin is float in sleep state.
>> +- marvell,lowpower-zero : The property means a pin is not configured in sleep
>> +                       state.
> 
> These (or most of them) look like they are not very Marvell specific. Should
> we try to standardize the way they are set across different bindings?

Yes please. That way we also have a higher chance that implementations
on other platforms will be similar.


Daniel

  reply	other threads:[~2012-08-06 10:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28  6:58 [PATCH 0/6] pinctrl: add DT support in PXA series Haojian Zhuang
2012-07-28  6:58 ` [PATCH 1/6] pinctrl: append new pins and groups in pxa910 Haojian Zhuang
2012-08-05  0:04   ` Linus Walleij
2012-07-28  6:58 ` [PATCH 2/6] pinctrl: add pinconf support in pxa3xx Haojian Zhuang
2012-07-28 10:22   ` Daniel Mack
2012-07-28 15:28     ` Haojian Zhuang
2012-08-05  0:05   ` Linus Walleij
2012-07-28  6:58 ` [PATCH 3/6] pinctrl: support dt in pxa series Haojian Zhuang
2012-08-05  0:07   ` Linus Walleij
2012-07-28  6:58 ` [PATCH 4/6] pinctrl: append new groups of mmp2 Haojian Zhuang
2012-08-05  0:07   ` Linus Walleij
2012-07-28  6:58 ` [PATCH 5/6] ARM: mmp: select pinctrl for boards with DT Haojian Zhuang
2012-08-05  0:08   ` Linus Walleij
2012-07-28  6:58 ` [PATCH 6/6] ARM: dts: add pinctrl in PXA DT files Haojian Zhuang
2012-08-05  0:09   ` Linus Walleij
2012-08-06  8:44   ` Arnd Bergmann
2012-08-06 10:32     ` Daniel Mack [this message]
2012-08-06 10:33     ` Haojian Zhuang
2012-08-07  6:49     ` Linus Walleij
2012-08-09 14:28       ` Daniel Mack
2012-08-10 10:56         ` Linus Walleij
2012-08-13  9:43           ` Daniel Mack
2012-08-13 14:11             ` 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=501F9D37.9030809@gmail.com \
    --to=zonque@gmail$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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