From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] saa7134: Add pm_qos_request to fix video corruption
Date: Mon, 29 Oct 2012 11:25:38 +0000 [thread overview]
Message-ID: <3124636.sEoNQbeq5Q@f17simon> (raw)
In-Reply-To: <1350906611-17498-1-git-send-email-simon.farnsworth@onelan.co.uk>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Monday 22 October 2012 12:50:11 Simon Farnsworth wrote:
> The SAA7134 appears to have trouble buffering more than one line of video
> when doing DMA. Rather than try to fix the driver to cope (as has been done
> by Andy Walls for the cx18 driver), put in a pm_qos_request to limit deep
> sleep exit latencies.
>
> The visible effect of not having this is that seemingly random lines are
> only partly transferred - if you feed in a static image, you see a portion
> of the image "flicker" into place.
>
> Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Hello Mauro,
I've just noticed that I forgot to CC you in on this patch I sent last week -
Patchwork grabbed it at https://patchwork.kernel.org/patch/1625311/ but if you
want me to resend it so that you've got it in a mailbox for consideration,
just let me know.
--
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-10-29 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 11:50 [PATCH] saa7134: Add pm_qos_request to fix video corruption Simon Farnsworth
2012-10-29 11:25 ` Simon Farnsworth [this message]
2012-10-29 11:58 ` Mauro Carvalho Chehab
2012-10-29 13:02 ` Simon Farnsworth
2012-10-29 13:32 ` Andy Walls
2012-10-29 14:11 ` Simon Farnsworth
2012-10-29 15:44 ` Mauro Carvalho Chehab
2012-10-29 16:03 ` Simon Farnsworth
2012-10-30 15:11 ` Alan Stern
2012-12-04 17:22 ` Mauro Carvalho Chehab
2012-10-29 14:27 ` Andy Walls
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=3124636.sEoNQbeq5Q@f17simon \
--to=simon.farnsworth@onelan.co.uk \
--cc=linux-media@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