RE: Need help for missing sound after some time in /dev/dsp

2009-06-15 Thread Santosh Singh
Hi Mohamed, Thanks for response. But I am able to play for a longer period without any problem. My problem is with start stop many time the player /dev/dsp sound goes off which comes back after hard (hardware) reboot only not with software reboot command. I tried out the entire sampling rate but

GPIO Interrupt type

2009-06-15 Thread Liu, Yan
Hello, I am using linux kernel 2.6.30. I am trying to set interrupt type like Falling edge or Rising edge to my GPIO. I am using the following calls: set_irq_type(irq_num, IRQ_TYPE_EDGE_RISING)// here irq_num is 50 for gpio 6 in DM355 But, the value in GPIO register SET_RIS_TRIG is n

Re: [PATCH 7/10 - v2] DM355 platform changes for vpfe capture driver

2009-06-15 Thread Hans Verkuil
On Tuesday 16 June 2009 00:24:34 Karicheri, Muralidharan wrote: > Hans, > > Please see my response below. > >A general remark: currently you link your inputs directly to a subdev. > > This approach has two disadvantages: > > > >1) It doesn't work if there are no subdevs at all (e.g. because > >

Re: [PATCH 1/10 - v2] vpfe capture bridge driver for DM355 and DM6446

2009-06-15 Thread Hans Verkuil
On Monday 15 June 2009 23:47:07 Karicheri, Muralidharan wrote: > Hans, > > I am not clear about some of your comments. Please see below with a [MK] > prefix. > > >> + /* set if client specific interface param is available */ > >> + if (subdev->pdata) { > >> + /* each client will have

RE: [PATCH 7/10 - v2] DM355 platform changes for vpfe capture driver

2009-06-15 Thread Karicheri, Muralidharan
Hans, Please see my response below. >> +/* { plus irq }, */ >> /* { I2C_BOARD_INFO("tlv320aic3x", 0x1b), }, */ > >Huh? What's this? I only know the tlv320aic23b and that's an audio driver. > [MK] Thanks to David for answering this. >> -/* { I2C_BOARD_INFO("tvp5146", 0x5d), }, */ >>

RE: Did I miss any other patches or RFCs that need to be reviewed?

2009-06-15 Thread Karicheri, Muralidharan
Hans, I will do my best to push v3 of this patch this week. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 Phone : 301-515-3736 email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Monday, June 15, 20

RE: [PATCH 1/10 - v2] vpfe capture bridge driver for DM355 and DM6446

2009-06-15 Thread Karicheri, Muralidharan
Hans, I am not clear about some of your comments. Please see below with a [MK] prefix. >> +static int debug; >> +static u32 numbuffers = 3; >> +static u32 bufsize = (720 * 576 * 2); >> + >> +module_param(numbuffers, uint, S_IRUGO); >> +module_param(bufsize, uint, S_IRUGO); >> +module_param(debug,

Re: Did I miss any other patches or RFCs that need to be reviewed?

2009-06-15 Thread Hans Verkuil
On Monday 15 June 2009 20:44:15 Karicheri, Muralidharan wrote: > Hans, > > That is great! > > Once I change the code based on the comments, do you think there is a > chance to get the driver to be merged to 2.6.31 (If so, how soon should I > be ready with the next version, v3 of the patch) or do we

RE: Did I miss any other patches or RFCs that need to be reviewed?

2009-06-15 Thread Karicheri, Muralidharan
Hans, That is great! Once I change the code based on the comments, do you think there is a chance to get the driver to be merged to 2.6.31 (If so, how soon should I be ready with the next version, v3 of the patch) or do we need to wait until 2.6.32? Regards, Murali Karicheri Software Design En

Re: Did I miss any other patches or RFCs that need to be reviewed?

2009-06-15 Thread Hans Verkuil
On Monday 15 June 2009 18:24:53 Karicheri, Muralidharan wrote: > Hans, > > Thanks for your review. I will get back to you if I need more > information on your comments. > > You have reviewed the following patches in this series... > 1,7,8,10 Those were the only ones I had any comments on. So I'm

RE: [PATCH 10/10 - v2] common vpss module for video drivers

2009-06-15 Thread Karicheri, Muralidharan
= >dm644x_clear_wbl_overflow; >> +       else >> +               return -ENODEV; > >Do you need clean up procedure if you return error here? I mean - >calls to release_mem_region, release_mem_region, etc > Oops! I need to add that. Thanks. >> +       spin_lock_init(&oper_cfg.vpss_lock); >> +      

RE: [PATCH 1/10 - v2] vpfe capture bridge driver for DM355 and DM6446

2009-06-15 Thread Karicheri, Muralidharan
>> +       /* set the default image parameters in the device */ >> +       ret = vpfe_config_image_format(vpfe_dev, >> +                               &vpfe_standards[vpfe_dev- >>std_index].std_id); >> +       if (ret) >> +               goto unlock_out; > >Why you check ret value and go to label b

RE: Did I miss any other patches or RFCs that need to be reviewed?

2009-06-15 Thread Karicheri, Muralidharan
Hans, Thanks for your review. I will get back to you if I need more information on your comments. You have reviewed the following patches in this series... 1,7,8,10 Following are part of this series which requires review as well. [PATCH 2/10 - v2] ccdc hw device header file for vpfe capture [PA

Re: Status of PWM, Resizer and VPBE Drivers

2009-06-15 Thread Kevin Hilman
"Karicheri, Muralidharan" writes: > Hi Yusuf, > >> >>I want to query status of pwm, resizer and video processing back end >>drivers. I ported these drivers from MV tree and using them since >>2.6.27. If anybody is not working on these drivers, I would like to >>submit my versions. It would be goo

RE: [PATCH RFC] adding support for setting bus parameters in sub device

2009-06-15 Thread Karicheri, Muralidharan
>> + >> +struct v4l2_subdev_bus { >> +       enum v4l2_subdev_bus_type type; >> +       u8 width; >> +       /* 0 - active low, 1 - active high */ >> +       unsigned pol_vsync:1; >> +       /* 0 - active low, 1 - active high */ >> +       unsigned pol_hsync:1; >> +       /* 0 - low to high , 1 - h

RE: Status of PWM, Resizer and VPBE Drivers

2009-06-15 Thread Karicheri, Muralidharan
Hi Yusuf, > >I want to query status of pwm, resizer and video processing back end >drivers. I ported these drivers from MV tree and using them since >2.6.27. If anybody is not working on these drivers, I would like to >submit my versions. It would be good to have these drivers in >DaVinci tree for

Status of PWM, Resizer and VPBE Drivers

2009-06-15 Thread Yusuf Caglar AKYUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I want to query status of pwm, resizer and video processing back end drivers. I ported these drivers from MV tree and using them since 2.6.27. If anybody is not working on these drivers, I would like to submit my versions. It would be good to have

Question about dvsdk 2.00.00.18 examples

2009-06-15 Thread Ottavio Campana
Hi, I'd like to use a dm6446 to grab video from a camera and to encode it by using h264. By reading some emails that passed on this mailing list, I understood that with MVL5.0 I need to allocate buffers with CMEM and enqueue them to the video driver using user pointers. Successively I have t

RE: [PATCH v4 3/4] ARM: DaVinci: ASoC: Add mcasp support for DM646x

2009-06-15 Thread chaithrika
On Fri, Jun 12, 2009 at 07:01:07, Denys Dmytriyenko wrote: > Chaithrika, > > On Fri, Jun 05, 2009 at 06:28:40AM -0400, Chaithrika U S wrote: > > Adds driver support for the two instances of McASP on TI's DM646x. > > In patch #3 you removed struct evm_snd_platform_data: > > > -struct evm_snd_plat

RE: [alsa-devel] [PATCH v4 1/4] ARM: DaVinci: ASoC: Add the platform devices for ASP

2009-06-15 Thread chaithrika
On Thu, Jun 11, 2009 at 22:42:42, Kevin Hilman wrote: > Chaithrika U S writes: > > > 1) Registers the platform devices for ASP on dm355, dm644x and dm646x so that > > the machine driver can probe to get ASP related platform data. > > 2) Move towards definition of the asp clocks using physical nam