Nicolas Pitre wrote:
>
>
>On Wed, 11 Apr 2001, John Dorsey wrote:
>
>> (My recollection is a bit hazy on this, and I haven't looked at the code
>> lately. Hopefully, someone will step in to debunk any myths that I'm
>> about to tell.)
>>
>> When that driver was written, there were promises of a Grand Unified
>> UCB1200 driver framework which would allow cooperative sharing of that
>> chip's single interrupt source. As such, absolutely no effort was made
>> to permit any sort of peaceful coexistance between the sa1100_switches
>> driver and, say, the touchscreen code.
>
>That should be a myth now.
I feel the need to add $.02 (US) :-).
Recently I added code to read the ucb1200 adc and get audio working again.
I found some old audio code in arch/arm/special and some new ucb1200 code
(at least I think it was new) in drivers/char/ucb1200_*.c
The touch screen code was pretty possessive about the adc ports so I
added some code to the touch screen state machine to include the
notion of 'we are currently in the middle of reading the touch screen'
or 'we're currently reading the adc'. This seemed to go ok and seems
to work. I wasn't convinced it was worth much layering.
I also converted the old ucb1200 audio driver in special to work with
the new ucb1200_general code. This works also and plays mp3's,
etc... now.
The new ucb1200_audio.c file has all of the dma code which should
(some day) be moved up into the platform specific ucb1200_sa1100 code
and some sort of interface for this added for this type of function.
This seemed like a good first step which doesn't (he said) break
anything and sets the stage for future more general work.
Hopefully this all makes sense and doesn't conflict with anyone else's
work...
-brad
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
