linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Russell King <linux@arm.linux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Joe Perches <joe@perches.com>,
	Martin Persson <martin.persson@stericsson.com>,
	Stephen Warren <swarren@nvidia.com>,
	Linaro Dev <linaro-dev@lists.linaro.org>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/2] drivers: create a pinmux subsystem v3
Date: Mon, 8 Aug 2011 10:28:49 +0800	[thread overview]
Message-ID: <CAGsJ_4yb4DNt4nSJHJcGMaL+U6KDRNj4sqkULu3jhwN2t_G6Fw@mail.gmail.com> (raw)
In-Reply-To: <CAGsJ_4yKHQGrY4kbwd+VPsg1ggj3wQqoN+uPLmh31RnhbroysQ@mail.gmail.com>

Hi Linus,

>> diff --git a/Documentation/ABI/testing/sysfs-class-pinmux b/Documentation/ABI/testing/sysfs-class-pinmux
>> new file mode 100644
>> index 0000000..c2ea843
>> --- /dev/null
>> +++ b/Documentation/ABI/testing/sysfs-class-pinmux
>> @@ -0,0 +1,11 @@
>> +What:          /sys/class/pinmux/.../name
>> +Date:          May 2011
>> +KernelVersion: 3.1
>
> has this been ready for 3.1? we have been planning to write pinmux
> driver based on this framework.

What is the status of pincfg subsystem? what's the plan about merging
this subsystem?

>
>> +Contact:       Linus Walleij <linus.walleij@linaro.org>
>> +Description:
>> +               Each pinmux directory will contain a field called
>> +               name. This holds a string identifying the pinmux for
>> +               display purposes.
>> +
>> +               NOTE: this will be empty if no suitable name is provided
>> +               by platform or pinmux drivers.
>> diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
>> new file mode 100644
>> index 0000000..c4b6f48
>> --- /dev/null
>> +++ b/Documentation/pinctrl.txt
>> @@ -0,0 +1,397 @@
>> +PINCTRL (PIN CONTROL) subsystem
>> +This document outlines the pin control subsystem in Linux
>> +
>> +This subsystem deals with:
>> +
-barry

  reply	other threads:[~2011-08-08  2:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 16:58 [PATCH 1/2] drivers: create a pinmux subsystem v3 Linus Walleij
2011-06-13 18:11 ` Joe Perches
2011-06-14  9:19   ` Linus Walleij
2011-06-13 19:57 ` Grant Likely
2011-06-14 11:33   ` Linus Walleij
2011-07-09 10:23   ` Mark Brown
2011-08-19 11:59     ` Linus Walleij
2011-06-13 23:28 ` Stephen Warren
2011-06-14 14:25   ` Linus Walleij
2011-06-14 22:11     ` Stephen Warren
2011-06-16 12:47       ` Linus Walleij
2011-06-16 19:10         ` Stephen Warren
2011-06-27 14:34           ` Linus Walleij
2011-06-29 21:23             ` Stephen Warren
2011-08-19 12:34         ` Linus Walleij
2011-07-14  5:57 ` Barry Song
2011-08-08  2:28   ` Barry Song [this message]
2011-08-19 11:53   ` 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=CAGsJ_4yb4DNt4nSJHJcGMaL+U6KDRNj4sqkULu3jhwN2t_G6Fw@mail.gmail.com \
    --to=21cnbao@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=joe@perches.com \
    --cc=lee.jones@linaro.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=martin.persson@stericsson.com \
    --cc=swarren@nvidia.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 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).