public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Gatliff <bgat@billgatliff.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Toggling GPIO at 38Khz
Date: Wed, 08 Oct 2008 07:01:05 -0500	[thread overview]
Message-ID: <48ECA101.8010604@billgatliff.com> (raw)
In-Reply-To: <9e4733910810072043m6c69f3bdv104bd32928fe64ae@mail.gmail.com>

Jon Smirl wrote:

> 
> Are there other techniques for generating pulse trains in the 36-56Khz
> range on a simple GPIO pin?
> 

Yes.

Use the GPIO pin to enable the output of an external circuit.  Or, hope that the
GPIO pin in question is multiplexed with a timer/counter or PWM peripheral.

But somehow, I don't think either answer is what you were looking for.  :)

36 KHz bit-banging is a reach for any processor running Linux, methinks.  Maybe
you could launch an FIQ (assuming ARM) and then do the bit-bang as a burst in
there, so that you would have more control over the timing.  But that kind of
code isn't going to play well with the rest of the kernel...

If the hardware design isn't set, you might want to consider using that GPIO
line as a quasi-SPI link to a small, AVR-type microcontroller that does the
bit-banging on your behalf.  Long-term, that's going to be a more reliable and
flexible solution I think.


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com

  parent reply	other threads:[~2008-10-08 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  3:43 Toggling GPIO at 38Khz Jon Smirl
2008-10-08  6:40 ` Eric Miao
2008-10-09  8:38   ` Andy Green
2008-10-08 12:01 ` Bill Gatliff [this message]
2008-10-08 13:06   ` Jon Smirl
2008-10-08 17:00     ` Chris Friesen
2008-10-08 21:58     ` Krzysztof Halasa
2008-10-08 18:57 ` Remy Bohmer
2008-10-08 22:24   ` Dave Hylands
2008-10-09  2:26     ` Bill Gatliff
2008-10-09 17:53     ` linux-os (Dick Johnson)
     [not found] <bkydL-21G-5@gated-at.bofh.it>
2008-10-08 12:15 ` Bodo Eggert

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=48ECA101.8010604@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox