The vivid driver depends on FB, update the Kconfig accordingly.
Signed-off-by: Hans Verkuil
Reported-by: Jim Davis
diff --git a/drivers/media/platform/vivid/Kconfig
b/drivers/media/platform/vivid/Kconfig
index d71139a..c309093 100644
--- a/drivers/media/platform/vivid/Kconfig
+++ b/drivers/med
Commit 4c255791ffd6410f ("asm-generic: io: implement relaxed accessor
macros as conditional wrappers") adds wrappers to asm-generic of
{read,write}{b,w,l,q}_relaxed.
Change CONFIG_PM to CONFIG_PM_SLEEP to solve
warning: 'hix5hd2_ir_suspend' & 'hix5hd2_ir_resume' defined but not used
Reported-by:
Adds support for AmScope MU800 / ToupTek UCMOS08000KPB USB microscope camera.
Signed-off-by: John McMaster
---
drivers/media/usb/gspca/Kconfig | 10 +
drivers/media/usb/gspca/Makefile |2 +
drivers/media/usb/gspca/touptek.c | 829 +
3 files changed,
Em Sun, 28 Sep 2014 13:54:05 +0200
Johannes Stezenbach escreveu:
> On Sun, Sep 28, 2014 at 08:12:11AM -0300, Mauro Carvalho Chehab wrote:
> > Em Sun, 28 Sep 2014 12:55:40 +0200
> > Johannes Stezenbach escreveu:
> >
> > > I tried again both with and without the patch. The issue above
> > > odes
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Mon Sep 29 04:00:23 CEST 2014
git branch: test
git hash: cf3167cf1e969b17671a4d3d956d22718a8ceb85
gcc versi
This field is not used on this driver anymore. Remove it.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/usb/em28xx/em28xx-dvb.c
b/drivers/media/usb/em28xx/em28xx-dvb.c
index 9682c52d67d1..65a456d2f454 100644
--- a/drivers/media/usb/em28xx/em28xx-dvb.c
+++ b/drivers/media/usb/e
Before suspending, we should be stoping streaming, as it
makes no sense to deliver pending URBs after resume. Also,
we need to properly reinitialize the streaming after resume,
otherwise if suspend happens while streaming, it won't be
returning back.
Signed-off-by: Mauro Carvalho Chehab
diff --g
This patch partially reverts 0fb220f2a5cb. What happened is
that the conversion of debug messages to use pr_debug() was a
bad idea, because one needing to debug would need to both
enable debug level via a modprobe parameter, and then to
enable the dynamic printk's.
So, for now, let's use printk()
This patch series addresses some issues with suspend2ram of devices
based on DRX-K.
With this patch series, it is now possible to suspend to ram while
streaming. At resume, the stream will continue to play.
While doing that, I added a few other changes:
- I moved the init code to .init. That is
Instead of initializing the board during frontend attach, do it
latter, when DVB core calls the .init() callback.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb-frontends/drxk_hard.c
b/drivers/media/dvb-frontends/drxk_hard.c
index f140b835c414..18c499acb4c8 100644
--- a/dri
hybrid_tuner_release_state() can free the priv state, so we need to
release the firmware before calling it.
root@debian:~# rmmod em28xx_dvb em28xx_v4l drxk em28xx
[ 1992.790039] em2884 #0: Closing DVB extension
[ 1992.797623] xc5000 2-0061: destroying instance
[ 1992.799595] general protection fau
Some drivers are doing some board-specific init.
The same init is also needed during restore, so, let's
move this code to a separate function.
No functional changes should be noticed so far
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/usb/em28xx/em28xx-dvb.c
b/drivers/media
Hi Matt,
(CC'ing the linux-media mailing list and Mark Ryan from Intel)
Sorry for the late reply.
On Monday 01 September 2014 12:54:02 Matt Wells wrote:
> I'm sure you guys get this a bit. It's on the Dell XPS Camera. As
> far as I can tell, it's the Omniview camera and requires a rebuild of
>
Hi,
I managed to find some time for debugging my original omap3isp DT support
patchset (which includes smiapp DT support as well), and found a few small
but important bugs.
The status is now that images can be captured using the Nokia N9 camera, in
which the sensor is connected to the CSI-2 inter
Em Sun, 28 Sep 2014 23:43:07 +0300
Antti Palosaari escreveu:
>
>
> On 09/28/2014 10:57 PM, Mauro Carvalho Chehab wrote:
> > Em Sun, 28 Sep 2014 21:13:59 +0300
> > Antti Palosaari escreveu:
> >
> >> On 09/28/2014 08:25 PM, Antti Palosaari wrote:
> >>> I want raise that bug:
> >>> Too many ISO f
On 09/28/2014 10:57 PM, Mauro Carvalho Chehab wrote:
Em Sun, 28 Sep 2014 21:13:59 +0300
Antti Palosaari escreveu:
On 09/28/2014 08:25 PM, Antti Palosaari wrote:
I want raise that bug:
Too many ISO frames scheduled when starting stream
https://bugzilla.kernel.org/show_bug.cgi?id=72891
Is th
Em Sun, 28 Sep 2014 21:13:59 +0300
Antti Palosaari escreveu:
> On 09/28/2014 08:25 PM, Antti Palosaari wrote:
> > I want raise that bug:
> > Too many ISO frames scheduled when starting stream
> > https://bugzilla.kernel.org/show_bug.cgi?id=72891
> >
> > Is there anyone who cares to study it? It l
On 09/28/2014 08:25 PM, Antti Palosaari wrote:
I want raise that bug:
Too many ISO frames scheduled when starting stream
https://bugzilla.kernel.org/show_bug.cgi?id=72891
Is there anyone who cares to study it? It looks like em28xx driver bug
or USB host controller driver or both.
According to c
I want raise that bug:
Too many ISO frames scheduled when starting stream
https://bugzilla.kernel.org/show_bug.cgi?id=72891
Is there anyone who cares to study it? It looks like em28xx driver bug
or USB host controller driver or both.
According to comments bug appeared on kernel 3.13.
Is there
Forget it, I invented something strange.
2014-09-28 12:02 GMT+04:00 Matwey V. Kornilov :
> Current parport_irq_handler behaviour is not correct when IRQ is shared.
> LDDv3 on page 279 requires us:
>
> "Be sure to return IRQ_NONE whenever your handler is called and finds
> the device is not interru
Yes it is clearly wrong and as it is trivial and clear bug I recommended
just send patch instead.
Antti
On 09/28/2014 04:27 PM, Nibble Max wrote:
Hello,
static int sp2_remove(struct i2c_client *client)
{
struct si2157 *s = i2c_get_clientdata(client);
..
wrong "struct si2157", it
Hello,
static int sp2_remove(struct i2c_client *client)
{
struct si2157 *s = i2c_get_clientdata(client);
..
wrong "struct si2157", it should be "struct sp2".
Could you check it?
BR,
Max
>Driver for the CIMaX SP2 common interface chip. It is very much based on
>the existing cimax2 dr
Em Sun, 28 Sep 2014 13:54:05 +0200
Johannes Stezenbach escreveu:
> On Sun, Sep 28, 2014 at 08:12:11AM -0300, Mauro Carvalho Chehab wrote:
> > Em Sun, 28 Sep 2014 12:55:40 +0200
> > Johannes Stezenbach escreveu:
> >
> > > I tried again both with and without the patch. The issue above
> > > odes
Em Sun, 28 Sep 2014 13:54:05 +0200
Johannes Stezenbach escreveu:
> On Sun, Sep 28, 2014 at 08:12:11AM -0300, Mauro Carvalho Chehab wrote:
> > Em Sun, 28 Sep 2014 12:55:40 +0200
> > Johannes Stezenbach escreveu:
> >
> > > I tried again both with and without the patch. The issue above
> > > odes
On Sun, Sep 28, 2014 at 08:12:11AM -0300, Mauro Carvalho Chehab wrote:
> Em Sun, 28 Sep 2014 12:55:40 +0200
> Johannes Stezenbach escreveu:
>
> > I tried again both with and without the patch. The issue above
> > odesn't reproduce, but after hibernate it fails to tune
> > (while it works after s
Em Sun, 28 Sep 2014 12:55:40 +0200
Johannes Stezenbach escreveu:
> On Fri, Sep 26, 2014 at 12:43:09PM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 26 Sep 2014 17:22:28 +0200
> > Johannes Stezenbach escreveu:
> >
> > > On Fri, Sep 26, 2014 at 05:06:02PM +0200, Johannes Stezenbach wrote:
> > >
On Fri, Sep 26, 2014 at 12:43:09PM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 26 Sep 2014 17:22:28 +0200
> Johannes Stezenbach escreveu:
>
> > On Fri, Sep 26, 2014 at 05:06:02PM +0200, Johannes Stezenbach wrote:
> > >
> > > [ 20.212162] usb 1-1: reset high-speed USB device number 2 using
>
> Maybe that is proper fix. I didn't test it.
I had some tests with/without inserting a deliberate error return
from dvb_register_frontend() and with/without CONFIG_MODULES option,
and the all combinations seem to have worked fine.
kiitos, Antti and Randy.
--
akihiro
--
To unsubscribe from this l
Current parport_irq_handler behaviour is not correct when IRQ is shared.
LDDv3 on page 279 requires us:
"Be sure to return IRQ_NONE whenever your handler is called and finds
the device is not interrupting."
This is not the case of parport_irq_handler.
Current implementation of IRQ handling use th
29 matches
Mail list logo
