From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Bill Gatliff <bgat@billgatliff.com>,
linux-embedded@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH 0/6] Generic PWM API implementation
Date: Sat, 28 Nov 2009 13:54:11 -0800 [thread overview]
Message-ID: <200911281354.11653.david-b@pacbell.net> (raw)
In-Reply-To: <20091123180920.GA1404@rakim.wolfsonmicro.main>
On Monday 23 November 2009, Mark Brown wrote:
> Judging from some of the other messages in the thread I suspect you're
> thinking of a much closer mapping between PWM and GPIO pins - many SoCs
> do have distinct PWM controllers that aren't terribly tied to a GPIO
> pin.
Sometimes they can be coupled to one of several pins ... possibly
even outputting to several at the same time.
> For them the whole concept of requesting a "pin" or having the PWM
> controller be tied to a particular pin is going to be at best confusing,
> you really do want to request the PWM controller itself and let the pin
> mux setup figure out where that emerges from the SoC.
Nicely put. At some level one ends with something like "pwm.2 channel 3"
getting allocated, and does not care about pins except as more low-level
artifacts to be ignored outside of board setup code.
- Dave
next prev parent reply other threads:[~2009-11-28 21:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 18:14 [PATCH 0/6] Generic PWM API implementation Bill Gatliff
2008-10-15 18:14 ` [PATCH 1/6] [PWM] " Bill Gatliff
2008-10-17 15:59 ` Mike Frysinger
2008-11-04 20:16 ` Bill Gatliff
2008-11-04 20:51 ` Mike Frysinger
2008-11-04 23:55 ` David Brownell
2008-11-05 0:17 ` Mike Frysinger
2008-11-05 2:59 ` Bill Gatliff
2008-11-05 5:08 ` David Brownell
2008-11-05 2:56 ` Bill Gatliff
2008-10-15 18:14 ` [PATCH 2/6] [PWM] Changes to existing include/linux/pwm.h to adapt to generic PWM API Bill Gatliff
2008-10-15 18:14 ` [PATCH 3/6] [PWM] Documentation Bill Gatliff
2008-10-15 18:14 ` [PATCH 4/6] [PWM] Driver for Atmel PWMC peripheral Bill Gatliff
2008-10-15 18:14 ` [PATCH 5/6] [PWM] Install new Atmel PWMC driver in Kconfig, expunge old one Bill Gatliff
2008-10-15 18:14 ` [PATCH 6/6] [PWM] New LED driver and trigger that use PWM API Bill Gatliff
2009-11-13 19:08 ` [PATCH 0/6] Generic PWM API implementation Grant Likely
2009-11-14 4:22 ` Mike Frysinger
2009-11-14 7:55 ` Grant Likely
2009-11-17 7:47 ` David Brownell
2009-11-17 15:48 ` Bill Gatliff
2009-11-17 16:53 ` David Brownell
2009-11-20 22:51 ` Grant Likely
2009-11-20 22:14 ` Grant Likely
2009-11-23 14:12 ` Bill Gatliff
2009-11-23 17:39 ` Grant Likely
2009-11-23 20:51 ` Albrecht Dreß
2009-11-28 21:38 ` David Brownell
2009-11-28 21:59 ` David Brownell
2009-11-17 15:45 ` Bill Gatliff
2009-11-17 8:27 ` David Brownell
2009-11-17 15:54 ` Bill Gatliff
2009-11-20 22:21 ` Grant Likely
2009-11-23 14:13 ` Bill Gatliff
2009-11-23 17:40 ` Grant Likely
2009-11-23 15:29 ` Mark Brown
2009-11-23 17:44 ` Grant Likely
2009-11-23 18:09 ` Mark Brown
2009-11-28 21:54 ` David Brownell [this message]
2009-11-17 15:39 ` Bill Gatliff
2009-11-20 22:49 ` Grant Likely
2009-11-28 21:28 ` 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=200911281354.11653.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=bgat@billgatliff.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-embedded@vger.kernel.org \
--cc=vapier.adi@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;
as well as URLs for NNTP newsgroup(s).