From: Bill Gatliff <bgat@billgatliff.com>
To: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
linux-embedded@vger.kernel.org
Subject: Re: [RFC 5/6] [PWM] Install new Atmel PWMC driver in Kconfig, expunge old one
Date: Thu, 09 Oct 2008 09:04:00 -0500 [thread overview]
Message-ID: <48EE0F50.4020405@billgatliff.com> (raw)
In-Reply-To: <20081009141756.0da223ca@hcegtvedt>
Hans-Christian Egtvedt wrote:
> On Thu, 9 Oct 2008 14:16:01 +0200
> Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
>
>> Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> wrote:
>>> You know that there are other users of ATMEL_PWM ?
>>>
>>> There is a atmel-pwm-bl driver in drivers/video/backlight which
>>> could probably be converted to pwm-bl using the new pwm framework.
>> There's already a pwm_bl driver there which I'm assuming is using the
>> generic pwm API. Hopefully, we can simply delete the atmel-pwm-bl
>> driver. Maybe some board code needs updating before that can happen
>> though.
Yes. I think atmel-pwm-bl goes away completely, and video/backlight/pwm_bl.c
gets modified (slightly) to use the new PWM API and becomes the general
backlight-via-PWM-peripheral solution. After that, anyone who wants to write a
backend pwm_device driver suddenly can use their peripheral for backlights (and
other stuff) out-of-the-box.
I just glanced over drivers/video/backlight, it looks like there are a couple
other implementations that could move over to Generic PWM as well.
> That would be the Favr-32 board, since the atmel-pwm-bl driver was
> developed for that board.
>
> Weird how this stuff almost was inserted almost in parallel.
Indeed. But also a bit tragic--- some wasted effort. :(
Not entirely weird, however, since I try to follow AVR32 as closely as I do ARM.
I have an NGW100 and an STK1000, in addition to about five different ARM
machines including ones based on the AT91SAM9263. These common frameworks help
me slide into insanity a little more slowly. :)
(I have some PPC and MIPS boards, too. Occupational hazard).
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2008-10-09 14:04 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 16:43 [RFC 0/6] Proposal for a Generic PWM Device API Bill Gatliff
2008-10-08 16:43 ` [RFC 1/6] [PWM] Generic PWM API implementation Bill Gatliff
2008-10-09 8:17 ` Marc Pignat
2008-10-10 3:20 ` Benjamin Herrenschmidt
2008-10-10 4:07 ` Bill Gatliff
2008-10-10 14:07 ` Bill Gatliff
2008-10-13 16:04 ` Scott Wood
2008-10-08 16:43 ` [RFC 2/6] [PWM] Changes to existing include/linux/pwm.h to adapt to generic PWM API Bill Gatliff
2008-10-08 16:43 ` [RFC 1/6] [PWM] Generic PWM API implementation Bill Gatliff
2008-10-08 16:43 ` [RFC 2/6] [PWM] Changes to existing include/linux/pwm.h to adapt to generic PWM API Bill Gatliff
2008-10-08 16:43 ` [RFC 3/6] [PWM] Documentation Bill Gatliff
2008-10-08 16:43 ` Bill Gatliff
2008-10-08 16:43 ` [RFC 4/6] [PWM] Driver for Atmel PWMC peripheral Bill Gatliff
2008-10-08 16:43 ` Bill Gatliff
2008-10-08 16:43 ` [RFC 5/6] [PWM] Install new Atmel PWMC driver in Kconfig, expunge old one Bill Gatliff
2008-10-09 5:21 ` 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 [this message]
2008-10-09 13:40 ` Bill Gatliff
2008-10-09 13:44 ` Hans-Christian Egtvedt
2008-10-08 16:43 ` Bill Gatliff
2008-10-08 16:43 ` [RFC 6/6] [PWM] New LED driver and trigger that use PWM API Bill Gatliff
2008-10-08 16:43 ` 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
2008-10-09 21:08 ` Matt Sealey
2008-10-09 21:29 ` Bill Gatliff
2008-10-10 3:20 ` Benjamin Herrenschmidt
2008-10-10 4:06 ` Bill Gatliff
2008-10-10 5:02 ` Benjamin Herrenschmidt
2008-10-10 5:06 ` Jon Smirl
2008-10-10 14:04 ` Bill Gatliff
2008-10-10 14:12 ` Jon Smirl
2008-10-10 20:45 ` Jon Loeliger
2008-10-12 2:32 ` Matt Sealey
2008-10-10 9:00 ` Geert Uytterhoeven
2008-10-10 9:00 ` Geert Uytterhoeven
2008-10-10 9:36 ` Paul Mundt
2008-10-10 9:36 ` Paul Mundt
2008-10-10 9:46 ` David Woodhouse
2008-10-10 9:46 ` David Woodhouse
2008-10-10 13:59 ` Bill Gatliff
2008-10-10 13:59 ` Bill Gatliff
2008-10-10 14:03 ` Bill Gatliff
2008-10-10 14:03 ` Bill Gatliff
2008-10-10 14:32 ` Haavard Skinnemoen
2008-10-10 14:32 ` Haavard Skinnemoen
2008-10-10 17:28 ` Paul Mundt
2008-10-10 19:15 ` Bill Gatliff
2008-10-10 19:15 ` Bill Gatliff
2008-10-10 13:59 ` Bill Gatliff
2008-10-10 13:59 ` Bill Gatliff
2008-10-10 17:40 ` Paul Mundt
2008-10-10 17:40 ` Paul Mundt
2008-10-10 19:42 ` Bill Gatliff
2008-10-13 7:40 ` Geert Uytterhoeven
2008-10-13 7:40 ` Geert Uytterhoeven
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=48EE0F50.4020405@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=hans-christian.egtvedt@atmel.com \
--cc=linux-embedded@vger.kernel.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.