On 06/19/2013 12:36 PM, Laurent Pinchart wrote:
Hi Andrzej,
On Wednesday 19 June 2013 12:33:11 Andrzej Hajda wrote:
On 06/19/2013 12:03 AM, Laurent Pinchart wrote:
On Thursday 16 May 2013 10:14:32 Andrzej Hajda wrote:
This patch adds managed versions of initialization
function for media
On 06/20/2013 08:14 AM, P. van Gaans wrote:
Hi all,
(device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio)
Thanks to the message from Philip Pemberton I was able to try loading
the em28xx driver myself using:
sudo modprobe em28xx card=NUMBER
echo eb1a 2885 | sudo tee
Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae:
-Original Message-
From: dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org
[mailto:dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org] On
Behalf Of Russell King - ARM Linux
Sent: Thursday, June
On 20-06-13 09:40, Antti Palosaari wrote:
On 06/20/2013 08:14 AM, P. van Gaans wrote:
Hi all,
(device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio)
Thanks to the message from Philip Pemberton I was able to try loading
the em28xx driver myself using:
sudo modprobe em28xx card=NUMBER
On Thu, Jun 20, 2013 at 09:47:07AM +0200, Lucas Stach wrote:
Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae:
-Original Message-
From: dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org
[mailto:dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org]
On 06/20/2013 11:11 AM, P. van Gaans wrote:
On 20-06-13 09:40, Antti Palosaari wrote:
On 06/20/2013 08:14 AM, P. van Gaans wrote:
Hi all,
(device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio)
Thanks to the message from Philip Pemberton I was able to try loading
the em28xx driver
-Original Message-
From: Lucas Stach [mailto:l.st...@pengutronix.de]
Sent: Thursday, June 20, 2013 4:47 PM
To: Inki Dae
Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho';
'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm-
Am Donnerstag, den 20.06.2013, 09:17 +0100 schrieb Russell King - ARM
Linux:
On Thu, Jun 20, 2013 at 09:47:07AM +0200, Lucas Stach wrote:
Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae:
-Original Message-
From:
Am Donnerstag, den 20.06.2013, 17:24 +0900 schrieb Inki Dae:
[...]
In addition, please see the below more detail examples.
The conventional way (without dmabuf-sync) is:
Task A
1. CPU accesses buf
2. Send the buf to Task B
3. Wait for the buf
-Original Message-
From: Lucas Stach [mailto:l.st...@pengutronix.de]
Sent: Thursday, June 20, 2013 7:11 PM
To: Inki Dae
Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho';
'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm-
None of the ww_mutex codepaths should be taken in the 'normal'
mutex calls. The easiest way to verify this is by using the
normal mutex calls, and making sure o.ctx is unmodified.
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
lib/locking-selftest.c | 62
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
lib/locking-selftest.c | 264 +++-
1 file changed, 261 insertions(+), 3 deletions(-)
diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c
index 37faefd..d554f3f 100644
---
When CONFIG_PROVE_LOCKING is not enabled, more tests are expected to
pass unexpectedly, but there no tests that should start to fail that
pass with CONFIG_PROVE_LOCKING enabled.
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
lib/locking-selftest.c |8 +---
1 file
From: Daniel Vetter daniel.vet...@ffwll.ch
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is
Changes since RFC patch v1:
- Updated to use atomic_long instead of atomic, since the reservation_id was a
long.
- added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
- removed mutex_locked_set_reservation_id (or w/e it was called)
Changes since RFC patch v2:
- remove use of
This will allow me to call functions that have multiple arguments if fastpath
fails.
This is required to support ticket mutexes, because they need to be able to
pass an
extra argument to the fail function.
Originally I duplicated the functions, by adding
__mutex_fastpath_lock_retval_arg.
This
Changes since v4:
- Some documentation cleanups.
- Added a lot more tests to cover all the DEBUG_LOCKS_WARN_ON cases.
- Added EDEADLK tests.
- Split off the normal mutex tests to a separate patch.
- Added a patch to not allow tests to fail that succeed with PROVE_LOCKING
enabled.
---
Daniel
This stresses the lockdep code in some ways specifically useful to
ww_mutexes. It adds checks for most of the common locking errors.
Changes since v1:
- Add tests to verify reservation_id is untouched.
- Use L() and U() macros where possible.
Changes since v2:
- Use the ww_mutex api directly.
* Maarten Lankhorst maarten.lankho...@canonical.com wrote:
Changes since RFC patch v1:
- Updated to use atomic_long instead of atomic, since the reservation_id was
a long.
- added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
- removed mutex_locked_set_reservation_id (or w/e
* Maarten Lankhorst maarten.lankho...@canonical.com wrote:
+The algorithm that TTM came up with for dealing with this problem is quite
+simple. [...]
'TTM' here reads like a person - but in reality it's the TTM graphics
subsystem, right?
Please clarify this portion of the text.
Thanks,
Op 20-06-13 13:55, Ingo Molnar schreef:
* Maarten Lankhorst maarten.lankho...@canonical.com wrote:
Changes since RFC patch v1:
- Updated to use atomic_long instead of atomic, since the reservation_id
was a long.
- added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
- removed
* Maarten Lankhorst maarten.lankho...@canonical.com wrote:
Well they've helped me with some of the changes and contributed some
code and/or fixes, but if acked-by is preferred I'll use that..
Such contributions can be credited in the changelog, and/or copyright
notices, and/or the code
From: Hans Verkuil hans.verk...@cisco.com
These fields are global, not per-filehandle.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-core.c | 1 +
drivers/media/pci/saa7134/saa7134-vbi.c | 11 ++--
drivers/media/pci/saa7134/saa7134-video.c | 102
From: Hans Verkuil hans.verk...@cisco.com
saa6588 always blocked while waiting for data, even if the filehandle
was in non-blocking mode.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/i2c/saa6588.c | 45 +--
This is the second version of an earlier cleanup patch series:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg62863.html
Several patches of that earlier series have already been merged, but the move
of the queue data away from saa7134_fh caused some concern.
After testing with xdtv
From: Hans Verkuil hans.verk...@cisco.com
The empress video node can share resource management with the normal
video nodes, thus allowing for code sharing and making the empress node
non-exclusive.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
From: Hans Verkuil hans.verk...@cisco.com
Use the saa7134_fh struct for the empress video node as well, drop the dev
pointer from that struct since we can use drvdata for that.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-empress.c | 42 ++
From: Hans Verkuil hans.verk...@cisco.com
The video and empress nodes can share various ioctls.
Drop the input/std ioctls from the radio node (out of spec).
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-empress.c | 79 +++-
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-core.c| 9 +-
drivers/media/pci/saa7134/saa7134-empress.c | 142 ++
drivers/media/pci/saa7134/saa7134-video.c | 395
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-empress.c | 19 +
drivers/media/pci/saa7134/saa7134-video.c | 32 +
2 files changed, 38 insertions(+), 13 deletions(-)
From: Hans Verkuil hans.verk...@cisco.com
The saa7134 driver is now converted to the control framework, so drop the
control compat code in saa6752hs.c.
Also add 'const' to several static arrays.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa6752hs.c | 19
From: Hans Verkuil hans.verk...@cisco.com
You can set this through sysfs, so don't mix the two.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/pci/saa7134/saa7134-core.c
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-empress.c | 1 -
include/media/saa6752hs.h | 26 --
2 files changed, 27 deletions(-)
delete mode 100644
From: Hans Verkuil hans.verk...@cisco.com
NO_SYNC was meant for DVB and shouldn't be used anymore.
In this case NO_SIGNAL is a good alternative.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-video.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Hans Verkuil hans.verk...@cisco.com
This driver is independent from saa7134, so there is no reason why this
shouldn't be in media/i2c like all other i2c media drivers.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/i2c/Kconfig | 14 +-
From: Hans Verkuil hans.verk...@cisco.com
There are no controls for the radio node, so just drop support for this ioctl.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/saa7134/saa7134-video.c | 1 -
1 file changed, 1 deletion(-)
diff --git
From: Hans Verkuil hans.verk...@cisco.com
CMD_CLOSE sets data_available_for_read to 1, which is necessary to do the
wakeup call, but it is never reset to 0.
Because of this calling CMD_POLL afterwards will always return that data is
available, even if there isn't any.
Signed-off-by: Hans
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/i2c/saa6588.c | 4
include/media/saa6588.h | 1 -
2 files changed, 5 deletions(-)
diff --git a/drivers/media/i2c/saa6588.c b/drivers/media/i2c/saa6588.c
index 54dd7a0..21cf940
There are a large number of reports that the media build is
not compiling when some drivers are compiled as builtin, while
the needed frontends are compiled as module.
On the last one of such reports:
From: kbuild test robot fengguang...@intel.com
Subject: saa7134-dvb.c:undefined
The $obj-m/$obj-y vars should be adding new modules to build, not
overriding it. So, it should never use
$obj-y := foo.o
instead, it should use:
$obj-y += foo.o
Failing to do that is very bad, as it will suppress needed modules.
Signed-off-by: Mauro Carvalho Chehab
After the change to use IS_ENABLED() everywhere, we started to notice
some troubles with randconfigs, that weren't that trivial to discover
what actually caused them.
Today, I finally found some time to dig into it. I found actually
two problems.
This small patch series should fix them. Those
This pull request removes the last usages of g_chip_ident.
It was originally posted here:
http://www.spinics.net/lists/linux-media/msg64081.html
Most of those patches have already been merged, but due to merge conflicts
I postponed the cx88 change and the actual g_chip_ident removal until the
This pull request makes sure all drivers set v4l2_dev, which is needed for
correct behavior of the debug ioctls if sub-devices are present.
It also fixes a bug in cx88 where the wrong parent was used, causing an
incorrect sysfs hierarchy.
This pull request is identical to the earlier posted
Hi Scott!
My apologies for the delay in reviewing this, it somehow fell through the
cracks...
I have just a few small comments below.
After fixing those, can you also post the output of the v4l2-compliance tool?
(It's part of http://git.linuxtv.org/v4l-utils.git).
Regards,
Hans
On
Jon,
Can you ack this series? I don't see anything wrong with it, but neither am
I a marvell-ccic expert.
I'd like to have your input before I merge this.
Regards,
Hans
On Tue June 4 2013 07:35:44 lbyang wrote:
The patch set adds some feature into the marvell ccic driver
Patch 1:
The following changes since commit 37c1d2e4098e48d9107858246027510efcfd7774:
Merge branch 'linus' into patchwork (2013-06-20 05:19:09 -0300)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git for-v3.11
for you to fetch changes up to
Signed-off-by: Alexander Shiyan shc_w...@mail.ru
---
drivers/media/platform/coda.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/coda.c b/drivers/media/platform/coda.c
index 48b8d7a..1c77781 100644
--- a/drivers/media/platform/coda.c
+++
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: Thu Jun 20 19:00:18 CEST 2013
git branch: test
git hash: 37c1d2e4098e48d9107858246027510efcfd7774
gcc
From: Hans Verkuil hans.verk...@cisco.com
build/media_build/v4l/ml86v7667.c: In function 'ml86v7667_s_ctrl':
build/media_build/v4l/ml86v7667.c:120:6: warning: variable 'ret' set but not
used [-Wunused-but-set-variable]
int ret = 0;
^
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
From: Hans Verkuil hans.verk...@cisco.com
media-git/drivers/media/platform/omap/omap_vout.c: In function ‘omapvid_init’:
media-git/drivers/media/platform/omap/omap_vout.c:382:17: warning: ‘mode’ may
be used uninitialized in this function [-Wmaybe-uninitialized]
vout-dss_mode =
From: Hans Verkuil hans.verk...@cisco.com
media-git/drivers/media/platform/blackfin/bfin_capture.c: In function
‘bcap_probe’:
media-git/drivers/media/platform/blackfin/bfin_capture.c:1007:16: warning:
ignoring return value of ‘vb2_queue_init’, declared with attribute
warn_unused_result
Hi Arun,
On 05/31/2013 03:03 PM, Arun Kumar K wrote:
Please add at least one sentence here. All in all this patch
adds DT binding documentation for a fairly complex subsystem.
And please Cc devicetree-disc...@lists.ozlabs.org next time.
Signed-off-by: Arun Kumar Karun...@samsung.com
---
On 05/31/2013 03:03 PM, Arun Kumar K wrote:
This driver is for the FIMC-IS IP available in Samsung Exynos5
SoC onwards. This patch adds the core files for the new driver.
Signed-off-by: Arun Kumar Karun...@samsung.com
Signed-off-by: Kilyeon Imkilyeon...@samsung.com
---
On 05/31/2013 03:03 PM, Arun Kumar K wrote:
FIMC-IS uses certain sensors which are exclusively controlled
from the IS firmware. This patch adds the sensor subdev for the
fimc-is sensors.
Signed-off-by: Arun Kumar Karun...@samsung.com
Signed-off-by: Kilyeon Imkilyeon...@samsung.com
---
On 05/31/2013 03:03 PM, Arun Kumar K wrote:
fimc-is driver takes video data input from the ISP video node
which is added in this patch. This node accepts Bayer input
buffers which is given from the IS sensors.
Signed-off-by: Arun Kumar Karun...@samsung.com
Signed-off-by: Kilyeon
Hi Guennadi,
Sorry for the response delay and thank you for new review.
Guennadi Liakhovetski wrote:
+ /* output format */
+ switch (icd-current_fmt-host_fmt-fourcc) {
+ case V4L2_PIX_FMT_NV16:
+ iowrite32(ALIGN(cam-width * cam-height, 0x80),
+
Hi Hans,
Thanks for the patch.
On Fri, Jun 21, 2013 at 1:58 AM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
media-git/drivers/media/platform/omap/omap_vout.c: In function ‘omapvid_init’:
media-git/drivers/media/platform/omap/omap_vout.c:382:17: warning:
Hi Sergei and Valadmir,
From: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Date: Fri, 24 May 2013 02:11:28 +0400
(snip)
+/* Similar to set_crop multistage iterative algorithm */
+static int rcar_vin_set_fmt(struct soc_camera_device *icd,
+ struct v4l2_format *f)
58 matches
Mail list logo
