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
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
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
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
