From: Tony Lindgren <tony@atomide.com>
To: Timo Kokkonen <timo.t.kokkonen@iki.fi>
Cc: balbi@ti.com, linux-omap@vger.kernel.org,
linux-media@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/7] ir-rx51: Handle signals properly
Date: Fri, 14 Dec 2012 11:41:16 -0800 [thread overview]
Message-ID: <20121214194115.GL4989@atomide.com> (raw)
In-Reply-To: <50CB7E88.9050207@iki.fi>
* Timo Kokkonen <timo.t.kokkonen@iki.fi> [121214 11:33]:
> On 12/14/12 19:26, Felipe Balbi wrote:
> >
> > if it's really for PWM, shouldn't we be using drivers/pwm/ ??
> >
>
> Now that Neil Brown posted the PWM driver for omap, I've been thinking
> about whether converting the ir-rx51 into the PWM API would work. Maybe
> controlling the PWM itself would be sufficient, but the ir-rx51 uses
> also another dmtimer for creating accurate (enough) timing source for
> the IR pulse edges.
OK.
> I haven't tried whether the default 32kHz clock source is enough for
> that. Now that I think about it, I don't see why it wouldn't be good
> enough. I think it would even be possible to just use the PWM api alone
Cool.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] ir-rx51: Handle signals properly
Date: Fri, 14 Dec 2012 11:41:16 -0800 [thread overview]
Message-ID: <20121214194115.GL4989@atomide.com> (raw)
In-Reply-To: <50CB7E88.9050207@iki.fi>
* Timo Kokkonen <timo.t.kokkonen@iki.fi> [121214 11:33]:
> On 12/14/12 19:26, Felipe Balbi wrote:
> >
> > if it's really for PWM, shouldn't we be using drivers/pwm/ ??
> >
>
> Now that Neil Brown posted the PWM driver for omap, I've been thinking
> about whether converting the ir-rx51 into the PWM API would work. Maybe
> controlling the PWM itself would be sufficient, but the ir-rx51 uses
> also another dmtimer for creating accurate (enough) timing source for
> the IR pulse edges.
OK.
> I haven't tried whether the default 32kHz clock source is enough for
> that. Now that I think about it, I don't see why it wouldn't be good
> enough. I think it would even be possible to just use the PWM api alone
Cool.
Regards,
Tony
next prev parent reply other threads:[~2012-12-14 19:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 15:13 [PATCH 0/7] ir-rx51: Various fixes Timo Kokkonen
2012-11-18 15:13 ` [PATCH 1/7] ir-rx51: Handle signals properly Timo Kokkonen
2012-11-20 19:57 ` Tony Lindgren
2012-11-20 19:57 ` Tony Lindgren
2012-12-14 17:28 ` Tony Lindgren
2012-12-14 17:28 ` Tony Lindgren
2012-12-14 17:26 ` Felipe Balbi
2012-12-14 17:26 ` Felipe Balbi
2012-12-14 17:26 ` Felipe Balbi
2012-12-14 17:46 ` Tony Lindgren
2012-12-14 17:46 ` Tony Lindgren
2012-12-14 17:49 ` Felipe Balbi
2012-12-14 17:49 ` Felipe Balbi
2012-12-14 17:49 ` Felipe Balbi
2012-12-14 18:06 ` Tony Lindgren
2012-12-14 18:06 ` Tony Lindgren
2012-12-14 18:08 ` Felipe Balbi
2012-12-14 18:08 ` Felipe Balbi
2012-12-14 18:08 ` Felipe Balbi
2012-12-14 19:31 ` Timo Kokkonen
2012-12-14 19:31 ` Timo Kokkonen
2012-12-14 19:41 ` Tony Lindgren [this message]
2012-12-14 19:41 ` Tony Lindgren
2012-11-18 15:13 ` [PATCH 2/7] ir-rx51: Clean up timer initialization code Timo Kokkonen
2012-11-18 15:13 ` [PATCH 3/7] ir-rx51: Move platform data checking into probe function Timo Kokkonen
2012-11-18 15:13 ` [PATCH 4/7] ir-rx51: Replace module_{init,exit} macros with module_platform_driver Timo Kokkonen
2012-11-18 15:13 ` [PATCH 5/7] ir-rx51: Convert latency constraints to PM QoS API Timo Kokkonen
2012-11-18 15:13 ` [PATCH 6/7] ir-rx51: Remove useless variable from struct lirc_rx51 Timo Kokkonen
2012-11-18 15:13 ` [PATCH 7/7] ir-rx51: Fix sparse warnings Timo Kokkonen
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=20121214194115.GL4989@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=timo.t.kokkonen@iki.fi \
/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.