mediapointer-dvb-s2/linux/drivers/media/dvb/pluto2, branch master

Use DIV_ROUND_CLOSEST

2009-08-01T19:48:41+00:00

From: Julia Lawall 

The kernel.h macro DIV_ROUND_CLOSEST performs the computation (x + d/2)/d
but is perhaps more readable.

The semantic patch that makes this change is as follows:
(http://www.emn.fr/x-info/coccinelle/)

// 
@haskernel@
@@


@depends on haskernel@
expression x,__divisor;
@@

- (((x) + ((__divisor) / 2)) / (__divisor))
+ DIV_ROUND_CLOSEST(x,__divisor)
// 

Signed-off-by: Julia Lawall 
Signed-off-by: Mauro Carvalho Chehab

backport commit 284901a90a9e0b812ca3f5f852cbbfb60d10249d

2009-04-14T13:25:59+00:00

From: Mauro Carvalho Chehab 

Author: Yang Hongyang 
    Date:   Mon Apr 6 19:01:15 2009 -0700

    dma-mapping: replace all DMA_32BIT_MASK macro with DMA_BIT_MASK(32)

    Replace all DMA_32BIT_MASK macro with DMA_BIT_MASK(32)

Priority: normal

Signed-off-by: Mauro Carvalho Chehab

[PATCH] pluto2: silence spew of card hung up messages

2009-03-26T20:47:48+00:00

From: Alan Cox 

If the card is ejected on some systems you get a spew of messages as other
shared IRQ devices interrupt between the card eject and the card IRQ
disable.

We don't need to spew them all out

Closes #7472

Signed-off-by: Alan Cox 
Signed-off-by: Mauro Carvalho Chehab

backport commit 7c510e4b730a92cecf94ada45c989d8be0200d47

2008-10-28T00:47:26+00:00

From: Mauro Carvalho Chehab 

Author: Johannes Berg 

    net: convert more to %pM

    A number of places still use %02x:...:%02x because it's
    in debug statements or for no real reason. Make a few
    of them use %pM.

kernel-sync:

Priority: normal

Signed-off-by: Mauro Carvalho Chehab

backport commit 8d8bb39b9eba32dd70e87fd5ad5c5dd4ba118e06

2008-07-27T15:36:24+00:00

From: Mauro Carvalho Chehab 

kernel-sync:
    Author: FUJITA Tomonori 
    Date:   Fri Jul 25 19:44:49 2008 -0700

    dma-mapping: add the device argument to dma_mapping_error()

    Add per-device dma_mapping_ops support for CONFIG_X86_64 as POWER
    architecture does:

    This enables us to cleanly fix the Calgary IOMMU issue that some devices
    are not behind the IOMMU (http://lkml.org/lkml/2008/5/8/423).

    I think that per-device dma_mapping_ops support would be also helpful for
    KVM people to support PCI passthrough but Andi thinks that this makes it
    difficult to support the PCI passthrough (see the above thread).  So I
    CC'ed this to KVM camp.  Comments are appreciated.

    A pointer to dma_mapping_ops to struct dev_archdata is added.  If the
    pointer is non NULL, DMA operations in asm/dma-mapping.h use it.  If it's
    NULL, the system-wide dma_ops pointer is used as before.

    If it's useful for KVM people, I plan to implement a mechanism to register
    a hook called when a new pci (or dma capable) device is created (it works
    with hot plugging).  It enables IOMMUs to set up an appropriate
    dma_mapping_ops per device.

    The major obstacle is that dma_mapping_error doesn't take a pointer to the
    device unlike other DMA operations.  So x86 can't have dma_mapping_ops per
    device.  Note all the POWER IOMMUs use the same dma_mapping_error function
    so this is not a problem for POWER but x86 IOMMUs use different
    dma_mapping_error functions.

    The first patch adds the device argument to dma_mapping_error.  The patch
    is trivial but large since it touches lots of drivers and dma-mapping.h in
    all the architecture.

    This patch:

    dma_mapping_error() doesn't take a pointer to the device unlike other DMA
    operations.  So we can't have dma_mapping_ops per device.

    Note that POWER already has dma_mapping_ops per device but all the POWER
    IOMMUs use the same dma_mapping_error function.  x86 IOMMUs use device
    argument.

    [akpm@linux-foundation.org: fix sge]
    [akpm@linux-foundation.org: fix svc_rdma]
    [akpm@linux-foundation.org: build fix]
    [akpm@linux-foundation.org: fix bnx2x]
    [akpm@linux-foundation.org: fix s2io]
    [akpm@linux-foundation.org: fix pasemi_mac]
    [akpm@linux-foundation.org: fix sdhci]
    [akpm@linux-foundation.org: build fix]
    [akpm@linux-foundation.org: fix sparc]
    [akpm@linux-foundation.org: fix ibmvscsi]

Signed-off-by: Mauro Carvalho Chehab

pluto_set_dma_addr() fix

2008-06-22T14:20:39+00:00

From: Al Viro 

bogus cpu_to_le32() when passing dma address to hardware
via writel() - writel() converts itself.

Signed-off-by: Al Viro 
Signed-off-by: Mauro Carvalho Chehab

Adds selectable adapter numbers as per module option

2008-04-09T19:13:13+00:00

From: Janne Grunau 

The adapter_nr module options can be used to allocate static adapter
numbers on a driver level. It avoids problems with changing DVB apapter
numbers after warm/cold boot or device unplugging and repluging.

Each driver holds DVB_MAX_ADAPTER long array of the preferred order of
adapter numbers.

options dvb-usb-dib0700 adapter_nr=7,6,5,4,3,2,1,0 would result in a
reversed allocation of adapter numbers.

With adapter_nr=2,5 it tries first to get adapter number 2 and 5. If
both are already in use it will allocate the lowest free adapter number.

Signed-off-by: Janne Grunau 
Acked-by: Hermann Pitton 
Signed-off-by: Michael Krufky

dvb: use '+=' instead of '=' for EXTRA_CFLAGS

2007-06-04T23:18:51+00:00

From: Trent Piepho 

The Makefiles in the dvb directory tree used '=' when defining EXTRA_CFLAGS
rather than '+=', which is far more common in the rest of the kernel source.

  =  14 times (9 of which this patch removes)
 :=  25 times
 += 123 times

This change also has certain advantages for the out of kernel v4l-dvb build
system.

Signed-off-by: Trent Piepho

Workaround for bad hardare/firmware on some pluto2 devices

2007-05-01T12:25:56+00:00

From: holger@muscate-magnussen.de 

pluto2_driver: Workaround for pluto2 card reporting wrong number of
received packets and flooding system with interrupts.

This patch constitutes a workaround for a hardware/firmware problem of the
pluto2-based card (e.g., Satelco EasyWatch).

It can happen in rare cases that the card gets into a mode where it
always reports back a number of received packets (nbpackets) which is
larger than the maximum permissible number of packets (TS_DMA_PACKETS).

The workaround that is already in the driver in function pluto_dma_end
reports back zero received packets. In spite of the (in reality) zero
received packets the card continues to generate interrupts at a very
high rate, which can effectively stall the system.

The patch resets the TS logic, which puts the card back into normal
operations.

Signed-off-by: Holger Magnussen 
Signed-off-by: Andreas Oberritter 
Signed-off-by: Mauro Carvalho Chehab

pluto2: fix incorrect TSCR register setting

2007-04-02T13:44:35+00:00

From: Andreas Oberritter 

The ADEF bits in the TSCR register have different meanings in read and
write mode. For this reason ADEF has to be reset on every
read-modify-write operation.

This patch introduces a special write function for this register, which
takes care of it.

Thanks to Holger Magnussen for pointing my nose at this problem.

Signed-off-by: Andreas Oberritter 
Signed-off-by: Mauro Carvalho Chehab