From: Bankim Bhavsar <bankim.bhavsar@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kw I²C
Date: Fri, 3 Sep 2010 16:13:55 -0700 [thread overview]
Message-ID: <AANLkTinQOpo9RtL3k75WTbSD2==Ri4NA646ov11B5737@mail.gmail.com> (raw)
In-Reply-To: <257739.47cbc5b4.ijDr.mx@tumtum.plumbweb.net>
By I²C, you mean Immediate Command/Response Interface of HDAudio controller?
Though Immediate Command/Response Interface should work, CORB/RIRB is
the recommended way to send/receive commands/responses from the codec.
If you do use Immediate mode, please refer to the updated HDAudio spec
that clarifies use of ICB bit in ICIS register.
http://www.intel.com/standards/hdaudio/pdf/hda002-a.pdf
Thanks,
Bankim.
On Fri, Sep 3, 2010 at 4:08 PM, Tristan Plumb <9p-st@imu.li> wrote:
> I'm working on a audio driver for kw (openrd) as a warmup for other more
> useful drivers (do something easy before something hard), and I've come
> to the point where to do anything more requires talking to the audio
> codec. According to various linux patches, this is done over I²C. Has
> anyone done anything with I²C, is it used for anything else? The kirkwood
> functional specification does not mention it (at least so far as I can
> see in the copy I have). Elseways I'll scrounge around some more.
>
> Thoughts?
>
> tristan
>
> --
> All original matter is hereby placed immediately under the public domain.
>
>
next prev parent reply other threads:[~2010-09-03 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 23:08 Tristan Plumb
2010-09-03 23:13 ` Bankim Bhavsar [this message]
2010-09-04 14:18 ` Tristan Plumb
2010-09-04 17:09 ` [9fans] " Bankim Bhavsar
2010-09-04 0:11 ` [9fans] kw IC erik quanstrom
2010-09-04 0:47 ` ron minnich
2010-09-04 0:49 ` erik quanstrom
2010-09-04 0:54 ` andrey mirtchovski
2010-09-04 1:02 ` andrey mirtchovski
2010-09-04 1:43 ` EBo
2010-09-04 7:21 ` Akshat Kumar
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='AANLkTinQOpo9RtL3k75WTbSD2==Ri4NA646ov11B5737@mail.gmail.com' \
--to=bankim.bhavsar@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).