From: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Bill Gatliff <bgat@billgatliff.com>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux-embedded@vger.kernel.org
Subject: Re: [GIT PULL] Generic PWM Device API
Date: Mon, 28 Feb 2011 12:18:09 +0000 [thread overview]
Message-ID: <4D6B9281.4060700@cam.ac.uk> (raw)
In-Reply-To: <4D6B86EE.1050908@cam.ac.uk>
On 02/28/11 11:28, Jonathan Cameron wrote:
> On 02/28/11 10:31, Sascha Hauer wrote:
>> On Sun, Feb 27, 2011 at 09:38:38PM -0600, Bill Gatliff wrote:
>>> Andrew, Linus:
>>>
>>>
>>> The git repository described in the following pull request implements
>>> a generic PWM device driver API. This API is intended to eventually
>>> supercede the existing PWM device drivers, but during a migration
>>> period will coexist peacefully with them.
>>
>> Sorry for the late answer, but it took some time to read the patches
>> again.
>>
>> Is it a good idea to have to APIs for the same thing in the kernel?
>> The old API has users whereas the new API has none. How can we migrate
>> from one API to the other when for example the backlight pwm driver
>> depends on the old API, SoC level drivers implement the old API, but
>> the atmel pwm driver is only available for the new API?
>>
> See the info in Bill's previous postings. He has other drivers queued
> up but wants to break up the review burden by merging this core stuff
> first...
>
Come to think of it, Bill, could you post these at this stage to
show the full benefit of this move?
prev parent reply other threads:[~2011-02-28 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 3:38 [GIT PULL] Generic PWM Device API Bill Gatliff
2011-02-28 4:45 ` Greg KH
[not found] ` <AANLkTinEX8ascZeZG7HJB=_UGVbbPatpcNp5B2__mbVh@mail.gmail.com>
2011-02-28 16:50 ` Greg KH
2011-02-28 10:31 ` Sascha Hauer
2011-02-28 11:28 ` Jonathan Cameron
2011-02-28 12:18 ` Jonathan Cameron [this message]
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=4D6B9281.4060700@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=bgat@billgatliff.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=torvalds@linux-foundation.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).