From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tristan Plumb <9p-st@imu.li> To: 9fans@9fans.net Subject: Re: kw I²C Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Message-Id: <257793.b4d7e47c.SQS6.mx@tumtum.plumbweb.net> In-Reply-To: <7d86ad3ab98383f438bc9498f3c56619@brasstown.quanstro.net> References: <257739.47cbc5b4.ijDr.mx@tumtum.plumbweb.net> <7d86ad3ab98383f438bc9498f3c56619@brasstown.quanstro.net> Date: Sat, 4 Sep 2010 10:18:51 -0400 User-Agent: mx-alpha Topicbox-Message-UUID: 4f404a9c-ead6-11e9-9d60-3106f5b1d025 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.