All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Engelmayer <christian.engelmayer@frequentis.com>
To: <grant.likely@secretlab.ca>, <linus.walleij@stericsson.com>,
	<devicetree-discuss@lists.ozlabs.org>
Cc: linuxppc-dev@lists.ozlabs.org, christian.engelmayer@frequentis.com
Subject: Re: [RFC] Configure GPIO settings via the device tree
Date: Thu, 19 Jul 2012 10:39:17 +0200	[thread overview]
Message-ID: <20120719103917.78e01091@frequentis.com> (raw)
In-Reply-To: <20120713100440.7a80e05f@frequentis.com>

Hello,

As there was no response to my question I assume that I see it correctly
that at the moment the only 2 options for setting up GPIO configurations
is either via platform-specific code by eg. platform_data or via userspace?

Would there be a common use of defining GPIO configurations via a device
tree and applying those settings via a generic, platform-unaware driver?

Regards,
Christian


On Fri, 13 Jul 2012 10:04:40 +0200
Christian Engelmayer <christian.engelmayer@frequentis.com> wrote:

> Hello,
> 
> I am looking for a way to configure GPIO initial settings and exports to the
> userspace via Sysfs in a generic way via a device tree.
> 
> The purpose would be to have the same features as when initializing and
> exporting pins via platform code, eg.
> 
> 	static struct gpio leds_gpios[] = {
> 		{ 32, GPIOF_OUT_INIT_HIGH, "Power LED" }, /* default to ON */
> 		{ 33, GPIOF_OUT_INIT_LOW,  "Green LED" }, /* default to OFF */
> 		{ 34, GPIOF_OUT_INIT_LOW,  "Red LED"   }, /* default to OFF */
> 		{ 35, GPIOF_OUT_INIT_LOW,  "Blue LED"  }, /* default to OFF */
> 		{ ... },
> 	};
> 
> ,however, with no need for the kernel to know anything more about those pins
> and their later handling by simple userpsace drivers than the setup information
> provided in the device tree.
> 
> This should also attack the problem of unstable GPIO numbers in the case of
> daughtercards on different base boards and would help provide a defined API
> to the userspace based on pin labels with the board specifics hidden in one
> place in the device tree.
> 
> Is there already a way for realizing such a scenario ?
> 
> Regards,
> Christian

WARNING: multiple messages have this Message-ID (diff)
From: Christian Engelmayer <christian.engelmayer@frequentis.com>
To: grant.likely@secretlab.ca, linus.walleij@stericsson.com,
	devicetree-discuss@lists.ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org, christian.engelmayer@frequentis.com
Subject: Re: [RFC] Configure GPIO settings via the device tree
Date: Thu, 19 Jul 2012 10:39:17 +0200	[thread overview]
Message-ID: <20120719103917.78e01091@frequentis.com> (raw)
In-Reply-To: <20120713100440.7a80e05f@frequentis.com>

Hello,

As there was no response to my question I assume that I see it correctly
that at the moment the only 2 options for setting up GPIO configurations
is either via platform-specific code by eg. platform_data or via userspace?

Would there be a common use of defining GPIO configurations via a device
tree and applying those settings via a generic, platform-unaware driver?

Regards,
Christian


On Fri, 13 Jul 2012 10:04:40 +0200
Christian Engelmayer <christian.engelmayer@frequentis.com> wrote:

> Hello,
> 
> I am looking for a way to configure GPIO initial settings and exports to the
> userspace via Sysfs in a generic way via a device tree.
> 
> The purpose would be to have the same features as when initializing and
> exporting pins via platform code, eg.
> 
> 	static struct gpio leds_gpios[] = {
> 		{ 32, GPIOF_OUT_INIT_HIGH, "Power LED" }, /* default to ON */
> 		{ 33, GPIOF_OUT_INIT_LOW,  "Green LED" }, /* default to OFF */
> 		{ 34, GPIOF_OUT_INIT_LOW,  "Red LED"   }, /* default to OFF */
> 		{ 35, GPIOF_OUT_INIT_LOW,  "Blue LED"  }, /* default to OFF */
> 		{ ... },
> 	};
> 
> ,however, with no need for the kernel to know anything more about those pins
> and their later handling by simple userpsace drivers than the setup information
> provided in the device tree.
> 
> This should also attack the problem of unstable GPIO numbers in the case of
> daughtercards on different base boards and would help provide a defined API
> to the userspace based on pin labels with the board specifics hidden in one
> place in the device tree.
> 
> Is there already a way for realizing such a scenario ?
> 
> Regards,
> Christian

  reply	other threads:[~2012-07-19  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  8:04 [RFC] Configure GPIO settings via the device tree Christian Engelmayer
2012-07-13  8:04 ` Christian Engelmayer
2012-07-19  8:39 ` Christian Engelmayer [this message]
2012-07-19  8:39   ` Christian Engelmayer

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=20120719103917.78e01091@frequentis.com \
    --to=christian.engelmayer@frequentis.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@stericsson.com \
    --cc=linuxppc-dev@lists.ozlabs.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 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.