From: Jonathan Cameron <jic23@cam.ac.uk>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: michael.hennerich@analog.com, linux-iio@vger.kernel.org,
drivers@analog.com, device-drivers-devel@blackfin.uclinux.org
Subject: Re: [Device-drivers-devel] [PATCH] IIO: trigger: New Blackfin specific trigger driver iio-trig-bfin-timer
Date: Wed, 23 Feb 2011 11:08:42 +0000 [thread overview]
Message-ID: <4D64EABA.2030005@cam.ac.uk> (raw)
In-Reply-To: <AANLkTikKRR4JOxS0e_7ezZu-AvN4d9=vtE2BEW=mq4yj@mail.gmail.com>
On 02/22/11 22:35, Mike Frysinger wrote:
> On Tue, Feb 22, 2011 at 10:03, Jonathan Cameron wrote:
>> On 02/16/11 13:42, michael.hennerich@analog.com wrote:
>>> This driver allows any Blackfin system timer to be used as IIO trigger.
>>> It supports trigger rates from 0 to 100kHz in Hz resolution.
>>
>> The reason we ended up with a rtc based trigger in the first place, was that
>> I had a very similar set of timers on the pxa271 that I mainly develop with.
>>
>> At the time some debate opened up on whether there was a use case here for
>> a more general way of providing access to system periodic timers for exactly
>> this sort of device. The view seemed to be that there was, but I certainly didn't
>> have time to do it at the time and no one else seems to have looked at it since.
>> My dirty solution was an rtc driver that just added a lot of rtcs. It was never
>> going to merge though...
>>
>> Right now I can only track down a previous email from myself saying this has
>> been discussed a number of times, but naturally with no references at all. Oops.
>>
>> Anyhow, such a general subsystem for cpu timers doesn't exist AFAIK so for now
>> lets just go with your approach. Perhaps if we find other possible users we can
>> talk again about how best to support these.
>
> does this offer functionality that is not available in the new PWM framework ?
> http://thread.gmane.org/gmane.linux.kernel.embedded/3400
It's certainly conceivable that we could treat these as some sort of 'virtual' pwm,
possibly with rather more limited controls than you usual get.
next prev parent reply other threads:[~2011-02-23 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 13:42 [PATCH] IIO: trigger: New Blackfin specific trigger driver iio-trig-bfin-timer michael.hennerich
2011-02-22 15:03 ` Jonathan Cameron
2011-02-22 20:58 ` Michael Hennerich
2011-02-22 22:35 ` [Device-drivers-devel] " Mike Frysinger
2011-02-23 11:08 ` Jonathan Cameron [this message]
2011-02-23 18:00 ` Mike Frysinger
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=4D64EABA.2030005@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--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