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: Fri Sep 13 04:00:19 CEST 2013
git branch: test
git hash: f66b2a1c7f2ae3fb0d5b67d07ab4f5055fd3cf16
gcc versi
On Thu, 12 Sep 2013 16:59:57 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> I got a few reports those days about Siano regressions/issues.
>
> The first one was reported at:
>https://bugzilla.kernel.org/show_bug.cgi?id=60645
>
> While its fix was already upstream, the "er
On Thu, 12 Sep 2013 17:04:07 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> The Stellar firmware load routine is different. Improve it to use
> the default firmware, if no modprobe parameter tells otherwise.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> drivers/media/usb/sian
On Thu, 12 Sep 2013 17:00:00 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> Since kernel 3.8, the initialization for Stellar (sms1000)
> devices are broken.
>
> Those devices have a behaviour different than usual sms1100
> and sms2270: they start with one USB ID (devices in cold s
On Thu, 12 Sep 2013 17:00:00 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> Since kernel 3.8, the initialization for Stellar (sms1000)
> devices are broken.
>
> Those devices have a behaviour different than usual sms1100
> and sms2270: they start with one USB ID (devices in cold s
I got a few reports those days about Siano regressions/issues.
The first one was reported at:
https://bugzilla.kernel.org/show_bug.cgi?id=60645
While its fix was already upstream, the "error" messages there doesn't
help, as it induced people to believe that it was a firmware related
error.
At this bugzilla and similar ones:
https://bugzilla.kernel.org/show_bug.cgi?id=60645
Those debug messages were seen as errors, but they're just debug
data, and are OK to appear on sms1100 and sms2270. Re-tag them
to appear only if debug is enabled.
Signed-off-by: Mauro Carvalho Chehab
---
dr
Some messages are not clear, some are debug data, but are
shown as errors, and one message is duplicated.
Cleanup that mess in order to provide a cleaner log.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/siano/smsusb.c | 18 ++
1 file changed, 10 insertions(+), 8 d
On Thu, 12 Sep 2013 16:59:59 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> Some messages are not clear, some are debug data, but are
> shown as errors, and one message is duplicated.
>
> Cleanup that mess in order to provide a cleaner log.
>
> Signed-off-by: Mauro Carvalho Cheha
On Thu, 12 Sep 2013 16:59:58 -0300
Mauro Carvalho Chehab wrote:
Tested-by: André Roth
> At this bugzilla and similar ones:
>https://bugzilla.kernel.org/show_bug.cgi?id=60645
>
> Those debug messages were seen as errors, but they're just debug
> data, and are OK to appear on sms1100 and sms
The Stellar firmware load routine is different. Improve it to use
the default firmware, if no modprobe parameter tells otherwise.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/siano/smsusb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/usb/siano/smsusb.c b/dr
Since kernel 3.8, the initialization for Stellar (sms1000)
devices are broken.
Those devices have a behaviour different than usual sms1100
and sms2270: they start with one USB ID (devices in cold state),
but after firmware load, they get a different USB ID.
This weren't docummented at the driver.
Hi Guennadi,
On 09/12/2013 09:13 PM, Guennadi Liakhovetski wrote:
So, I think, our V4L2 clock enable / disable calls should be balanced, and
to enforce that a warning is helpful. Other opinions?
I'd assume we should enforce those calls balanced, but I might not be
well aware of consequences fo
Hi all
We've got a broken driver in 3.11 and in 3.12-rc and we don't have a clear
way to properly fix it. The problem has been originally reported and
discussed in [1], a patch-set to fix the problem has been proposed in [2],
which actually lead to the topic of this mail - whether or not calls
2_fop_release'
drivers/built-in.o:(.data+0x23b40): undefined reference to
`vb2_ops_wait_prepare'
drivers/built-in.o:(.data+0x23b44): undefined reference to `vb2_ops_wait_finish'
Signed-off-by: Randy Dunlap
Cc: Antti Palosaari
---
drivers/staging/media/msi3101/Kconfig |
ilt-in.o:(.data+0x23b44): undefined reference to `vb2_ops_wait_finish'
Signed-off-by: Randy Dunlap
Cc: Antti Palosaari
---
drivers/staging/media/msi3101/Kconfig | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20130912.orig/drivers/staging/media/msi3101/Kconfig
+++ linux-next-20
e to `vb2_fop_mmap'
> > drivers/built-in.o:(.rodata+0x355a0): undefined reference to
> > `vb2_fop_release'
> > drivers/built-in.o:(.data+0x23b40): undefined reference to
> > `vb2_ops_wait_prepare'
> > drivers/built-in.o:(.data+0x23b44): undefine
Hi Hans
On Wed, Sep 11, 2013 at 3:02 PM, Hans Verkuil wrote:
> Hi Ricardo,
>
> On 09/11/2013 02:13 PM, Ricardo Ribalda Delgado wrote:
>> Hello Hans
>>
>> On Wed, Sep 11, 2013 at 12:49 PM, Hans Verkuil wrote:
>>> Hi Ricardo,
>>>
>>> On 09/11/2013 11:34 AM, Ricardo Ribalda Delgado wrote:
Hi H
Extend v4l2 selection API to support multiple selection areas, this way
sensors that support multiple readout areas can work with multiple areas
of insterest.
The struct v4l2_selection and v4l2_subdev_selection has been extented
with a new field rectangles. If it is value is different than zero th
From: Bjørn Mork
I took a quick look at the code and wonder if the problem is caused by
an initial zero statistics message? This is all just a wild guess, but
if it is correct, then the attached untested patch might fix it...
Bjørn
>From d78a0599d5b5d4da384eae08bf7da316389dfbe5 Mon Sep 17 00:00:
This patch adds support for SCALER device which is a new device
for scaling, blending, color fill and color space conversion
on EXYNOS5410 and EXYNOS5420 SoCs.
This device supports the followings as key feature.
input image format
- YCbCr420 2P(UV/VU), 3P
- YCbCr422 1P(YUYV/UY
This patch adds support for SCALER device which is a
new device for scaling, blending, color fill and color space
conversion on EXYNOS5410/5420 SoCs.
This device supports the following as key features.
input image format
- YCbCr420 2P(UV/VU), 3P
- YCbCr422 1P(YUYV/UYVY/YVYU),
This patch adds the Makefile and memory to memory (m2m) interface
functionality for the SCALER driver.
Signed-off-by: Shaik Ameer Basha
---
drivers/media/platform/Kconfig|8 +
drivers/media/platform/Makefile |1 +
drivers/media/platform/exynos-scaler
This patch adds the DT binding documentation for the
Exynos5420/5410 based SCALER device driver.
Signed-off-by: Shaik Ameer Basha
---
.../devicetree/bindings/media/exynos5-scaler.txt | 22
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bind
This patch adds the core functionality for the SCALER driver.
Signed-off-by: Shaik Ameer Basha
---
drivers/media/platform/exynos-scaler/scaler.c | 1261 +
drivers/media/platform/exynos-scaler/scaler.h | 385
2 files changed, 1646 insertions(+)
create mode 10064
On certain platforms a sequence of dma_map_sg() and dma_unmap_sg()
discards data previously stored in the buffers. Build video headers
only after the DMA is completed.
Signed-off-by: Krzysztof Hałasa
diff --git a/drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
b/drivers/staging/media/solo6x1
Signed-off-by: Krzysztof Hałasa
diff --git a/drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
b/drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
index a4c5896..e501287 100644
--- a/drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
+++ b/drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c
@@
Signed-off-by: Krzysztof Hałasa
diff --git a/drivers/staging/media/solo6x10/solo6x10-disp.c
b/drivers/staging/media/solo6x10/solo6x10-disp.c
index 32d9953..884512e 100644
--- a/drivers/staging/media/solo6x10/solo6x10-disp.c
+++ b/drivers/staging/media/solo6x10/solo6x10-disp.c
@@ -176,18 +176,26
Signed-off-by: Krzysztof Hałasa
diff --git a/drivers/staging/media/solo6x10/solo6x10.h
b/drivers/staging/media/solo6x10/solo6x10.h
index 6f91d2e..f1bbb8c 100644
--- a/drivers/staging/media/solo6x10/solo6x10.h
+++ b/drivers/staging/media/solo6x10/solo6x10.h
@@ -94,7 +94,6 @@
#define SOLO_ENC_MOD
This patch adds subdev driver for Samsung S5K4E5 raw image sensor.
Like s5k6a3, it is also another fimc-is firmware controlled
sensor. This minimal sensor driver doesn't do any I2C communications
as its done by ISP firmware. It can be updated if needed to a
regular sensor driver by adding the I2C c
This patch adds the register definition file for the fimc-is driver
and also the header file containing the main context for the driver.
Signed-off-by: Arun Kumar K
Signed-off-by: Kilyeon Im
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exynos5-is/fimc-is-regs.h | 105 +++
FIMC-IS has two hardware scalers named as scaler-codec and
scaler-preview. This patch adds the common code handling the
video nodes and subdevs of both the scalers.
Signed-off-by: Arun Kumar K
Signed-off-by: Kilyeon Im
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exynos5-is/fimc-
s5k6a3 sensor has actual pixel resolution of 1408x1402 against
the active resolution 1392x1392. The real resolution is needed
when raw sensor SRGB data is dumped to memory by fimc-lite.
Signed-off-by: Arun Kumar K
Reviewed-by: Sylwester Nawrocki
---
drivers/media/i2c/s5k6a3.c | 10 ++
The hardware interface module finally sends the commands to the
FIMC-IS firmware and runs the interrupt handler for getting the
responses.
Signed-off-by: Arun Kumar K
Signed-off-by: Kilyeon Im
Reviewed-by: Sylwester Nawrocki
---
.../media/platform/exynos5-is/fimc-is-interface.c | 810 +++
This patch adds the crucial hardware pipeline control for the
fimc-is driver. All the subdev nodes will call this pipeline
interfaces to reach the hardware. Responsibilities of this module
involves configuring and maintaining the hardware pipeline involving
multiple sub-ips like ISP, DRC, Scalers,
Some sensors to be used with fimc-is are exclusively controlled
by the fimc-is firmware. This minimal sensor driver provides
the required info for the firmware to configure the sensors
sitting on I2C bus.
Signed-off-by: Arun Kumar K
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exy
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 K
Signed-off-by: Kilyeon Im
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exynos5-is/fimc
Adds Kconfig and Makefile for exynos5-is driver files.
Signed-off-by: Shaik Ameer Basha
Signed-off-by: Arun Kumar K
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/Kconfig |1 +
drivers/media/platform/Makefile|1 +
drivers/media/platform/exynos5-is/Kc
The patch adds the DT binding documentation for Samsung
Exynos5 SoC series imaging subsystem (FIMC-IS).
Signed-off-by: Arun Kumar K
Reviewed-by: Sylwester Nawrocki
---
.../devicetree/bindings/media/exynos5-fimc-is.txt | 46
1 file changed, 46 insertions(+)
create mode 1
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 K
Signed-off-by: Kilyeon Im
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exynos5-is/fimc-is-core.c | 413 +
The patch series add support for Exynos5 camera subsystem. It
re-uses mipi-csis and fimc-lite from exynos4-is and adds a new
media device and fimc-is device drivers for exynos5.
The media device supports asynchronos subdev registration for the
fimc-is sensors and is tested on top of the patch serie
Hi Hans,
On 09/11/2013 04:01 PM, Hans Verkuil wrote:
> On 09/11/2013 03:07 PM, Sylwester Nawrocki wrote:
>> On 09/09/2013 11:07 AM, Hans Verkuil wrote:
>>> On 09/06/2013 12:33 AM, Sylwester Nawrocki wrote:
On 08/07/2013 07:49 PM, Hans Verkuil wrote:
> On 08/07/2013 06:49 PM, Sylwester Naw
On Mon, Sep 9, 2013 at 9:00 AM, Michael Opdenacker
wrote:
> This patch proposes to remove the IRQF_DISABLED flag from
> davinci media platform drivers.
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
Acked-by: Lad, Prabhakar
Regrads,
--Prabhak
Vá?ení: Webmail Subscriber
Oznamujeme vám, ?e vá? e-mailový ú?et presiahol
skladovacie kapacity. Nebudete môc? odosiela? a prijíma? e-maily a va?e
e-mailový ú?et, budú vymazané z ná?ho servera. Ak sa chcete tomuto
problému vyhnú?,
kliknite: http://webmailupdate20323421.jimdo.com/
tpre aktu
44 matches
Mail list logo
