On Sat, May 6, 2017 at 3:50 AM, Thomas Hollstegge
wrote:
> Hi Markus,
>
> Markus Rechberger schrieb am Sat, 06. May 00:33:
>> We had different HW designs based on Empia until 2012 using this USB
>> ID it will not work with many units out there, also with different
>> standby behaviours, chipsets
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: Sat May 6 05:00:23 CEST 2017
media-tree git hash:3622d3e77ecef090b5111e3c5423313f11711dfa
media_build gi
Subject is too long.
On Sat, May 06, 2017 at 04:04:50AM +0300, Gideon Sheril wrote:
> /* The atomisp uses type==0 for the end-of-list marker, so leave space. */
> @@ -152,13 +152,13 @@ const struct camera_af_platform_data
> *camera_get_af_platform_data(void)
> EXPORT_SYMBOL_GPL(camera_get_af_pl
atomisp_gmin_platform.c:
Fix ERROR: spaces instead of tabs and comma/assignment padding error.
Signed-off-by: Gideon Sheril
---
.../platform/intel-mid/atomisp_gmin_platform.c | 166 ++---
1 file changed, 83 insertions(+), 83 deletions(-)
diff --git
a/drivers/staging/media/a
Hi Kieran / Mauro,
On Fri, May 05, 2017 at 06:33:22PM +0100, Kieran Bingham wrote:
> Hi Sakari,
>
> On 04/01/17 08:57, Sakari Ailus wrote:
> > Hi Kieran,
> >
> > Thanks for the patch!
> >
> > On Tue, Jan 03, 2017 at 05:05:58PM +, Kieran Bingham wrote:
> >> On 03/01/17 13:36, Laurent Pinchar
From: Remco Verhoef
this patch will fix one code style problem (ctx:WxE), space
prohibited before that
Signed-off-by: Remco Verhoef
---
.../staging/media/atomisp/platform/intel-mid/atomisp_gmin_platform.c| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/drivers/staging/m
Sundtek MediaTV Digital Home is a rebranded MaxMedia UB425-TC with the
following components:
USB bridge: Empia EM2874B
Demodulator: Micronas DRX 3913KA2
Tuner: NXP TDA18271HDC2
Signed-off-by: Thomas Hollstegge
---
Changes in v2:
- Make the patch apply against linux-media master
drivers/media
Hi Markus,
Markus Rechberger schrieb am Sat, 06. May 00:33:
> We had different HW designs based on Empia until 2012 using this USB
> ID it will not work with many units out there, also with different
> standby behaviours, chipsets etc.
Well, after this patch there's one more device that works wi
Hi Sakari,
On 04/01/17 08:57, Sakari Ailus wrote:
> Hi Kieran,
>
> Thanks for the patch!
>
> On Tue, Jan 03, 2017 at 05:05:58PM +, Kieran Bingham wrote:
>> On 03/01/17 13:36, Laurent Pinchart wrote:
>>> Hi Kieran,
>>>
>>> Thank you for the patch.
>>>
>>> On Tuesday 03 Jan 2017 13:12:11 Kiera
Added "static" storage class to 4 not-declared functions
Signed-off-by: Avraham Shukron
---
.../media/atomisp/platform/intel-mid/atomisp_gmin_platform.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
a/drivers/staging/media/atomisp/platform/intel-mid/atomisp_gmin
On Fri, May 5, 2017 at 11:44 PM, Thomas Hollstegge
wrote:
> Hi Markus,
>
> Markus Rechberger schrieb am Fri, 05. May 08:06:
>> On Fri, May 5, 2017 at 6:21 AM, Thomas Hollstegge
>> wrote:
>> > Sundtek MediaTV Digital Home is a rebranded MaxMedia UB425-TC with the
>> > following components:
>> >
>
Hi Markus,
Markus Rechberger schrieb am Fri, 05. May 08:06:
> On Fri, May 5, 2017 at 6:21 AM, Thomas Hollstegge
> wrote:
> > Sundtek MediaTV Digital Home is a rebranded MaxMedia UB425-TC with the
> > following components:
> >
> > USB bridge: Empia EM2874B
> > Demodulator: Micronas DRX 3913KA2
>
Enable DCMI camera interface on STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 3c99466..617f2f7 100644
---
This patchset introduces a basic support for Digital Camera Memory Interface
(DCMI) of STMicroelectronics STM32 SoC series.
This first basic support implements RGB565 & YUV frame grabbing.
Cropping and JPEG support will be added later on.
This has been tested on STM324x9I-EVAL evaluation board em
Enable DCMI camera interface and OV2640 camera sensor drivers.
Signed-off-by: Hugues Fruchet
---
arch/arm/configs/stm32_defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig
index 84adc88..3f2e4ce 100644
--- a/arc
Enable STMPE1600 GPIO expander.
Signed-off-by: Hugues Fruchet
---
arch/arm/configs/stm32_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig
index a9d8e3c..84adc88 100644
--- a/arch/arm/configs/stm32_defconfig
+++ b/
This adds documentation of device tree bindings for the STM32 DCMI
(Digital Camera Memory Interface).
Acked-by: Rob Herring
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/st,stm32-dcmi.txt| 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Docu
Enable DCMI camera interface on STM32F429 MCU.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32f429.dtsi | 37 +
1 file changed, 37 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index ee0da97..e1ff978
This V4L2 subdev driver enables Digital Camera Memory Interface (DCMI)
of STMicroelectronics STM32 SoC series.
Reviewed-by: Hans Verkuil
Signed-off-by: Yannick Fertre
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/Kconfig| 12 +
drivers/media/platform/Makefile
Enable OV2640 camera support of STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 2bb8
Enable STMPE1600 gpio expander of STM32F429-EVAL board.
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stm32429i-eval.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 617f2f7..2bb8a0
To be able to perform page flips in DRM without flicker we need to be
able to notify the rcar-du module when the VSP has completed its
processing.
We must not have bidirectional dependencies on the two components to
maintain support for loadable modules, thus we extend the API to allow
a callback
Currently we process page flip events on every display interrupt,
however this does not take into consideration the processing time needed
by the VSP1 utilised in the pipeline.
Register a callback with the VSP driver to obtain completion events, and
track them so that we only perform page flips wh
The RCAR-DU utilises a running VSPD pipeline to perform processing for the
display pipeline. This presents the opportunity for some race conditions to
affect the quality of the display output.
To prevent reporting page flips early, we must track this timing through the
VSP1, and only allow the rca
From: Laurent Pinchart
The page flip event is armed in the atomic begin handler, creating a
race condition with the frame end interrupt that could send the event
before the atomic operation actually completes. To avoid that, arm the
event in the atomic flush handler after queuing the page flip.
If we try to commit the display list while an update is pending, we have
missed our opportunity. The display list manager will hold the commit
until the next interrupt.
In this event, we skip the pipeline completion callback handler so that
the pipeline will not mistakenly report frame completion
On 05/05/2017 03:23 PM, Stanimir Varbanov wrote:
> Hi Hans,
>
> On 05/05/2017 02:34 PM, Hans Verkuil wrote:
>> On 04/28/17 11:13, Stanimir Varbanov wrote:
>>> Unfortunatly previous attempt to allow consumer drivers to
>>> use COMPILE_TEST option in Kconfig is not enough, because in the
>>> past th
Fixed spelling mistake of "successfully"
Signed-off-by: Rene Hickersberger
---
drivers/staging/media/s5p-cec/s5p_cec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/s5p-cec/s5p_cec.c
b/drivers/staging/media/s5p-cec/s5p_cec.c
index 2a07968..7e9ace8 100
Hi Hans,
On 05/05/2017 03:44 PM, Hans Verkuil wrote:
> Hi Stanimir,
>
> It looks good to me. I do think that patch 01/10 shouldn't go through
> media. This might mean that we have to drop the COMPILE_TEST dependency
> on the media driver until this firmware driver patch gets merged, which
> is fi
Hi Bjorn
On 05/02/2017 09:52 PM, Bjorn Andersson wrote:
> On Tue 02 May 01:52 PDT 2017, Stanimir Varbanov wrote:
>
>> Hei Sakari,
>>
>> On 04/30/2017 01:21 AM, Sakari Ailus wrote:
>>> Hi, Stan!!
>>>
>>> On Fri, Apr 28, 2017 at 12:13:52PM +0300, Stanimir Varbanov wrote:
>>> ...
+int helper_ge
Hi Hans,
On 05/05/2017 02:34 PM, Hans Verkuil wrote:
> On 04/28/17 11:13, Stanimir Varbanov wrote:
>> Unfortunatly previous attempt to allow consumer drivers to
>> use COMPILE_TEST option in Kconfig is not enough, because in the
>> past the consumer drivers used 'depends on' Kconfig option but
>>
On 04/28/17 13:30, Tomi Valkeinen wrote:
> On 14/04/17 13:25, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> The hdmi_power_on/off_core functions can be called multiple times:
>> when the HPD changes and when the HDMI CEC support needs to power
>> the HDMI core.
>>
>> So use a counter to know whe
> #define DEFINE_SYSFS_PROPERTY(prop, signal, size, mask, check)
> \
> -property_write(prop, signal size, mask, check)
> \
> -property_read(prop, size, mask)
> +(property_write(prop, signal size, mask, check)
> \
> +prop
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.12-1
For:
- New driver to support mediatek jpeg in hardware codec;
- rc-lirc, s5p-cec and st-cec staging drivers got promoted;
- Hardware histogram support for vsp1 driver;
- add
enclosing complex macro expansion with parentheses is
meaningfull according kernel coding style
Signed-off-by: Surender Polsani
---
drivers/staging/media/bcm2048/radio-bcm2048.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/bcm2048/radio-bcm2048.c
On Fri, May 05, 2017 at 10:22:19AM +0200, Boris Brezillon wrote:
> On Fri, 25 Nov 2016 16:48:59 +
> Brian Starkey wrote:
>
> > +/**
> > + * drm_writeback_connector_init - Initialize a writeback connector and its
> > properties
> > + * @dev: DRM device
> > + * @wb_connector: Writeback connect
Hi Stanimir,
It looks good to me. I do think that patch 01/10 shouldn't go through
media. This might mean that we have to drop the COMPILE_TEST dependency
on the media driver until this firmware driver patch gets merged, which
is fine with me as long as this is clearly stated in the commit log for
Hi Ramesh,
Looks good. I replied to patch 3/7 requesting a small change, but otherwise
I'm OK.
The only thing missing is an Ack from Rob for patch 6/7 (R-car DRIF bindings).
Once I have that + an updated patch 3/7 I can make a pull request for this.
Regards,
Hans
On 05/02/17 15:26, Ra
On 05/02/17 15:26, Ramesh Shanmugasundaram wrote:
> This patch adds driver support for the MAX2175 chip. This is Maxim
> Integrated's RF to Bits tuner front end chip designed for software-defined
> radio solutions. This driver exposes the tuner as a sub-device instance
> with standard and custom co
On 04/28/17 11:13, Stanimir Varbanov wrote:
> this add functions for:
> - remove buffers from src/dst queue by index
> - remove exact buffer from src/dst queue
>
> also extends m2m API to iterate over a list of src/dst buffers
> in safely and non-safely manner.
>
> Signed-off-by: Stanimir Var
On 04/28/17 11:13, Stanimir Varbanov wrote:
> Unfortunatly previous attempt to allow consumer drivers to
> use COMPILE_TEST option in Kconfig is not enough, because in the
> past the consumer drivers used 'depends on' Kconfig option but
> now they are using 'select' Kconfig option which means on no
Hi Hugues,
I found a few small things that should be fixed first. It should all be
easy and quick to fix.
On 04/20/17 18:07, Hugues Fruchet wrote:
> This V4L2 subdev driver enables Digital Camera Memory Interface (DCMI)
> of STMicroelectronics STM32 SoC series.
>
> Reviewed-by: Hans Verkuil
> S
The following changes since commit 3622d3e77ecef090b5111e3c5423313f11711dfa:
[media] ov2640: print error if devm_*_optional*() fails (2017-04-25 07:08:21
-0300)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git for-v4.12i
for you to fetch changes up to ad21c
Hi,
On Fri, May 05, 2017 at 11:48:30AM +0300, Sakari Ailus wrote:
> Many camera sensor devices contain EEPROM chips that describe the
> properties of a given unit --- the data is specific to a given unit can
> thus is not stored e.g. in user space or the driver.
>
> Some sensors embed the EEPROM
Hi,
On Fri, May 05, 2017 at 11:48:29AM +0300, Sakari Ailus wrote:
> The lens-focus property contains a phandle to the lens voice coil driver
> that is associated to the sensor; typically both are contained in the same
> camera module.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Pavel Machek
Re
This RFC patchset documents properties commonly required by camera modules
and associated camera flash devices.
The camera module is essentially a package consisting of an image sensor,
a lens, possibly a voice coil to move the lens and a number of other
things that at least the drivers need not
The lens-focus property contains a phandle to the lens voice coil driver
that is associated to the sensor; typically both are contained in the same
camera module.
Signed-off-by: Sakari Ailus
Acked-by: Pavel Machek
---
Documentation/devicetree/bindings/media/video-interfaces.txt | 2 ++
1 file c
On Thu, May 04, 2017 at 04:38:04PM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Tue, May 02, 2017 at 01:25:49PM +0300, Sakari Ailus wrote:
> > Many camera sensor devices contain EEPROM chips that describe the
> > properties of a given unit --- the data is specific to a given unit can
> > thus is n
Camera flash drivers (and LEDs) are separate from the sensor devices in
DT. In order to make an association between the two, provide the
association information to the software.
Signed-off-by: Sakari Ailus
Acked-by: Pavel Machek
Reviewed-by: Sebastian Reichel
---
Documentation/devicetree/bindi
Many camera sensor devices contain EEPROM chips that describe the
properties of a given unit --- the data is specific to a given unit can
thus is not stored e.g. in user space or the driver.
Some sensors embed the EEPROM chip and it can be accessed through the
sensor's I2C interface. This property
Hi,
On Fri, May 05, 2017 at 11:28:34AM +0300, Sakari Ailus wrote:
> Sebastian Reichel wrote:
> > On Tue, May 02, 2017 at 01:25:47PM +0300, Sakari Ailus wrote:
> > > +- flash: An array of phandles that refer to the flash light sources
> > > + related to an image sensor. These could be e.g. LEDs. I
Hi Sebastian,
Sebastian Reichel wrote:
Hi Sakari,
On Tue, May 02, 2017 at 01:25:47PM +0300, Sakari Ailus wrote:
Camera flash drivers (and LEDs) are separate from the sensor devices in
DT. In order to make an association between the two, provide the
association information to the software.
Sig
On Fri, 25 Nov 2016 16:48:59 +
Brian Starkey wrote:
> +/**
> + * drm_writeback_connector_init - Initialize a writeback connector and its
> properties
> + * @dev: DRM device
> + * @wb_connector: Writeback connector to initialize
> + * @funcs: Connector funcs vtable
> + * @formats: Array of su
53 matches
Mail list logo
