Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Paul Barker <paul@paulbarker.me.uk>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: McBSP functions not exported
Date: Fri, 11 Jan 2013 11:48:46 +0000	[thread overview]
Message-ID: <20130111114846.00005679@unknown> (raw)

Hi,

I'm currently working on a driver to talk to an analog-to-digital
converter (specifically a Texas Instruments ADS1672) connected to the
McBSP port on a Beagleboard-xM. I'm currently building my driver module
against a 3.2 series kernel with Beagleboard patches and config from
https://github.com/beagleboard/kernel (branch beagleboard-3.2). I'd
like to keep up-to-date with the more recent kernels but my module
won't compile with them.

When the OMAP McBSP driver stack was merged into a single driver
(commit 45656b4 by Peter Ujfalusi, looks like it went into linux 3.3)
all the EXPORT_SYMBOL macros were removed so I can no longer call the
functions I was using from my external module. Alternatively I could
just be missing something really obvious, let me know if I am!

I'm just wondering what the best way forward is from here and I'm sure
I can't be the only person who was using the McBSP driver code in the
kernel to interface with external hardware. The two options I can think
of are either that I move my driver into the kernel source tree itself
or the McBSP driver functions are exported again so that they can be
used by external modules. It's easier to maintain an external module
than a series of patches against the kernel, unless a driver for an
analog-to-digital converter connected to the McBSP port is something
that would actually have a chance of being merged into the mainline
kernel. I could look at making this driver more generic once I have the
current hardware/driver combination working, so that it should work
with most analog-to-digital converters - I haven't found such a driver
in my previous googling.

If you have any advice on this or a pointer to a better place to ask
this question please let me know.

Thanks,

-- 
Paul Barker

paul@paulbarker.me.uk
http://www.paulbarker.me.uk/

             reply	other threads:[~2013-01-11 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 11:48 Paul Barker [this message]
2013-01-11 13:17 ` McBSP functions not exported 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
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=20130111114846.00005679@unknown \
    --to=paul@paulbarker.me.uk \
    --cc=linux-omap@vger.kernel.org \
    --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