From: Tristan Plumb <9p-st@imu.li>
To: 9fans@9fans.net
Subject: Re: kw I²C
Date: Sat, 4 Sep 2010 10:18:51 -0400 [thread overview]
Message-ID: <257793.b4d7e47c.SQS6.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <7d86ad3ab98383f438bc9498f3c56619@brasstown.quanstro.net> <AANLkTinQOpo9RtL3k75WTbSD2==Ri4NA646ov11B5737@mail.gmail.com>
eric quanstrom:
> if i read the marvell specification correctly, it uses i²s, not i²c.
> wikipedia has a pointer to the phillips specification.
It uses i²s to for the data (sound) transport. the control for the codec
is seperate, the codec is a cs42l51, which has an i²s interface for data
and either an i²c or spi interface for control, with the spi write-only.
Bankim Bhavsar:
> Though Immediate Command/Response Interface should work, CORB/RIRB is
> the recommended way to send/receive commands/responses from the codec.
Reading the datasheet of the codec, I havn't found any mention of CORB or
RIRB, so I would hazard a guess that that's not what I want. But still,
what is CORB/RIRB?
In light of further digging, the functional specification does talk about
"TWSI Bus Operation". twsi ≅ i²c. I guess I'll work on that now. Which,
according to the openrd schematics, connects to the audio codec and
the SMBus connector.
...
tristan
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2010-09-04 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 23:08 kw I²C Tristan Plumb
2010-09-03 23:13 ` [9fans] " Bankim Bhavsar
2010-09-04 14:18 ` Tristan Plumb [this message]
2010-09-04 17:09 ` 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=257793.b4d7e47c.SQS6.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
--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).