From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Deepthy Ravi <deepthy.ravi@ti.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@infradead.org, linux-omap@vger.kernel.org,
Abhilash K V <abhilash.kv@ti.com>
Subject: Re: [PATCH 1/2] omap3: ISP: Fix the failure of CCDC capture during suspend/resume
Date: Tue, 30 Aug 2011 23:07:47 +0200 [thread overview]
Message-ID: <201108302307.47564.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1312984992-19315-1-git-send-email-deepthy.ravi@ti.com>
Hi,
On Wednesday 10 August 2011 16:03:12 Deepthy Ravi wrote:
> From: Abhilash K V <abhilash.kv@ti.com>
>
> While resuming from the "suspended to memory" state,
> occasionally CCDC fails to get enabled and thus fails
> to capture frames any more till the next suspend/resume
> is issued.
> This is a race condition which happens only when a CCDC
> frame-completion ISR is pending even as ISP device's
> isp_pm_prepare() is getting called and only one buffer
> is left on the DMA queue.
> The DMA queue buffers are thus depleted which results in
> its underrun.So when ISP resumes there are no buffers on
> the queue (as the application which can issue buffers is
> yet to resume) to start video capture.
> This fix addresses this issue by dequeuing and enqueing
> the last buffer in isp_pm_prepare() after its DMA gets
> completed. Thus,when ISP resumes it always finds atleast
> one buffer on the DMA queue - this is true if application
> uses only 3 buffers.
How is that problem specific to the CCDC ? Can't it be reproduce at the
preview engine or resizer output as well ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2011-08-30 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 14:03 Deepthy Ravi
2011-08-30 21:07 ` Laurent Pinchart [this message]
2011-09-07 10:10 ` Koyamangalath, Abhilash
2011-09-07 10:36 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201108302307.47564.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=abhilash.kv@ti.com \
--cc=deepthy.ravi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®