1. 21 10月, 2016 1 次提交
    • M
      [media] dvb-frontends: don't break long lines · 4bd69e7b
      Mauro Carvalho Chehab 提交于
      Due to the 80-cols restrictions, and latter due to checkpatch
      warnings, several strings were broken into multiple lines. This
      is not considered a good practice anymore, as it makes harder
      to grep for strings at the source code.
      
      As we're right now fixing other drivers due to KERN_CONT, we need
      to be able to identify what printk strings don't end with a "\n".
      It is a way easier to detect those if we don't break long lines.
      
      So, join those continuation lines.
      
      The patch was generated via the script below, and manually
      adjusted if needed.
      
      </script>
      use Text::Tabs;
      while (<>) {
      	if ($next ne "") {
      		$c=$_;
      		if ($c =~ /^\s+\"(.*)/) {
      			$c2=$1;
      			$next =~ s/\"\n$//;
      			$n = expand($next);
      			$funpos = index($n, '(');
      			$pos = index($c2, '",');
      			if ($funpos && $pos > 0) {
      				$s1 = substr $c2, 0, $pos + 2;
      				$s2 = ' ' x ($funpos + 1) . substr $c2, $pos + 2;
      				$s2 =~ s/^\s+//;
      
      				$s2 = ' ' x ($funpos + 1) . $s2 if ($s2 ne "");
      
      				print unexpand("$next$s1\n");
      				print unexpand("$s2\n") if ($s2 ne "");
      			} else {
      				print "$next$c2\n";
      			}
      			$next="";
      			next;
      		} else {
      			print $next;
      		}
      		$next="";
      	} else {
      		if (m/\"$/) {
      			if (!m/\\n\"$/) {
      				$next=$_;
      				next;
      			}
      		}
      	}
      	print $_;
      }
      </script>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      4bd69e7b
  2. 05 2月, 2016 1 次提交
  3. 10 6月, 2015 1 次提交
    • M
      [media] dvb: Get rid of typedev usage for enums · 0df289a2
      Mauro Carvalho Chehab 提交于
      The DVB API was originally defined using typedefs. This is against
      Kernel CodingStyle, and there's no good usage here. While we can't
      remove its usage on userspace, we can avoid its usage in Kernelspace.
      
      So, let's do it.
      
      This patch was generated by this shell script:
      
      	for j in $(grep typedef include/uapi/linux/dvb/frontend.h |cut -d' ' -f 3); do for i in $(find drivers/media -name '*.[ch]' -type f) $(find drivers/staging/media -name '*.[ch]' -type f); do sed "s,${j}_t,enum $j," <$i >a && mv a $i; done; done
      
      While here, make CodingStyle fixes on the affected lines.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@osg.samsung.com>
      Acked-by: Stefan Richter <stefanr@s5r6.in-berlin.de> # for drivers/media/firewire/*
      0df289a2
  4. 23 12月, 2014 1 次提交
  5. 14 8月, 2012 1 次提交
  6. 05 1月, 2012 1 次提交
  7. 31 12月, 2011 5 次提交
  8. 07 11月, 2011 1 次提交
  9. 06 12月, 2009 3 次提交
    • D
      V4L/DVB (13332): s5h1409: remove a set register that would cause lock to be lost. · adcd8de6
      Devin Heitmueller 提交于
      On particularly weak signals, changing register 0xab after setting the
      interleave mode will cause the FEC lock to get lost (while still holding the
      EQ lock).  So remove the write entirely, which seems to have had no adverse
      effect in either of my ClearQAM environments (and in particular resolves the
      customer's reported issue).
      
      Also flip around the order of the amhum optimization and the interleave setup
      to be consistent with the windows driver, which has the side-benefit of doing
      them both in the same call (since the amhum optimization can only be done once
      the interleave setup).
      
      This work was sponsored by ONELAN Limited.
      Signed-off-by: NDevin Heitmueller <dheitmueller@kernellabs.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      adcd8de6
    • D
      V4L/DVB (13330): s5h1409: properly handle QAM optimization after lock achieved · f0cd44b4
      Devin Heitmueller 提交于
      The sh51409 driver was only doing the QAM optimization a single time, and it
      would only occur if you received a lock instantaneously after the tuning
      request.  Restructure the code so that the optimization occurs once you reach
      a signal lock.
      
      Note that this depends on the caller polling for status, but we don't have
      much choice at this point without an independent thread monitoring the lock
      status.  Also, at this point pretty much every application polls for status
      lock after doing the tune, so the likelihood of the optimization not occurring
      in the real world is pretty low.
      
      The state machine has also been reworked such that setting the interleave mode
      is now a dependency of doing the QAM optimization.  Before both were mutually
      exclusive, which was not consistent with the Windows driver.  We now have a
      single state machine that controls both.
      
      The changes as-is are only enabled for the HVR-1600.  Once the changes are
      tested with some of the other boards, this change should be made generic and
      the "_legacy" functions should be removed.
      
      This work was sponsored by ONELAN Limited.
      Signed-off-by: NDevin Heitmueller <dheitmueller@kernellabs.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      f0cd44b4
    • D
      V4L/DVB (13329): s5h1409: provide HVR-1600 specific optimizations · af5c8e15
      Devin Heitmueller 提交于
      Perform some optimization of the register configuration based on a trace
      of the HVR-1600 Windows i2c traffic (and consultation with Steven Toth).
      Note that some of these values may be able to be moved into the common driver,
      but I am holding off on that until they can be tested with other boards.
      
      This work was sponsored by ONELAN Limited.
      
      Cc: Steven Toth <stoth@kernellabs.com>
      Signed-off-by: NDevin Heitmueller <dheitmueller@kernellabs.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      af5c8e15
  10. 14 8月, 2009 1 次提交
  11. 01 2月, 2009 1 次提交
  12. 18 10月, 2008 1 次提交
  13. 04 9月, 2008 2 次提交
  14. 20 7月, 2008 1 次提交
  15. 25 4月, 2008 2 次提交
  16. 07 4月, 2008 1 次提交
  17. 26 1月, 2008 4 次提交
  18. 14 12月, 2007 1 次提交
  19. 05 11月, 2007 1 次提交
  20. 10 10月, 2007 3 次提交