From: Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
To: Jon Smirl <jonsmirl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Finding 'orphaned' i2c drivers
Date: Mon, 23 Feb 2009 15:43:00 +0100 [thread overview]
Message-ID: <20090223144300.GA18378@buzzloop.caiaq.de> (raw)
In-Reply-To: <9e4733910902230638w262cd027pba4b65509e2e8a41-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On Mon, Feb 23, 2009 at 09:38:45AM -0500, Jon Smirl wrote:
> On Mon, Feb 23, 2009 at 6:00 AM, Daniel Mack <daniel-rDUAYElUppE@public.gmane.org> wrote:
> > what's the suggested way of implementing an i2c drver which does not
> > have any other interfaces to the outside world than just the i2c device
> > it is communicating with? More specifically, I implemented a driver for a
> > Maxim clock generator and would like to use a proprietary interface with
> > it from a alsa-soc module. I just can't find a sane way to access the
> > driver's instance from there. It does exist somewhere in the linux
> > device tree, but is there a simple function that iterates over it and
> > returns it to me by name? Reading include/linux/device.h didn't point me
> > to anything that could fit.
>
> The max9485? Which codec are you using it with? I tried submitting the
> attached driver for the chip but Jean said it was too simple of a
> driver.
Yes, it's the same one.
> I use it like this:
>
> static int dspeak01_fabric_hw_params(struct snd_pcm_substream
> *substream, struct snd_pcm_hw_params *params)
> {
> uint rate, select;
> int ret;
> struct snd_soc_pcm_runtime *rtd = substream->private_data;
> struct snd_soc_dai *cpu_dai = rtd->dai->cpu_dai;
>
> printk("dspeak01_fabric_hw_params\n");
>
> switch (params_rate(params)) {
> case 11025:
> case 22050:
> case 44100:
> case 88200:
> case 176400:
> rate = 22579200;
> select = MAX9485_225792;
> break;
> default:
> rate = 24576000;
> select = MAX9485_245760;
> break;
> }
> max9485_set(fabric.clock, select | MAX9485_CLK_OUT_2);
I still don't see where you got the pointer from you are using here, and
that's my whole question.
Your driver looks very much like the one I wrote, though ;)
Daniel
next prev parent reply other threads:[~2009-02-23 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 11:00 Finding 'orphaned' i2c drivers Daniel Mack
[not found] ` <20090223110052.GE15722-ahpEBR4enfnCULTFXS99ULNAH6kLmebB@public.gmane.org>
2009-02-23 14:38 ` Jon Smirl
[not found] ` <9e4733910902230638w262cd027pba4b65509e2e8a41-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-23 14:43 ` Daniel Mack [this message]
[not found] ` <20090223144300.GA18378-ahpEBR4enfnCULTFXS99ULNAH6kLmebB@public.gmane.org>
2009-02-23 15:16 ` Jon Smirl
[not found] ` <9e4733910902230716t39994927i454bceb641c650ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-23 15:18 ` Jon Smirl
[not found] ` <9e4733910902230718p1f896e77u9292708b71ab36a6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-23 15:24 ` Jon Smirl
2009-02-23 14:43 ` Mark Brown
[not found] ` <20090223144343.GC2078-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2009-02-23 14:51 ` Daniel Mack
[not found] ` <20090223145142.GB18378-ahpEBR4enfnCULTFXS99ULNAH6kLmebB@public.gmane.org>
2009-02-23 15:04 ` Mark Brown
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=20090223144300.GA18378@buzzloop.caiaq.de \
--to=daniel-rduayeluppe@public.gmane.org \
--cc=jonsmirl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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