Please, let me open this thread in the hope that you'll be able to clarify iegpv2 kernel modifications.
In particular I want to understand the kernel TWL4030 architecture (only the audio part).
Bassically I've read ASoC and some other audio others driver implementations.
In refenrece to ..../kernel/sound/soc/omap/igep0020.c file, at the very begining there are the DAI<->CPU interface definition. Here it mentions "omap-mcbsp-dai.1". The question is: what it makes reference, mcbsp1? Seeing igepv2 schema it seems that TWL it is using mcbsp2 as main interface for audio/alsa.
Accepted AnswersergioOffline0Hi forum members!
I think I've found the answer myself (I guess). Looking at path "/sys/devices/platform/" it shows:
iPRO:~$ ls /sys/devices/platform/
arm-pmu.0/ omap-mcbsp-dai.0/ omap-pcm-audio/ omapfb/
ehci-omap.0/ omap-mcbsp-dai.1/ omap-sham/ power/
leds-gpio/ omap-mcbsp-dai.2/ omap2-nand.0/ reg-dummy/
mmci-omap-hs.0/ omap-mcbsp-dai.3/ omap2_mcspi.1/ reg-fixed-voltage.0/
mmci-omap-hs.1/ omap-mcbsp-dai.4/ omap2_mcspi.2/ regulatory.0/
musb-omap2430.0/ omap-mcbsp.1/ omap2_mcspi.3/ smsc911x.0/
omap/ omap-mcbsp.2/ omap2_mcspi.4/ soc-audio/
omap-aes/ omap-mcbsp.3/ omap_hdq.0/ twl4030_script/
omap-iommu.0/ omap-mcbsp.4/ omap_vout/ uevent
omap-mailbox/ omap-mcbsp.5/ omapdss/
It seems reasonable that using omap-mcbsp-dai.X, X can get values from 0 to N-1, and using omap-mcbsp.Y, Y can get values from 1..N