[Eee Pad Transformer Android Development] timduru:
Sounds good, it's always nice to have more features :)

For the DAC filter if we want to keep quality I think we should leave it at it's default mode , because switching it to the sloping stopband mode is mostly made for low frequencies ?

Edit: I played a bit too much with alsa and had the DAC and ADC settings mixed up ;)

After a reboot with the values back to default, the ADC is in high performance mode by default, while the DAC is in low power mode by default.

Weird choice definitely. Or it might make sense for phones maybe, for a tablet with a big battery, i think the sound chip is not really what is consuming much battery compared to the screen and such :)

So yeah It's always good to have access to those registers too, definitely :)

Yeah before I found the alsa interface, I was going to add all the registers into the sysfs for a start in a generic way.

I think the complexity should be added into the app itself and not into the driver though.

Before the TF101 I had been playing quite a bit with chinese tablet roms, and it had a WM8987 that I played with to maximize the volume a bit,

They were giving a full procfs interface to control all the registers directly.

So I was wondering why the 8903 didn't have that, but I guess they preferred to rely on alsa, it makes sense now.

Seeing that Wolfson's chip are made for asoc :)

Yeah I don't really use the TF101 much for recording, but that could come in handy too,

I saw a few people complaining that the mic level was too high in some of the threads,

so allowing to decrease the ADC gain and such could be useful for them.

Adding a few filters for the MIC path would actually make sense too.

Depending on what you are trying to record, if it's voice for example we don't need all the freqs.

Activating the DRC is something we might benefit from in such cases too :)

I think it all boils down to :

- the input levels

- how much the ADC levels are pushed at that time

So having some kind of predefined settings for these different cases combination could be nice,

as to switch all the registers from one case to the other with one click quickly :)

Turning the DRC on + the anti-clipping filter with a varying knee and slope depending if the location is noisy or not could come in handy :)

Because it should automatically compensate the loud scenes by decreasing the volume, and do that only when it's loud while we still keep the higher volume and quality for quiet scenes.

No they are not :)

As far as I know they are actually ICS or HC kernels with modifications backported and configuration tweaked to make them work with JB.

Now maybe when / if asus releases a JB rom they might actually use the regular 3.X JB kernel .

But for the moment the current roms are not, which is kinda handy as it makes things more compatible just like before. :)

Yeah I was not expecting the module to insert in so many kernels either.

I originally made it for the TeamEOS Roach's JB kernel, and it seems to work for most if not all 2.6.39.x kernels.

It kinda make sense, as you say it won't insert only if what it interfaces to has changed into the kernel.

The voodoo module mostly interfaces with the WM8903 codec's registers, which are quite common all over the kernels,

So it makes it a very low risk to be rejected by a kernel .

As long as the kernel has the WM8903 codec it should be mostly fine.

I had played with quite a few modules for the chinese tablet, and if a module is using things like usb or such, that was much more difficult to get it to insert into the kernel

(I didn't even have the rom source or the .config from the kernel)

So yeah for the moment you should be fine with inserting your kaudio in the JB & ICS kernels I'd say :)