From: Bill Gatliff <bgat@billgatliff.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-embedded@vger.kernel.org
Subject: Re: [RFC 0/6] Proposal for a Generic PWM Device API
Date: Fri, 10 Oct 2008 08:59:08 -0500 [thread overview]
Message-ID: <48EF5FAC.1060807@billgatliff.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810101054140.12257@vixen.sonytel.be>
Geert Uytterhoeven wrote:
>
> Were did you actually sent them to? Apparently you sent them to each mailing
> list (at least linux-embedded and linuxppc-dev) _separately_ (or using bcc).
I sent them separately to linux-embedded, linuxppc-dev, and linux-arm-kernel.
Those three groups seemed to have the developers who were most likely to provide
a motivated review and constructive response; unfortunately, some are
subscriber-only and so I couldn't just cross-post. I was expecting some
criticism for this, but I'm not sure there's a good alternative.
I don't like the idea of posting in so many places, but PWM is a pretty
expansive topic: just about every SoC under the sun has some ability to do PWM,
and people use the signals for all sorts of things. Both have to be taken into
consideration by the API, hence I need lots of review and feedback.
There isn't a lot of traffic on linux-embedded, and I'm not sure how many people
who read linux-arm-kernel also read linuxppc-dev. Lkml's topic coverage is
huge, so I don't know how many hardcore embedded developers I would encounter
there. I was hoping for a round of feedback at a lower level before pushing
anything upstream like that.
> Hence different people may give the same comments without knowing about each
> other, and you may have to explain everything multiple times.
Hasn't been a problem so far. I posted the first version of the code on l-a-k,
and got some feedback on the pwm_device API and a lot of feedback on the way
users wanted to use the API to realize applications. I incorporated all of it,
and in this "release" I broadened the exposure per recommendations received from
l-a-k.
> I would go for lkml and linux-embedded, _together_.
So, you're saying the same thing as me, basically. But leaving out the lists
with very high ratios of device-specific domain knowledge, which is important
for the backend parts of what I'm proposing. Blackfin's PWM-capable peripherals
work differently from those commonly found in ARM and PPC, for example. I
haven't run anything by the MIPS or AVR guys, but I'm guessing they would have
something to add, too.
I'm beginning to appreciate what everyone must have had to deal with for GPIO. :)
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2008-10-10 13:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 1/6] [PWM] Generic PWM API implementation Bill Gatliff
2008-10-08 19:27 ` [RFC 0/6] Proposal for a Generic PWM Device API Mike Frysinger
2008-10-09 2:23 ` Bill Gatliff
2008-10-09 2:29 ` Bill Gatliff
2008-10-09 2:32 ` Mike Frysinger
2008-10-09 3:46 ` Bill Gatliff
2008-10-09 4:05 ` Mike Frysinger
2008-10-09 4:18 ` Bill Gatliff
2008-10-09 4:33 ` Mike Frysinger
[not found] ` <4b5c3aa2b1bc2b7efad834da49c2dec8c0a8726b.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 2/6] [PWM] Changes to existing include/linux/pwm.h to adapt to generic PWM API Bill Gatliff
[not found] ` <88de40673cc33e014928c2ee3a86bdac566021c8.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 3/6] [PWM] Documentation Bill Gatliff
[not found] ` <7b16004ca5f8030184c2de96cbcee38657d56252.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 4/6] [PWM] Driver for Atmel PWMC peripheral Bill Gatliff
[not found] ` <5640f37b779f953c83e79c16b2a0466c0f5da702.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 5/6] [PWM] Install new Atmel PWMC driver in Kconfig, expunge old one Bill Gatliff
[not found] ` <475b4a5985463015fdfa943b9835ab8136dbc06a.1223482372.git.bgat@billgatliff.com>
2008-10-08 16:43 ` [RFC 6/6] [PWM] New LED driver and trigger that use PWM API Bill Gatliff
2008-10-09 5:21 ` [RFC 5/6] [PWM] Install new Atmel PWMC driver in Kconfig, expunge old one Hans-Christian Egtvedt
2008-10-09 12:16 ` Haavard Skinnemoen
2008-10-09 12:17 ` Hans-Christian Egtvedt
2008-10-09 14:04 ` Bill Gatliff
2008-10-09 13:40 ` Bill Gatliff
2008-10-09 13:44 ` Hans-Christian Egtvedt
2008-10-09 8:17 ` [RFC 1/6] [PWM] Generic PWM API implementation Marc Pignat
[not found] ` <1223608819.8157.127.camel@pasglop>
[not found] ` <48EED4D1.2040506@billgatliff.com>
2008-10-10 9:00 ` [RFC 0/6] Proposal for a Generic PWM Device API Geert Uytterhoeven
2008-10-10 9:36 ` Paul Mundt
2008-10-10 9:46 ` David Woodhouse
2008-10-10 13:59 ` Bill Gatliff
2008-10-10 14:03 ` Bill Gatliff
2008-10-10 14:32 ` Haavard Skinnemoen
2008-10-10 17:28 ` Paul Mundt
2008-10-10 19:15 ` Bill Gatliff
2008-10-10 13:59 ` Bill Gatliff [this message]
2008-10-10 17:40 ` Paul Mundt
2008-10-10 19:42 ` Bill Gatliff
2008-10-13 7:40 ` Geert Uytterhoeven
2008-10-08 16:43 Bill Gatliff
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=48EF5FAC.1060807@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=benh@kernel.crashing.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@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 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).