linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: "Mauro Carvalho Chehab" <mchehab@redhat.com>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Alfredo Jesús Delaiti" <alfredodelaiti@netscape.net>
Subject: [PATCH 00/11] Do some improvements/fixups on mb86a20s, cx231xx and em28xx
Date: Sun,  3 Mar 2013 12:58:40 -0300	[thread overview]
Message-ID: <1362326331-17541-1-git-send-email-mchehab@redhat.com> (raw)

While working to add support for a new device, I discovered a
series of issues with mb86a20s and one with em28xx.

While here, I also changed cx231xx to improve its signal
detection, by using a different IF frequency and increasing the
IF signal level from the tuner by 12dB.

Mauro Carvalho Chehab (11):
  [media] mb86a20s: don't pollute dmesg with debug messages
  [media] mb86a20s: adjust IF based on what's set on the tuner
  [media] mb86a20s: provide CNR stats before FE_HAS_SYNC
  [media] mb86a20s: Fix signal strength calculus
  [media] mb86a20s: don't allow updating signal strength too fast
  [media] mb86a20s: change AGC tuning parameters
  [media] mb86a20s: Always reset the frontend with set_frontend
  [media] mb86a20s: Don't reset strength with the other stats
  [media] mb86a20s: cleanup the status at set_frontend()
  [media] cx231xx: Improve signal reception for PV SBTVD
  [media] em28xx-dvb: Don't put device in suspend mode at feed stop

 drivers/media/dvb-core/dmxdev.c         |   3 +-
 drivers/media/dvb-frontends/mb86a20s.c  | 200 +++++++++++++++++++++-----------
 drivers/media/usb/cx231xx/cx231xx-dvb.c |   4 +-
 drivers/media/usb/em28xx/em28xx-dvb.c   |   2 -
 4 files changed, 136 insertions(+), 73 deletions(-)

-- 
1.8.1.4


             reply	other threads:[~2013-03-03 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 15:58 Mauro Carvalho Chehab [this message]
2013-03-03 15:58 ` [PATCH 01/11] [media] mb86a20s: don't pollute dmesg with debug messages Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 02/11] [media] mb86a20s: adjust IF based on what's set on the tuner Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 03/11] [media] mb86a20s: provide CNR stats before FE_HAS_SYNC Mauro Carvalho Chehab
2013-03-04 11:23   ` Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 04/11] [media] mb86a20s: Fix signal strength calculus Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 05/11] [media] mb86a20s: don't allow updating signal strength too fast Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 06/11] [media] mb86a20s: change AGC tuning parameters Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 07/11] [media] mb86a20s: Always reset the frontend with set_frontend Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 08/11] [media] mb86a20s: Don't reset strength with the other stats Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 09/11] [media] mb86a20s: cleanup the status at set_frontend() Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 10/11] [media] cx231xx: Improve signal reception for PV SBTVD Mauro Carvalho Chehab
2013-03-03 15:58 ` [PATCH 11/11] [media] em28xx-dvb: Don't put device in suspend mode at feed stop Mauro Carvalho Chehab

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=1362326331-17541-1-git-send-email-mchehab@redhat.com \
    --to=mchehab@redhat.com \
    --cc=alfredodelaiti@netscape.net \
    --cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).