This is not the way it works: the I2S bus only carries sound samples, the 
command to control an I2S codec use a separate bus (I2C or SPI) to access the 
codec registers, which in turn are not standardized in any way.

Thus, most codec chip require a specific driver: these are located into the 
"sound/soc/codecs" subdirectory within the kernel source tree.

-- Michel

Le 24/06/2013 20:39, [email protected] a écrit :
> I checked in the Ralink 3.3 SDK and don't see an I2S driver. Maybe no
> one has written one?
> 
> On Mon, Jun 24, 2013 at 7:43 AM, [email protected] <[email protected]> 
> wrote:
>> Is there a driver for Ralink I2S already in OpenWRT? I can't identify one.
>> If not, can someone with the Ralink SDK tell me if there is one in there?
>> I'd like to get Ralink I2S going if it can be done without a huge
>> amount of work.
>>
>> --
>> Jon Smirl
>> [email protected]
> 
> 
> 
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to