[Nook Color Android Development] fattire:
try, try again...

Tried again... using the acclaim omap4 drivers above. Here's what I had on:

+CONFIG_SND_OMAP_SOC_ABE_DSP=y
+CONFIG_SND_OMAP_SOC_MCBSP=y
+CONFIG_SND_OMAP_SOC_ABE=y
+CONFIG_ABE_44100=y
+# CONFIG_SND_OMAP_SOC_ENCORE is not set
+CONFIG_SND_OMAP_SOC_RY_AIC3110=y
+CONFIG_SND_OMAP4_ABE_USE_ALT_FW=y
CONFIG_SND_SOC_I2C_AND_SPI=y
# CONFIG_SND_SOC_ALL_CODECS is not set
+CONFIG_SND_SOC_TLV320AIC3100=y
+CONFIG_SND_SOC_AIC3110=y

I turned off CONFIG_MINIDSP in tlv320aic3100.h. I also added this to the board-peripherals file (acclaim has something similar) and registered it.

+static struct platform_device encore_aic3110 = {
+ .name = "tlv320aic3110-codec",
+ .id = -1,
+};

it builds fine.

# find /sys | grep audio
/sys/devices/platform/omap-pcm-audio
/sys/devices/platform/omap-pcm-audio/uevent
/sys/devices/platform/omap-pcm-audio/modalias
/sys/devices/platform/omap-pcm-audio/subsystem
/sys/devices/platform/omap-pcm-audio/power
/sys/devices/platform/omap-pcm-audio/power/async
/sys/devices/platform/omap-pcm-audio/power/runtime_status
/sys/devices/platform/omap-pcm-audio/power/runtime_usage
/sys/devices/platform/omap-pcm-audio/power/runtime_active_kids
/sys/devices/platform/omap-pcm-audio/power/runtime_enabled
/sys/devices/platform/omap-pcm-audio/power/control
/sys/devices/platform/omap-pcm-audio/power/runtime_suspended_time
/sys/devices/platform/omap-pcm-audio/power/runtime_active_time
/sys/devices/platform/omap-pcm-audio/power/autosuspend_delay_ms
/sys/devices/platform/omap-pcm-audio/driver
/sys/devices/virtual/switch/usb_audio
/sys/devices/virtual/switch/usb_audio/uevent
/sys/devices/virtual/switch/usb_audio/subsystem
/sys/devices/virtual/switch/usb_audio/power
/sys/devices/virtual/switch/usb_audio/power/async
/sys/devices/virtual/switch/usb_audio/power/runtime_status
/sys/devices/virtual/switch/usb_audio/power/runtime_usage
/sys/devices/virtual/switch/usb_audio/power/runtime_active_kids
/sys/devices/virtual/switch/usb_audio/power/runtime_enabled
/sys/devices/virtual/switch/usb_audio/power/control
/sys/devices/virtual/switch/usb_audio/power/runtime_suspended_time
/sys/devices/virtual/switch/usb_audio/power/runtime_active_time
/sys/devices/virtual/switch/usb_audio/power/autosuspend_delay_ms
/sys/devices/virtual/switch/usb_audio/state
/sys/devices/virtual/switch/usb_audio/name
/sys/bus/platform/devices/omap-pcm-audio
/sys/bus/platform/drivers/soc-audio
/sys/bus/platform/drivers/soc-audio/uevent
/sys/bus/platform/drivers/soc-audio/unbind
/sys/bus/platform/drivers/soc-audio/bind
/sys/bus/platform/drivers/omap-pcm-audio
/sys/bus/platform/drivers/omap-pcm-audio/omap-pcm-audio
/sys/bus/platform/drivers/omap-pcm-audio/uevent
/sys/bus/platform/drivers/omap-pcm-audio/unbind
/sys/bus/platform/drivers/omap-pcm-audio/bind
/sys/bus/usb/drivers/snd-usb-audio
/sys/bus/usb/drivers/snd-usb-audio/module
/sys/bus/usb/drivers/snd-usb-audio/uevent
/sys/bus/usb/drivers/snd-usb-audio/unbind
/sys/bus/usb/drivers/snd-usb-audio/bind
/sys/bus/usb/drivers/snd-usb-audio/new_id
/sys/bus/usb/drivers/snd-usb-audio/remove_id
/sys/class/switch/usb_audio
/sys/module/snd_usb_audio
/sys/module/snd_usb_audio/parameters
/sys/module/snd_usb_audio/parameters/ignore_ctl_error
/sys/module/snd_usb_audio/parameters/device_setup
/sys/module/snd_usb_audio/parameters/async_unlink
/sys/module/snd_usb_audio/parameters/nrpacks
/sys/module/snd_usb_audio/parameters/pid
/sys/module/snd_usb_audio/parameters/vid
/sys/module/snd_usb_audio/parameters/enable
/sys/module/snd_usb_audio/parameters/id
/sys/module/snd_usb_audio/parameters/index
/sys/module/snd_usb_audio/drivers
/sys/module/snd_usb_audio/drivers/usb:snd-usb-audio

but

# ls /dev/snd
timer

# dmesg | grep audio
<6>usbcore: registered new interface driver snd-usb-audio
# dmesg | grep audio
<6>usbcore: registered new interface driver snd-usb-audi

if I tried CONFIG_SND_OMAP_SOC_ENCORE=y (formerly CONFIG_SND_OMAP_SOC_ACCLAIM=y), it would just hang. I believe this is the fault of omap4_aic3100.c which is the big difference between that and SND_OMAP_SOC_RY_AIC3110 which is what I did use. (there is something there about DAC, so I'm gonna try commenting it out but I bet it does not much. Update: Nope. I'm pretty sure this file is choking.

nook_lover did whoever told you to use this driver know you were using omap3?

I didn't update the headset GPIO fwiw.