[1/3][PATCH][upstream]Adding documentation for TDM

[Aggrwal Poonam-B10812]

> -----Original Message-----
> From: David Laight [mailto:David.Laight at ACULAB.COM]
> Sent: Wednesday, July 25, 2012 2:14 PM
> To: Aggrwal Poonam-B10812; Singh Sandeep-B37400; linuxppc-
> dev at lists.ozlabs.org
> Cc: Singh Sandeep-B37400
> Subject: RE: [1/3][PATCH][upstream]Adding documentation for TDM
> 
> > > For flexibility you need to allow for 8bit samples being converted
> as:
> > > 1) 8bit raw ulaw or alaw data (unchanged from line).
> > > 2) 8bit raw data, bit reversed, any hdlc protocol
> > >    is bit reversed from audio [1].
> > > 3) 8bit audio, converted from alaw to ulaw
> > > 4) 8bit audio, converted from ulaw to alaw
> > > 5) 16bit linear converted to/from alaw or ulaw and on a per-timeslot
> > > basis.
> > I agree. That we only support very limited samples. But We can add
> this
> > in second step once the basic framework is in.
> > Also right now the testing infrastructure we have, we won't be able to
> > test all these scenarios.
> 
> You probably ought to make the application request a specific format -
> and error the unsupported ones.
> That would make it easier to add support for other formats later.
David there is still configuration interface which needs to be added to the Framework.
This is mentioned in the documentation and patch also.
But we really need the core stuff which is handling the data get in and things will be added subsequently. 
> 
> I also suspect that this 'framework' isn't that general!
All the feedback welcome!
> We (as a company) use the TDM interface blocks on the MSC8101 and MSC8013
> Starecore DSPs as well as some bespoke FPGA logic (which will do ulaw<-
> >alaw convertion).
> The 'framework' would almost certainly be inappropriate for both out
> hardware and software.
Thanks a lot for the feedback. Can you please help to understand what is the scenario and how you use TDM. This will be a big help.
More generic the better.

Regards
Poonam
> 
> 	David
> 
> 
>