Re: DM6446: EDMA

David Brownell wrote: On Monday 26 January 2009, Brian G Rhodes wrote: I think someone forgot an 'I' in edma_stop. Writing to ECR seems pointless to me. I am assuming they meant to do SH_IECR instead of SH_ECR. This also happens to fix the problem I was having with audio stalls on dm6446

Re: DM6446: EDMA

David Brownell wrote: On Monday 26 January 2009, Brian G Rhodes wrote: I think someone forgot an 'I' in edma_stop. Writing to ECR seems pointless to me. I am assuming they meant to do SH_IECR instead of SH_ECR. This also happens to fix the problem I was having with audio stalls on dm6446

Re: [PATCH 1/2] DM6446 DMSoC SPI driver

Mark A. Greer wrote: Brian, FYI, there is already an SPI driver that TI is preparing to push out to the community. I'm not sure who in TI is the acutal engineer doing that but hopefully, they'll speak up so you can sync up with them. That would be wonderful. I've been meaning to get this

Re: serial console port

Liu Hua wrote: I use linux-2.6.28 kernel for dm6446 board from montavista. It can work well except that there's some problem in serial console.When I login linux, I enter a charactor, the charactor will not display until I enter the next charactor. So there's one charactor delay. But whe

Re: Audio Driver Problem

amr ali wrote: AA, My final commercial product is supposed to play audio from USB. Do you think it is a driver problem?? -- Amr Ali. Try writing 0x4 to ESR when it is in the stalled state. devmem2 0x01c01010 0x4 0x4 is the ASP transmit channel. There is likely a pending event and writing

Re: SPI driver about Davinci DM6446

msg->complete(msg->context); } /* Place SPI peripheral into reset */ iowrite32(0, dvspi->regs_base+SPIGCR0); /* Disable the clock thus removing power from the peripheral */ clk_disable(dvspi->clk); clk_put(dvspi->clk); free_irq(dvspi->irq, master); spi_unregister_master(master); return 0; } #ifdef CONFIG_PM static int spi_davinci_suspend(struct platform_device *pdev, pm_message_t mesg) { struct spi_master *master = platform_get_drvdata(pdev); struct davinci_spi *dvspi = spi_master_get_devdata(master); clk_disable(dvspi->clk); return 0; } static int spi_davinci_resume(struct platform_device *pdev) { struct spi_master *master = platform_get_drvdata(pdev); struct davinci_spi *dvspi = spi_master_get_devdata(master); clk_enable(dvspi->clk); return 0; } #else #define spi_davinci_suspend NULL #define spi_davinci_resume NULL #endif static struct platform_driver spi_davinci_driver = { .driver = { .name = "spi_davinci", .owner = THIS_MODULE, }, .suspend = spi_davinci_suspend, .resume = spi_davinci_resume, .remove = __exit_p(spi_davinci_remove), }; static int __init spi_davinci_init(void) { return platform_driver_probe(&spi_davinci_driver, spi_davinci_probe); } static void __exit spi_davinci_exit(void) { platform_driver_unregister(&spi_davinci_driver); } module_init(spi_davinci_init); module_exit(spi_davinci_exit); MODULE_DESCRIPTION("DaVinci SPI Controller driver"); MODULE_AUTHOR("Brian Rhodes "); MODULE_LICENSE("GPL"); ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: SPI driver about Davinci DM6446

Steve Chen wrote: As far as I know, TI does not officially support SPI for dm6446. SPI is officially supported for dm355 and dm6467. Certainly might be the case since there are no SPI devices on the 6446 EVM, however I was referring to... Brian, The intent is to get the SPI driver for

Re: SPI driver about Davinci DM6446

David Brownell wrote: On Tuesday 05 May 2009, Narnakaje, Snehaprabha wrote: Initial patch set was sent back in March - http://linux.omap.com/pipermail/davinci-linux-open-source/2009-March/012210.html This was tested on DM355, but the same driver should work on DM6446, but requires some de

2.6.30 EDMA/Audio Lockup

I modified 2.6.30-rc7 which was pulled from davinci git last week to support our dm6446 board. In order to get i2s configured properly I had to make some changes. There was no longer a definition for the CLKSM bit. hwparams does not read the SRGR register, but instead simply sets FSGM which

Codec Engine 2_23_01 Failure to load Server

After updating to more current TI software I am not able to load one of the codec servers which we use. @0,069,812us: [+0 T:0x40020bf0 S:0xbea5c7e4] ti.sdo.ce.alg - ALG_init> Enter @0,070,063us: [+0 T:0x40020bf0 S:0xbea5c7d4] OG - Global_atexit> enter (fxn=0x4360f184) @0,070,269us: [+0 T:0x400

Re: Codec Engine 2_23_01 Failure to load Server

Brian Rhodes wrote: MV Pro 5.0 toolchain Codec Engine 2.23.01 DSP/BIOS 5.33.05 XDCTOOLS 3.15.00.50 Framework Components 2.23.01 XDAIS 6.23 DSPLINK 1.61.03 CMEM (linuxutils) 2.23.01 The error message @0,123,595us: [+7 T:0x44643490 S:0x44642d74] OP - Processor_create_d> Loading and starting

biosutils

Error: incompatible use of package 'ti.rtdx': imported ti.rtdx [2,0,0,1,1194024051755], ti.bios.utils was built with ti.rtdx [] Does biosutils need to be rebuilt? I am using the version from dvsdk 1.3.0. ___ Davinci-linux-open-source mailing list Da

building dsplink

prcs.c: In function `PRCS_Create': prcs.c:185: error: dereferencing pointer to incomplete type prcs.c:186: error: dereferencing pointer to incomplete type prcs.c:188: error: dereferencing pointer to incomplete type 185(*prcsObj)->handleToThread= (Pvoid) current->pid ; 186

Re: building dsplink

that adds support for Linux kernel versions 2.6.18 onwards into DSPLink http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg03002.html Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Rhodes Sen

Re: building dsplink

On Behalf Of Brian Rhodes Sent: Thursday, June 19, 2008 12:02 AM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: building dsplink Thanks for responding. I am trying to compile dsplink 1.50 and I am using codec engine 2.10. The error is with the type for &#x

Re: DM6446 1024x768 graphics with video overlay

Carl Renaud wrote: Hi, I am seeking advice on the DM6446... Our product requirements == Display a 1024x768 graphic background with a video overlay. Using the DM6446, there is no problem doing this is in D1 resolution, using VID0 for video, OSD0 for graphics and OSD1 for

Re: DM6446 1024x768 graphics with video overlay

This would prevent you from being able to play video or animations to OSD0 at higher resolutions. Thanks again! On Tue, Oct 14, 2008 at 4:57 PM, Brian Rhodes <[EMAIL PROTECTED]> wrote: Carl Renaud wrote: Hi, I am seeking advice on the DM6446... Our product requirements

Re: DM6446 1024x768 graphics with video overlay

Carl Renaud wrote: Hi Brian, Thanks, for the valuable feedback on your experience. I am working on a proof of concept with the EVMDM6446, but unfortunately I don't have a daughter card enabling output at 1024x768, so I need to do some guesstimations... 1) You say using the attribute window t

Re: DM6446 1024x768 graphics with video overlay

ain -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carl Renaud Sent: Wednesday, October 15, 2008 9:16 AM To: Brian Rhodes Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: DM6446 1024x768 graphics with video overlay Thanks for your respon

Codec Server/Algorithms

Is it permissible to call the create and delete functions for an algorithm from different threads/contexts? I am running into an issue which is fairly easy to replicate. If I call create/destroy in a loop, I can allocate and destroy the algorithm instance indefinitely, however, if I create a

Re: Codec Server/Algorithms

u are serializing access, you could quickly check that the application is fine by replacing the codec with the video copy algorithm from CE examples. On Mon, Nov 24, 2008 at 11:00 PM, Brian Rhodes <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Is it permissible to call the

DM6446 MUSB

Hello, Is PIO ONLY the only working USB mode in the current GIT kernel? By working, I mean without periodic reset. PIO is suitable for my application, but I just merged the latest GIT code into our kernel tree and without CONFIG_MUSB_PIO_ONLY=y USB does not work very well, so I was curious

Re: Codec Engine 2_23_01 Failure to load Server

Brian G Rhodes wrote: Chris, I found that my map is proper, and the issue is elsewhere. It looks like the LINKCFG_Dsp structure. The av5T ipc_dsplink library which is being linked with the application seems to have some duplicate symbols. I modified the LINKCFG_Dsp in dsplink to change the

Re: Flashing kernel from linux - need help

Vinod Nanjaiah wrote: Any idea if this is still an unresolved bug in the montavista kernel? How can I change the OOB code in the linux kernel to match with that of the uboot? Can someone please give me some pointers on where/what code needs to be changed. You need to add setup cod

RGB565 output on RGB666 Pixel Bus on 18BIT LVDS driver output

Hello, I have a custom dm6446 board which has connections for a couple different LCD displays which are connected via LVDS. In each case the surface format is RGB565 on OSD0 and the output is configured for RGB666. One of the displays is 24bit, and the other is 18bit. After the LVDS driver

Re: Problem with USB host mode + audio on DM6446

J.C. Wren wrote: I just got my audio working this evening with a TLV320DAC32 DAC on a near-copy of the DM6446 EVM board (we use the TLV320DAC32 instead of the TLV320AIC33 and drop the I2C port expanders). I've had USB host mode working for a while, but now when I try to use audio after mounti

Re: Debugging spurious reboots

Ben White wrote: Hi Folks, We have a video encoder product that is based on DM6446. GIT kernel 2.6.23-davinci1 and DVSDK 1.30.01.41. We have some automated test tools that repeatedly change the codecs from H.264->MJPEG->MPEG4-> etc (these simulate user actions). This results in the whole o