(no subject)

(no subject)

[Eric N. Johnson (ACD)]

Has anyone been able to use an I2S audio DAC connected to a Programmable 
Serial Controllers (PSC) on the Freescale MPC5200 CPU working under Linux?

The kernel included in the DENX ELDK v3.1.1 has two drivers:
   i2s_ring.c and i2s.c.
The ring driver appears to be RX only, and the i2s.c driver causes the FEC 
ethernet to hang at startup.  I've read some previous mailing list messages 
that suggest there are issues with bestcomm and i2s support.

We've tried adapting the i2s_ring.c driver for our needs.  By default, it 
only has a receive task.  It partially initializes the port, and we see 
appropriate waveforms on the MCLK, CLK, and FRAME lines, but have not been 
able to transmit data.

The stock i2s.c driver hung the boot sequence, but if we comment out the 
bestcomm startup code, it at least completes the boot cycle.  Again we see 
appropriate waveforms on the MCLK, CLK, and FRAME lines.  If we feed data 
to the device (after performing the port setup IOCTLs), we see a 750 us 
burst of data every 45 ms or so.

Is it feasible to send 44.1 or 48 KHz 16-bit audio this way or is the PSC 
only usable for lower data rate applications?

Thank you,
Eric
------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774

Re: (no subject)

[Wolfgang Denk]

In message <6.2.1.2.1.20050412143653.02ae7720@mail.int.acdstar.com> you wrote:
> 
> The kernel included in the DENX ELDK v3.1.1 has two drivers:
>    i2s_ring.c and i2s.c.

i2s.c is not really a driver, but a (very OLD) test  version  of  one
used  to  demonstrate  certain  BestComm  related problems. Don't try
using it as a real driver ;-)


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
People are always a lot more complicated than you  think.  It's  very
important to remember that.             - Terry Pratchett, _Truckers_

Re: MPC5200 I2S driver

[Eric N. Johnson (ACD)]

At 04:13 PM 4/12/2005, Wolfgang Denk wrote:
>i2s.c is not really a driver, but a (very OLD) test  version  of  one
>used  to  demonstrate  certain  BestComm  related problems. Don't try
>using it as a real driver ;-)

Humm, any pointers on writing our own driver then then?  Digging through 
the source for other drivers, bestcomm seems to be a real house of 
cards.  We just want simple audio output capability.  No need to make it 
work with the standard Linux/OSS sound API.

Where can we keep track of the eratta/bugs in bestcomm?  Browsing through 
the mailing list, I've found references that:
   IDE and Ethernet DMA can't work at the same time
   I2S TX and RX DMA can't work at the same time
   AC-97 is terminally broken (no way to handle the slot tags properly
          for variable sampling rates)
Are these all still true?

We've tried asking our local Freescale rep, but they seem to think that 
Linux==Metrowerks, and they are looking into the bestcomm question, but 
official responses from Freescale tend to take >1 week.

This is for a custom MPC5200 board, heavily based on IceCube with a single 
I2S DAC on PSC2 running in "CODEC with MCLK" mode.

Sorry about the null subject line previously: fingers were working faster 
than brain...

Thanks
Eric


------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774

Re: MPC5200 I2S driver

[Wolfgang Denk]

In message <6.2.1.2.1.20050412173010.02adaaa0@mail.int.acdstar.com> you wrote:
>
> Humm, any pointers on writing our own driver then then?  Digging through 
> the source for other drivers, bestcomm seems to be a real house of 
> cards.  We just want simple audio output capability.  No need to make it 
> work with the standard Linux/OSS sound API.

User the i2s_ring.c driver as model.

> Where can we keep track of the eratta/bugs in bestcomm?  Browsing through 
> the mailing list, I've found references that:
>    IDE and Ethernet DMA can't work at the same time
>    I2S TX and RX DMA can't work at the same time
>    AC-97 is terminally broken (no way to handle the slot tags properly
>           for variable sampling rates)
> Are these all still true?

This probably depends on your definition  of  "can't  work".  If  you
allow  for  a  failure every now and then under certain (more or less
exotic) usage conditions ... ;-)


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I have been over into the future, and it works.
                - Lincoln Steffens in _Letters_ (1938) vol. 1, p. 463

Re: MPC5200 I2S driver

[Hans Thielemans]

Hi Eric,

I have been working on a driver for a similar case:
mpc5200 talking to adi blackfin sport channel.

It is rather stable at the moment. Only now and then (~1/hour)
transmission stops due to bestcomm missing a taskstart.
When I check with the bdi2000 it is always the task active bit which
is cleared in the bestcomm registers.
When I kick the dma descriptor by setting the task active bit again with the
bdi2000 it continues normally. I suspect a problem with the bestcomm
api. The dma task active bit is cleared when dma is done. When this 
interferes with the
ppc setting the bit. the task is not started (so far my analysis).
I did not find yet a 100% secure way of getting the bit set.

My main problem was also that I wanted the blackfin to be master of the
link. But the mpc5200 has an anomaly on the frame sync. I managed to
get it work by using the mpc5200 psc spi slave mode and proper
settings at the blackfin side. I got reliable transmission for several hours 
at 16 Mbit/s

The driver supports simultaneous use of several psc channels. I tried psc2 
and psc3 together.
You can use the driver as master or slave by changing the control register 
with ioctl.
I'll forward the present version and a test program when i'm back at work 
tomorrow.

Regards,

Hans Thielemans
HAZO bvba

----- Original Message ----- 
From: "Eric N. Johnson (ACD)" <ejohnson@acdstar.com>
To: <linuxppc-embedded@ozlabs.org>
Sent: Wednesday, April 13, 2005 12:46 AM
Subject: Re: MPC5200 I2S driver


> At 04:13 PM 4/12/2005, Wolfgang Denk wrote:
>>i2s.c is not really a driver, but a (very OLD) test  version  of  one
>>used  to  demonstrate  certain  BestComm  related problems. Don't try
>>using it as a real driver ;-)
>
> Humm, any pointers on writing our own driver then then?  Digging through 
> the source for other drivers, bestcomm seems to be a real house of cards. 
> We just want simple audio output capability.  No need to make it work with 
> the standard Linux/OSS sound API.
>
> Where can we keep track of the eratta/bugs in bestcomm?  Browsing through 
> the mailing list, I've found references that:
>   IDE and Ethernet DMA can't work at the same time
>   I2S TX and RX DMA can't work at the same time
>   AC-97 is terminally broken (no way to handle the slot tags properly
>          for variable sampling rates)
> Are these all still true?
>
> We've tried asking our local Freescale rep, but they seem to think that 
> Linux==Metrowerks, and they are looking into the bestcomm question, but 
> official responses from Freescale tend to take >1 week.
>
> This is for a custom MPC5200 board, heavily based on IceCube with a single 
> I2S DAC on PSC2 running in "CODEC with MCLK" mode.
>
> Sorry about the null subject line previously: fingers were working faster 
> than brain...
>
> Thanks
> Eric
>
>
> ------------------------------------
> Eric Johnson, Electrical Engineer
> Advanced Communication Design
>   7901 12th Avenue South
>   Bloomington, MN 55425
> Ph: 952-854-4000  Fax: 952-854-5774
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

MPC5200 I2S driver

[Frank Bennett]

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

Hi Hans, Eric:

I would be interested in getting any driver code
examples for Bestcomm/PSC6/CODEC for the mpc5200
as well.

I am developing a couple of drivers: one a Data
Acquisition driver for SPI based AD7683 SAR ADC
on PSC6/codec and a LCD user interface on PSC3/SPI
using the DENX Linux distribution. Is arch/ppc/5xxx_io/i2s.c
a good example of a Bestcomm, Codec, non Ethernet
example?

Thanks to you guys and Wolfgang for you contributions
to this thread discussion.

*/Frank Bennett
President
/*Mathegraphics,LLC
613 Bentley Pl
Fort Collins,CO 80526
www.mathegraphics.com <http://www.mathegraphics.com>
bennett78@digis.net <mailto:bennett78@digis.net>




[-- Attachment #2: Type: text/html, Size: 1145 bytes --]

Re: MPC5200 I2S driver

[Wolfgang Denk]

In message <436D068A.7030905@digis.net> you wrote:
> 
> I am developing a couple of drivers: one a Data
> Acquisition driver for SPI based AD7683 SAR ADC
> on PSC6/codec and a LCD user interface on PSC3/SPI
> using the DENX Linux distribution. Is arch/ppc/5xxx_io/i2s.c
> a good example of a Bestcomm, Codec, non Ethernet
> example?

The  arch/ppc/5xxx_io/i2s.c  driver  is  *not*  a  good  example  for
anything  usefuil - it is test code used to demonstrate some problems
with (earlier versions of) the BestComm API code.  It  is  not  in  a
working state.

An example for a working driver is in  "i2s_ring.c",  but  note  that
this  driver  uses a pretty specialized interface to the application,
so you will probably have to adjust this for your needs.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Be careful what you wish for. You never know who will be listening.
                                      - Terry Pratchett, _Soul Music_

Re: MPC5200 I2S driver

[Eric N. Johnson (ACD)]

>I would be interested in getting any driver code
>examples for Bestcomm/PSC6/CODEC for the mpc5200
>as well.

There was an earlier discussion on this list.  Have a look at:
http://ozlabs.org/pipermail/linuxppc-embedded/2005-September/020210.html

That message has the code we've used to run an I2S DAC on the 
MPC5200.  It's been stable, although we've not done extensive 
testing.  You'll also have to prune out the code that's specific to 
our hardware, and it supports output only.  We have not tried using I2S inputs.

Eric

------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774