On Tue, 30 Apr 2013, Sachin Kamat wrote:
> Silences the following warning:
> WARNING: struct dev_pm_ops should normally be const
>
> Signed-off-by: Sachin Kamat
Thanks, both queued for 3.11
Guennadi
> ---
> drivers/media/i2c/soc_camera/mt9t031.c |2 +-
> 1 file changed, 1 insertion(+), 1
On Wed, 3 Apr 2013, Sachin Kamat wrote:
> Fixes the following checkpatch warnings:
> WARNING: unnecessary whitespace before a quoted newline
> WARNING: please, no space before tabs
>
> Signed-off-by: Sachin Kamat
Thanks, all 7 queued for 3.11
Guennadi
> ---
> drivers/media/platform/soc_camer
On 30 April 2013 14:59, Sachin Kamat wrote:
> Silences the following warning:
> WARNING: struct dev_pm_ops should normally be const
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/media/i2c/soc_camera/mt9t031.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/m
Ping this patch-set.
The first patch for vb2 was acked by Marek.
any suggestion for the second patch?
Regards,
- Seung-Woo Kim
On 2013년 04월 01일 15:40, Seung-Woo Kim wrote:
> As poll behavior described in following link, polling needs to just return if
> already some buffer is in done list.
> Li
From: Lad, Prabhakar
For NV12 format, even if display data is single image,
both VIDWIN0 and VIDWIN1 parameters must be used. The start
address of Y data plane and C data plane is configured in
VIDEOWIN0ADH/L and VIDEOWIN1ADH/L respectively.
cuurently only one layer was requested, which is suffic
Hi Andrzej,
> -Original Message-
> From: linux-leds-ow...@vger.kernel.org [mailto:linux-leds-
> ow...@vger.kernel.org] On Behalf Of Andrzej Hajda
> Sent: Monday, May 06, 2013 6:34 PM
> To: linux-media@vger.kernel.org; linux-l...@vger.kernel.org;
> devicetree-disc...@lists.ozlabs.org
> Cc:
3.9.0-next-20130506-sasha-00012-g01de88a #356 Tainted: GW
[ 160.269486] ---
[ 160.271108] trinity-child3/10132 is trying to acquire lock:
[ 160.271108] (&dev->dev_mutex){+.+.+.}, at: []
m2mtest_mmap+0x51/0x90
[ 160.271108]
[
> Hi Marco,
> I have the same device and the same issue on a 2.6.32 32 bit kernel.
> However, I was able to run the driver successfully on 3.2.44 and 3.9.0
> kernels (both 32 and 64 bit).
> Also, I can run a similar device with a e4000 tuner with no problem even
> on the old 2.6.32 kernel.
> I j
>>> One that appears the same as a GEM object created by userspace. i.e. mmap
>>> works.
>>
>> Oh, we have an mmap interface in the dma_buf thing for that, and iirc
>> Rob Clark even bothered to implement the gem->dma_buf mmap forwarding
>> somewhere. And iirc android's ion-on-dma_buf stuff is eve
On Mon, May 6, 2013 at 4:44 PM, Daniel Vetter wrote:
> On Mon, May 6, 2013 at 9:56 PM, Dave Airlie wrote:
>> On Tue, May 7, 2013 at 1:59 AM, Daniel Vetter wrote:
>>> On Mon, May 06, 2013 at 10:35:35AM +1000, Dave Airlie wrote:
>>
>> However if we don't set a dma mask on the usb device,
On Mon, May 6, 2013 at 9:56 PM, Dave Airlie wrote:
> On Tue, May 7, 2013 at 1:59 AM, Daniel Vetter wrote:
>> On Mon, May 06, 2013 at 10:35:35AM +1000, Dave Airlie wrote:
>>> >>
>>> >> However if we don't set a dma mask on the usb device, the mapping
>>> >> ends up using swiotlb on machines that h
On 05/03/2013 04:29 PM, Devin Heitmueller wrote:
> The lgdt3305 is probably on the second i2c bus -- typical for em2874
> based devices. The tuner is probably gated behind the 3305. It's also
> likely that the 3305 is being held in reset by default. You'll
> probably need to tweak a GPIO to take it
On Tue, May 7, 2013 at 1:59 AM, Daniel Vetter wrote:
> On Mon, May 06, 2013 at 10:35:35AM +1000, Dave Airlie wrote:
>> >>
>> >> However if we don't set a dma mask on the usb device, the mapping
>> >> ends up using swiotlb on machines that have it enabled, which
>> >> is less than desireable.
>> >>
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 May 6 19:00:24 CEST 2013
git branch: test
git hash: 02615ed5e1b2283db2495af3cf8f4ee172c77d80
gcc versi
Il 06/05/2013 13:48, marco caminati ha scritto:
> My thanks to Mauro for his work on this device. Eager to try it, I built
> sources yesterday following directions on
>
> http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
>
> My environment is Tinycore Lin
On Mon, May 06, 2013 at 10:35:35AM +1000, Dave Airlie wrote:
> >>
> >> However if we don't set a dma mask on the usb device, the mapping
> >> ends up using swiotlb on machines that have it enabled, which
> >> is less than desireable.
> >>
> >> Signed-off-by: Dave Airlie
> >
> > Fyi for everyone el
The memcpy in shadow_store() could exceed buffer limits when r > 0.
Signed-off-by: Gianluca Gennari
---
drivers/media/tuners/r820t.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/tuners/r820t.c b/drivers/media/tuners/r820t.c
index d8fd16a..2d6d498 100644
fe->tuner_priv and fe->ops.tuner_ops are initialized twice in r820t_attach().
Remove the redundant initializations and also move fe->ops.tuner_ops
initialization outside of the mutex lock (as in the xc4000 tuner code for
example).
Signed-off-by: Gianluca Gennari
---
drivers/media/tuners/r820t.c
fe->tuner_priv is already freed by hybrid_tuner_release_state().
Signed-off-by: Gianluca Gennari
---
drivers/media/tuners/r820t.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/tuners/r820t.c b/drivers/media/tuners/r820t.c
index 2d6d498..0a5f96b 100644
--- a/drivers/media/tuner
When testing the new r820t driver, I found several potential issues that are
fixed in this patch series.
I've run the driver successfully on several different kernels
(3.2.44 and 3.9.0, in 32 and 64 bit flavors) after upgrading the media drivers
with the media_build script.
Unfortunately, I was no
Hi Arnd,
On Fri, May 3, 2013 at 8:04 PM, Arnd Bergmann wrote:
> On Friday 03 May 2013, Prabhakar Lad wrote:
>>
[snip]
>> +}
>
> Ok, good.
>
>> @@ -955,7 +998,17 @@ static int mt9p031_probe(struct i2c_client *client,
>> mt9p031->pdata = pdata;
>> mt9p031->output_control = MT9P031_O
On Mon April 29 2013 22:52:31 Laurent Pinchart wrote:
> Hi Hans,
>
> Sorry for the late reply.
>
> On Friday 12 April 2013 17:36:16 Hans Verkuil wrote:
> > This RFC looks at adding support for motion detection to V4L2. This is the
> > main missing piece that prevents the go7007 and solo6x10 drive
On Sat, May 04, 2013 at 09:59:50PM +0200, Yann E. MORIN wrote:
> Ezequiel, All,
>
> On Sat, May 04, 2013 at 02:21:44PM -0300, Ezequiel Garcia wrote:
> > I'm trying to split the ac97 support into a separate module.
> > So far I've managed to do this with two different approaches,
> > but both of th
On Fri, Apr 26, 2013 at 11:22:48AM -0300, Mauro Carvalho Chehab wrote:
> Adds a code that (auto)detects gm7113c clones. The auto-detection
> here is not perfect, as, on contrary to what it would be expected
> by looking into its datasheets some devices would return, instead:
>
> saa7115 0-00
On Fri, Apr 26, 2013 at 11:22:47AM -0300, Mauro Carvalho Chehab wrote:
> As we're now seeing other variants from chinese clones, like
> gm1113c, we'll need to add more bits at the detection code.
>
> So, move it into a separate function.
>
> Signed-off-by: Mauro Carvalho Chehab
Tested-by: Ezequ
My thanks to Mauro for his work on this device. Eager to try it, I built
sources yesterday following directions on
http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
My environment is Tinycore Linux 4.7.5:
Linux box 3.0.21-tinycore #3021 SMP Sat Feb 18 11
The patch adds led-flash support to Maxim max77693 chipset.
Device is exposed to user space as a V4L2 subdevice.
It can be accessed via V4L2 controls interface.
Device supports up to two leds which can work in
flash and torch mode. Leds can be triggered externally or
by software.
Device is also exp
This patch adds helper functions for exposing V4L2 flash
subdevice as LED class device. For such device there will be
created appropriate entry in /class/leds/ directory with
standard LED class attributes and attributes corresponding
to V4L2 flash controls exposed by the subdevice.
Signed-off-by:
This RFC proposes generic API for exposing flash subdevices via LED framework.
Rationale
Currently there are two frameworks which are used for exposing LED flash to
user space:
- V4L2 flash controls,
- LED framework(with custom sysfs attributes).
The list below shows flash drivers in mainline ke
Hi,
I am trying to use the previewer to debayer pictures coming from the
filesystem instead of the capture hardware. The media-ctl links are as
follows :
preview V4L input -> preview pad 0 (sink), preview pad 1(src)
->preview V4L output.
Input output format is set via media-ctl for the preview e
30 matches
Mail list logo
