Re: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-04-01 Thread Mauro Carvalho Chehab
Muralidharan Karicheri wrote:
 Mauro,
 
 When I had last replied to your email, I didn't check if the patch is
 actually applied to your v4l_for_linux branch of fixes.git tree. But
 Today I checked and I can't find the patch merged to this tree as you
 had mentioned..
 
 So if you haven't merged it for some reason, please merge my updated patch
 available at https://patchwork.kernel.org/patch/86731/
 

I had merged, but, as I haven't pushed on linuxtv, I decided to rebase my local
tree. Patch applied.

-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-04-01 Thread Karicheri, Muralidharan
Mauro,

Thanks a lot for your support.

Do you plan to merge my pull request for 2.6.35 anytime soon?

Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com

-Original Message-
From: Mauro Carvalho Chehab [mailto:mche...@redhat.com]
Sent: Thursday, April 01, 2010 12:21 PM
To: Muralidharan Karicheri
Cc: Karicheri, Muralidharan; linux-media@vger.kernel.org;
hverk...@xs4all.nl; davinci-linux-open-sou...@linux.davincidsp.com
Subject: Re: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash
on DM365

Muralidharan Karicheri wrote:
 Mauro,

 When I had last replied to your email, I didn't check if the patch is
 actually applied to your v4l_for_linux branch of fixes.git tree. But
 Today I checked and I can't find the patch merged to this tree as you
 had mentioned..

 So if you haven't merged it for some reason, please merge my updated
patch
 available at https://patchwork.kernel.org/patch/86731/


I had merged, but, as I haven't pushed on linuxtv, I decided to rebase my
local
tree. Patch applied.

--

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-04-01 Thread Mauro Carvalho Chehab
Karicheri, Muralidharan wrote:
 Mauro,
 
 Thanks a lot for your support.
 
 Do you plan to merge my pull request for 2.6.35 anytime soon?

It were already merged locally. I'm running a compilation of the
tree with the merged patches. If all compile ok, your pull request
(and others) will be at linuxtv server soon.

-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-03-27 Thread Muralidharan Karicheri
Mauro,

When I had last replied to your email, I didn't check if the patch is
actually applied to your v4l_for_linux branch of fixes.git tree. But
Today I checked and I can't find the patch merged to this tree as you
had mentioned..

So if you haven't merged it for some reason, please merge my updated patch
available at https://patchwork.kernel.org/patch/86731/

Murali

On Wed, Mar 24, 2010 at 3:50 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
 Hi Murali,

 Karicheri, Muralidharan wrote:
 Please discard this patch. I have sent an updated version to the list.

 The patch were already added at the fixes tree. I can't just discard, since 
 this
 would break any other tree based on it. If the patch is so deadly broken, then
 we can add a rollback patch, making our and upstream tree dirty. Another 
 alternative
 would be to add just a diff between the two patches.

 Btw, please send me a patchwork ID when you want to refer to a patch sent
 to the mailing list, especially when there are two patches with the same name.
 Is this the one you're referring?
        X-Patchwork-Id: 86729

 Cheers,
 Mauro.
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html




-- 
Murali Karicheri
mkarich...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-03-24 Thread Mauro Carvalho Chehab
Hi Murali,

Karicheri, Muralidharan wrote:
 Please discard this patch. I have sent an updated version to the list.

The patch were already added at the fixes tree. I can't just discard, since this
would break any other tree based on it. If the patch is so deadly broken, then
we can add a rollback patch, making our and upstream tree dirty. Another 
alternative
would be to add just a diff between the two patches.

Btw, please send me a patchwork ID when you want to refer to a patch sent
to the mailing list, especially when there are two patches with the same name.
Is this the one you're referring?
X-Patchwork-Id: 86729

Cheers,
Mauro.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-03-24 Thread Karicheri, Muralidharan
Mauro,

 Please discard this patch. I have sent an updated version to the list.

The patch were already added at the fixes tree. I can't just discard, since
this
would break any other tree based on it.

Ok. 
 If the patch is so deadly broken,
then
we can add a rollback patch, making our and upstream tree dirty. Another
alternative
would be to add just a diff between the two patches.


Not broken. I can send you another patch for adding the diff.

Btw, please send me a patchwork ID when you want to refer to a patch sent
to the mailing list, especially when there are two patches with the same
name.
Is this the one you're referring?
   X-Patchwork-Id: 86729

Yes. That is the one. I will send you a diff patch. Sorry for the trouble.


Cheers,
Mauro.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on DM365

2010-03-18 Thread Karicheri, Muralidharan
Please discard this patch. I have sent an updated version to the list.

Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com

-Original Message-
From: Karicheri, Muralidharan
Sent: Wednesday, March 17, 2010 1:19 PM
To: linux-media@vger.kernel.org; hverk...@xs4all.nl
Cc: davinci-linux-open-sou...@linux.davincidsp.com; Karicheri, Muralidharan
Subject: [GIT FIX for 2.6.34] V4L - vpfe capture - fix for kernel crash on
DM365

From: Muralidharan Karicheri m-kariche...@ti.com

As part of upstream merge, set_params() function was removed from isif.c.
This requires
removal of BUG_ON() and check for set_params ptr in vpfe_capture.c.

Signed-off-by: Muralidharan Karicheri m-kariche...@ti.com
---
 drivers/media/video/davinci/vpfe_capture.c |   24 +---
 1 files changed, 13 insertions(+), 11 deletions(-)

diff --git a/drivers/media/video/davinci/vpfe_capture.c
b/drivers/media/video/davinci/vpfe_capture.c
index 91f665b..aa7dd65 100644
--- a/drivers/media/video/davinci/vpfe_capture.c
+++ b/drivers/media/video/davinci/vpfe_capture.c
@@ -222,7 +222,6 @@ int vpfe_register_ccdc_device(struct ccdc_hw_device
*dev)
   BUG_ON(!dev-hw_ops.get_frame_format);
   BUG_ON(!dev-hw_ops.get_pixel_format);
   BUG_ON(!dev-hw_ops.set_pixel_format);
-  BUG_ON(!dev-hw_ops.set_params);
   BUG_ON(!dev-hw_ops.set_image_window);
   BUG_ON(!dev-hw_ops.get_image_window);
   BUG_ON(!dev-hw_ops.get_line_length);
@@ -1704,16 +1703,19 @@ static long vpfe_param_handler(struct file *file,
void *priv,
   case VPFE_CMD_S_CCDC_RAW_PARAMS:
   v4l2_warn(vpfe_dev-v4l2_dev,
 VPFE_CMD_S_CCDC_RAW_PARAMS: experimental ioctl\n);
-  ret = ccdc_dev-hw_ops.set_params(param);
-  if (ret) {
-  v4l2_err(vpfe_dev-v4l2_dev,
-  Error in setting parameters in CCDC\n);
-  goto unlock_out;
-  }
-  if (vpfe_get_ccdc_image_format(vpfe_dev, vpfe_dev-fmt)  0) {
-  v4l2_err(vpfe_dev-v4l2_dev,
-  Invalid image format at CCDC\n);
-  goto unlock_out;
+  if (ccdc_dev-hw_ops.set_params) {
+  ret = ccdc_dev-hw_ops.set_params(param);
+  if (ret) {
+  v4l2_err(vpfe_dev-v4l2_dev,
+  Error setting parameters in CCDC\n);
+  goto unlock_out;
+  }
+  if (vpfe_get_ccdc_image_format(vpfe_dev,
+ vpfe_dev-fmt)  0) {
+  v4l2_err(vpfe_dev-v4l2_dev,
+  Invalid image format at CCDC\n);
+  goto unlock_out;
+  }
   }
   break;
   default:
--
1.6.0.4

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html