public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <ext-jani.1.nikula@nokia.com>
To: ext Trilok Soni <soni.trilok@gmail.com>
Cc: "ext Juha Yrjölä" <juha.yrjola@solidboot.com>,
	linux-omap@vger.kernel.org, dbrownell@users.sourceforge.net
Subject: Re: GPIO switch framework (was: Re: [PATCH] ARM: OMAP: Add support for dynamic GPIO switch update)
Date: Thu, 18 Dec 2008 15:40:49 +0200	[thread overview]
Message-ID: <1229607649.5895.438.camel@jani-desktop> (raw)
In-Reply-To: <5d5443650812180500j67647a34mf8eb99c1f4b24c0a@mail.gmail.com>

On Thu, 2008-12-18 at 18:30 +0530, ext Trilok Soni wrote:

> Why limit to GPIO based switches only? GPIOs should be client of
> switch framework I think, and how h/w implements that switch should be
> hidden by client specific driver.

You're quite right, it's better not to make such unnecessary
limitations. All the more reason to discuss before anyone submits a
truckload of patches for review. :)

Jani.



  reply	other threads:[~2008-12-18 13:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 12:08 [PATCH] ARM: OMAP: Add support for dynamic GPIO switch update Jani Nikula
2008-12-15 12:14 ` Trilok Soni
2008-12-15 13:31   ` Felipe Balbi
2008-12-15 13:22 ` Felipe Balbi
2008-12-15 13:44   ` Jani Nikula
2008-12-15 13:56     ` Felipe Balbi
2008-12-15 13:40 ` Juha Yrjölä
2008-12-15 14:52   ` Jani Nikula
2008-12-15 15:29     ` Juha Yrjölä
2008-12-15 15:58       ` Jani Nikula
2008-12-16  6:05         ` Trilok Soni
2008-12-18 11:42           ` GPIO switch framework (was: Re: [PATCH] ARM: OMAP: Add support for dynamic GPIO switch update) Jani Nikula
2008-12-18 13:00             ` Trilok Soni
2008-12-18 13:40               ` Jani Nikula [this message]
2008-12-19  8:47                 ` Trilok Soni
2008-12-19  8:51                   ` Brian Swetland
2008-12-21 20:26             ` David Brownell

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=1229607649.5895.438.camel@jani-desktop \
    --to=ext-jani.1.nikula@nokia.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=juha.yrjola@solidboot.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=soni.trilok@gmail.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