All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: device-tree vs gpio-leds gpio_blink_set
Date: Tue, 24 Apr 2012 13:36:40 +0100	[thread overview]
Message-ID: <20120424123639.GC13747@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdZ4RSiqrHU60auvCx9xxZp5CQQzjis+Xz6EVMA+7-8_eg@mail.gmail.com>

On Tue, Apr 24, 2012 at 02:24:16PM +0200, Linus Walleij wrote:
> On Mon, Apr 23, 2012 at 7:49 PM, Mark Brown

> > Another idea would be to use pinctrl and represent the blink as a
> > special function. ?Not sure that's sensible though.

> I would rather say that anything automatically toggling
> a GPIO pin on/off at specified intervals is HW-controlled
> GPIO PWM.

Yes, that's not a million miles away from what I was thinking - the
followup to what I was thinking was that the other function would be a
PWM function.  It's feeling like we might want some sort of generic
interface for handling situations like this and like the open drain
simulation code which was recently added to gpiolib where we end up
crossing subsystems.  In principle you should always use the subsystem
you want directly, the issue comes about when you want to use multiple
sets of functionality and still fall back on the emulations.

> So this would be something that gets to be modeled in the
> PWM subsystem, but there is no such thing (I know Sascha et
> al was working on that at one point.)

Thierry took over the work and last time I saw it things looked like
they were pretty much ready for merge, I'd really expect to see the code
in 3.5 based on the previous state (in fact I was pretty surprised 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120424/c0ba85ea/attachment.sig>

  reply	other threads:[~2012-04-24 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  7:27 device-tree vs gpio-leds gpio_blink_set Arnaud Patard (Rtp)
2012-04-23  7:27 ` [patch 1/1] orion/kirkwood/mv78xx0: add DT support to GPIO Arnaud Patard (Rtp)
2012-04-23 11:22 ` device-tree vs gpio-leds gpio_blink_set Arnd Bergmann
2012-04-23 17:49   ` Mark Brown
2012-04-24 12:24     ` Linus Walleij
2012-04-24 12:36       ` Mark Brown [this message]
2012-04-24 13:04         ` Thierry Reding
2012-04-24 12:39       ` jonsmirl at gmail.com
2012-04-24 12:41         ` jonsmirl at gmail.com
     [not found] <20120423115140.GA15792@lunn.ch>
2012-04-23 12:01 ` Arnaud Patard (Rtp)

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=20120424123639.GC13747@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --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 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.