Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>, linux-omap@vger.kernel.org
Subject: Re: McBSP functions not exported
Date: Wed, 16 Jan 2013 09:44:02 +0200	[thread overview]
Message-ID: <20130116094402.251b13fbe83ca5c172bfac7d@bitmer.com> (raw)
In-Reply-To: <f358e8045003700c83717ce3f7bc1932@localhost>

Hi

On Tue, 15 Jan 2013 17:43:54 +0000
Paul Barker <paul@paulbarker.me.uk> wrote:

> I'm going to go back to using kernel 3.2 and check that this actually 
> works
> with the McBSP. If it does, how much hassle is it to export the 
> required symbols
> in more recent kernels? I'll happily write the patch, I just don't want 
> to
> introduce too much more maintenance overhead going forward.
> 
Quick idea that came to my mind. Hack and I don't know how feasible it is but would it be possible to make that ADC as a simple ASoC codec driver in your usecase? I.e. using ALSA API for high-rate ADC measurements and reuse existing serial link and dma drivers.

Anyway I think high-rate ADC falls in gray area in kernel currently. drivers/iio/ seems to not cover them and does not match exactly with ASoC either.

-- 
Jarkko

  reply	other threads:[~2013-01-16  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 11:48 McBSP functions not exported Paul Barker
2013-01-11 13:17 ` Peter Ujfalusi
2013-01-11 16:27   ` Paul Barker
2013-01-14  8:48     ` Peter Ujfalusi
2013-01-15 17:43       ` Paul Barker
2013-01-16  7:44         ` Jarkko Nikula [this message]
2013-01-16  9:05         ` Peter Ujfalusi

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=20130116094402.251b13fbe83ca5c172bfac7d@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@paulbarker.me.uk \
    --cc=peter.ujfalusi@ti.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