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 May 5 05:00:17 CEST 2017
media-tree git hash:3622d3e77ecef090b5111e3c5423313f11711dfa
media_build
Dne 2.5.2017 v 16:43 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
>> During the transfer from the soc_camera a test in pxa_mbus_image_size()
>> got removed. Without it any PXA_MBUS_LAYOUT_PACKED format causes either
>> the return of a wrong value (PXA_MBUS_PACKING_2X8_PADHI
Dne 2.5.2017 v 16:53 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
>> In 'commit 295ab497d6357 ("[media] media: platform: pxa_camera: make
>> printk consistent")' a pointer to the device structure in
>> mclk_get_divisor() was changed to pcdev_to_dev(pcdev). The pointer used
Em Fri, 5 May 2017 01:14:29 +0200
Reinhard Speyerer escreveu:
> On Thu, May 04, 2017 at 09:11:47AM -0300, Mauro Carvalho Chehab wrote:
> > Em Thu, 4 May 2017 09:55:04 +0200
> > Gregor Jasny escreveu:
> >
> > > Hello Mauro,
> > >
> > > On 04.05.17
Fix checkpatch warning: removed unnecessary initialization of
static variable "skip_fwload" to 0 in source atomisp_v4l2.c
Signed-off-by: Fabrizio Perria
---
drivers/staging/media/atomisp/pci/atomisp2/atomisp_v4l2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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
> Tuner: NXP TDA18271HDC2
>
Not that it matters
On Thu, May 04, 2017 at 09:11:47AM -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 4 May 2017 09:55:04 +0200
> Gregor Jasny escreveu:
>
> > Hello Mauro,
> >
> > On 04.05.17 00:33, Mauro Carvalho Chehab wrote:
> > > Em Wed, 3 May 2017 09:53:03 -0300
> > > Mauro Carvalho
On Thu, May 04, 2017 at 11:32:08PM +0300, Sakari Ailus wrote:
> Hi Philipp,
>
> On Thu, May 04, 2017 at 03:38:57PM +0200, Philipp Zabel wrote:
> ...
> > +static const struct of_device_id video_mux_dt_ids[] = {
> > + { .compatible = "video-mux", },
> > + { /* sentinel */ }
> > +};
> >
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
---
drivers/media/usb/em28xx/em28xx-cards.c | 15
Hi Niklas,
On Thu, May 04, 2017 at 11:30:19PM +0200, Niklas Söderlund wrote:
> Hi Sakari,
>
> Thanks for your feedback.
You're welcome!
> On 2017-05-04 16:35:26 +0300, Sakari Ailus wrote:
> > Hi Niklas,
> >
> > On Fri, Apr 28, 2017 at 12:36:58AM +0200, Niklas Söderlund wrote:
> > > A V4L2
Fix function prototype so the position of arguments camif->colorfx_cb and
camif->colorfx_cr match the order of the parameters when calling
camif_hw_set_effect() function.
Addresses-Coverity-ID: 1248800
Addresses-Coverity-ID: 1269141
Cc: Sylwester Nawrocki
Switch users of the v4l2_of_ APIs to the more generic v4l2_fwnode_ APIs.
Async OF matching is replaced by fwnode matching and OF matching support
is removed.
Signed-off-by: Sakari Ailus
Acked-by: Benoit Parrot # i2c/ov2569.c, am437x/am437x-vpfe.c
Hi!
> 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
Hi Philipp,
Thanks for the patch!
On Thu, May 04, 2017 at 03:37:30PM +0200, Philipp Zabel wrote:
...
> @@ -194,11 +195,11 @@ static int imx_media_subdev_bound(struct
> v4l2_async_notifier *notifier,
> struct v4l2_async_subdev *asd)
> {
> struct
Hi Sakari,
Thanks for your feedback.
On 2017-05-04 16:35:26 +0300, Sakari Ailus wrote:
> Hi Niklas,
>
> On Fri, Apr 28, 2017 at 12:36:58AM +0200, Niklas Söderlund wrote:
> > A V4L2 driver for Renesas R-Car MIPI CSI-2 receiver. The driver
> > supports the rcar-vin driver on R-Car Gen3 SoCs where
Hello Sylwester,
Quoting Sylwester Nawrocki :
Hi Gustavo,
On 05/04/2017 09:05 PM, Gustavo A. R. Silva wrote:
The issue here is that the position of arguments in the call to
camif_hw_set_effect() function do not match the order of the parameters:
Hi Philipp,
On Thu, May 04, 2017 at 03:38:57PM +0200, Philipp Zabel wrote:
...
> +static const struct of_device_id video_mux_dt_ids[] = {
> + { .compatible = "video-mux", },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, video_mux_dt_ids);
> +
> +static struct platform_driver
On Wed, 15 Mar 2017 23:22:09 +0100
Andreas Kemnade wrote:
> i2c bus is already needed when the frontend is probed,
> so init it already in it930x_frontend_attach
> That prevents errors like
> si2168: probe of 6-0067 failed with error -5
>
> Signed-off-by: Andreas
Hi Gustavo,
On 05/04/2017 09:05 PM, Gustavo A. R. Silva wrote:
> The issue here is that the position of arguments in the call to
> camif_hw_set_effect() function do not match the order of the parameters:
>
> camif->colorfx_cb is passed to cr
> camif->colorfx_cr is passed to cb
>
> This is the
Hello everybody,
While looking into Coverity ID 1248800 I ran into the following piece
of code at drivers/media/platform/s3c-camif/camif-capture.c:67:
/* Locking: called with camif->slock spinlock held */
static int s3c_camif_hw_init(struct camif_dev *camif, struct camif_vp *vp)
{
From: Markus Elfring
Date: Thu, 4 May 2017 19:14:15 +0200
Seven single characters (line breaks) should be put into a sequence.
Thus use the corresponding function "seq_putc".
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
On Thu, May 4, 2017 at 5:36 PM, Philipp Zabel wrote:
> Hi Arnd,
>
> On Thu, 2017-05-04 at 17:24 +0200, Arnd Bergmann wrote:
>> On Thu, May 4, 2017 at 5:20 PM, Philipp Zabel wrote:
>> > The below mentioned fix contains a small but severe bug,
>> >
From: Tvrtko Ursulin
Scatterlist entries have an unsigned int for the offset so
correct the sg_alloc_table_from_pages function accordingly.
Since these are offsets withing a page, unsigned int is
wide enough.
Also converts callers which were using unsigned long
Hi Arnd,
On Thu, 2017-05-04 at 17:24 +0200, Arnd Bergmann wrote:
> On Thu, May 4, 2017 at 5:20 PM, Philipp Zabel wrote:
> > The below mentioned fix contains a small but severe bug,
> > fix it to make the driver work again.
> >
> > Fixes: 3538aa6ecfb2 ("[media] tc358743:
On Thu, May 4, 2017 at 5:20 PM, Philipp Zabel wrote:
> The below mentioned fix contains a small but severe bug,
> fix it to make the driver work again.
>
> Fixes: 3538aa6ecfb2 ("[media] tc358743: fix register i2c_rd/wr functions")
> Cc: Arnd Bergmann
> Cc:
Hi Sakari,
On Thu, May 4, 2017 at 4:45 PM, Sakari Ailus wrote:
>> --- a/drivers/media/platform/rcar-vin/rcar-dma.c
>> +++ b/drivers/media/platform/rcar-vin/rcar-dma.c
>> @@ -16,6 +16,7 @@
>>
>> #include
>> #include
>> +#include
>>
>> #include
>>
>> @@ -1240,3 +1241,45
The below mentioned fix contains a small but severe bug,
fix it to make the driver work again.
Fixes: 3538aa6ecfb2 ("[media] tc358743: fix register i2c_rd/wr functions")
Cc: Arnd Bergmann
Cc: Hans Verkuil
Cc: Mauro Carvalho Chehab
Add bindings documentation for the video multiplexer device.
Signed-off-by: Sascha Hauer
Signed-off-by: Philipp Zabel
Signed-off-by: Steve Longerbeam
Acked-by: Sakari Ailus
Reviewed-by:
This driver can handle SoC internal and external video bus multiplexers,
controlled by mux controllers provided by the mux controller framework,
such as MMIO register bitfields or GPIOs. The subdevice passes through
the mbus configuration of the active input to the output side.
Signed-off-by:
Hi Niklas,
On Fri, Apr 28, 2017 at 12:41:57AM +0200, Niklas Söderlund wrote:
> In media controller mode all VIN instances needs to be part of the same
> media graph. There is also a need to each VIN instance to know and in
> some cases be able to communicate with other VIN instances.
>
> Add a
Hi Sebastian,
On Thu, 2017-05-04 at 16:21 +0200, Sebastian Reichel wrote:
> Hi,
>
> On Thu, May 04, 2017 at 03:38:57PM +0200, Philipp Zabel wrote:
> > This driver can handle SoC internal and external video bus multiplexers,
> > controlled by mux controllers provided by the mux controller
Hi Kieran,
On Thu, 2017-05-04 at 15:59 +0100, Kieran Bingham wrote:
> Hi Philipp,
>
> Thankyou for the patch,
thank you for reviewing.
> On 04/05/17 14:38, Philipp Zabel wrote:
> > This driver can handle SoC internal and external video bus multiplexers,
> > controlled by mux controllers
Hi Niklas,
On Fri, Apr 28, 2017 at 12:41:55AM +0200, Niklas Söderlund wrote:
> When the driver runs in media controller mode it should not directly
> control the subdevice instead userspace will be responsible for
> configuring the pipeline. To be able to run in this mode a different set
> of
On Fri, Apr 28, 2017 at 12:41:56AM +0200, Niklas Söderlund wrote:
> When running in media controller mode a media pad is needed, register
> one.
>
> Signed-off-by: Niklas Söderlund
> ---
> drivers/media/platform/rcar-vin/rcar-core.c | 9 +
>
Hi Philipp,
Thankyou for the patch,
On 04/05/17 14:38, Philipp Zabel wrote:
> This driver can handle SoC internal and external video bus multiplexers,
> controlled by mux controllers provided by the mux controller framework,
> such as MMIO register bitfields or GPIOs. The subdevice passes
Hi Niklas,
On Fri, Apr 28, 2017 at 12:41:52AM +0200, Niklas Söderlund wrote:
> On Gen3 the CSI-2 routing is controlled by the VnCSI_IFMD register. One
> feature of this register is that it's only present in the VIN0 and VIN4
> instances. The register in VIN0 controls the routing for VIN0-3 and
Hi Niklas,
On Fri, Apr 28, 2017 at 12:41:48AM +0200, Niklas Söderlund wrote:
> Instead of caching the subdevice format each time the video device
> format is set read it directly when its needed. As it turns out the
> format is only needed when figuring out the max rectangle for cropping.
>
>
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 not stored e.g. in user space or the driver.
>
> Some sensors embed the EEPROM
Hi,
On Tue, May 02, 2017 at 01:25:48PM +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
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.
>
> Signed-off-by: Sakari Ailus
Hi,
On Thu, May 04, 2017 at 03:38:57PM +0200, Philipp Zabel wrote:
> This driver can handle SoC internal and external video bus multiplexers,
> controlled by mux controllers provided by the mux controller framework,
> such as MMIO register bitfields or GPIOs. The subdevice passes through
> the
Hi,
On Thu, May 04, 2017 at 03:38:56PM +0200, Philipp Zabel wrote:
> Add bindings documentation for the video multiplexer device.
>
> Signed-off-by: Sascha Hauer
> Signed-off-by: Philipp Zabel
> Signed-off-by: Steve Longerbeam
UNSUBSCRIBE linux-media@vger.kernel.org
On Thu, May 4, 2017 at 9:57 PM, Elizar Alcantara wrote:
> UNSUBSCRIBE
> linux-media@vger.kernel.org
>
>
>
>
>
> On Thu, May 4, 2017 at 9:43 PM, Philipp Zabel
> wrote:
>>
>> On Tue, 2017-04-25 at 14:56 +0300,
On Tue, 2017-04-25 at 14:56 +0300, Sakari Ailus wrote:
> Switch users of the v4l2_of_ APIs to the more generic v4l2_fwnode_ APIs.
> Async OF matching is replaced by fwnode matching and OF matching support
> is removed.
>
> Signed-off-by: Sakari Ailus
> Acked-by:
Add bindings documentation for the video multiplexer device.
Signed-off-by: Sascha Hauer
Signed-off-by: Philipp Zabel
Signed-off-by: Steve Longerbeam
Acked-by: Peter Rosin
Acked-by: Sakari Ailus
This driver can handle SoC internal and external video bus multiplexers,
controlled by mux controllers provided by the mux controller framework,
such as MMIO register bitfields or GPIOs. The subdevice passes through
the mbus configuration of the active input to the output side.
Signed-off-by:
Switch from the v4l2_of_ APIs to the v4l2_fwnode_ APIs so this driver
can work if the patch "v4l: Switch from V4L2 OF not V4L2 fwnode API"
is applied before it. Tested against
https://git.linuxtv.org/sailus/media_tree.git/log/?h=v4l2-acpi-merge
Signed-off-by: Philipp Zabel
Hi Niklas,
On Fri, Apr 28, 2017 at 12:36:58AM +0200, Niklas Söderlund wrote:
> A V4L2 driver for Renesas R-Car MIPI CSI-2 receiver. The driver
> supports the rcar-vin driver on R-Car Gen3 SoCs where separate CSI-2
> hardware blocks are connected between the video sources and the video
> grabbers
Good Day,
My wife and I have awarded you with a donation of $ 1,000,000.00 Dollars from
part of our Jackpot Lottery of 50 Million Dollars, respond with your details
for claims.
We await your earliest response and God Bless you.
Friedrich And Annand Mayrhofer.
---
This email has been checked
Hi Alexandru,
On Thursday 04 May 2017 13:53:33 agheorghe wrote:
> Add two new plane properties colorkey and colorkey_alpha for rcar gen3.
> * colorkey:
> - used for specifying the color on which the filtering is done.
> - bits 0 to 23 are interpreted as RGB888 format, in case we are
>
Em Thu, 4 May 2017 09:55:04 +0200
Gregor Jasny escreveu:
> Hello Mauro,
>
> On 04.05.17 00:33, Mauro Carvalho Chehab wrote:
> > Em Wed, 3 May 2017 09:53:03 -0300
> > Mauro Carvalho Chehab escreveu:
> >> Em Tue, 2 May 2017 22:30:29 +0200
> >>
On Thu, May 4, 2017 at 12:53 PM, agheorghe
wrote:
> --- a/include/media/vsp1.h
> +++ b/include/media/vsp1.h
> @@ -32,6 +32,9 @@ struct vsp1_du_atomic_config {
> struct v4l2_rect dst;
> unsigned int alpha;
> unsigned int zpos;
> + u32
On 05/04/2017 01:53 PM, agheorghe wrote:
The vsp2 hw supports changing of the alpha of pixels that match a color
key, this patch adds support for this feature in order to be used by
the rcar-du driver.
The colorkey is interpreted different depending of the pixel format:
* RGB - all
Currently, rcar-du supports colorkeying only for rcar-gen2 and it uses
some hw capability of the display unit(DU) which is not available on gen3.
In order to implement colorkeying for gen3 we need to use the colorkey
capability of the VSPD, hence the need to change both drivers rcar-du and
vsp1.
Add two new plane properties colorkey and colorkey_alpha for rcar gen3.
* colorkey:
- used for specifying the color on which the filtering is done.
- bits 0 to 23 are interpreted as RGB888 format, in case we are
dealing with an YCbCr format, only the Y componenet is
The vsp2 hw supports changing of the alpha of pixels that match a color
key, this patch adds support for this feature in order to be used by
the rcar-du driver.
The colorkey is interpreted different depending of the pixel format:
* RGB - all color components have to match.
*
On Thu, 2017-05-04 at 12:48 +0300, Sakari Ailus wrote:
> Hi Philipp,
>
> On Thu, May 04, 2017 at 11:26:18AM +0200, Philipp Zabel wrote:
> > Hi Sakari,
> >
> > On Thu, 2017-05-04 at 10:17 +0300, Sakari Ailus wrote:
> > > Hi Philipp,
> > >
> > > On Thu, May 04, 2017 at 09:07:32AM +0200, Philipp
Hi Philipp,
On Thu, May 04, 2017 at 11:26:18AM +0200, Philipp Zabel wrote:
> Hi Sakari,
>
> On Thu, 2017-05-04 at 10:17 +0300, Sakari Ailus wrote:
> > Hi Philipp,
> >
> > On Thu, May 04, 2017 at 09:07:32AM +0200, Philipp Zabel wrote:
> > > On Wed, 2017-05-03 at 22:28 +0300, Sakari Ailus wrote:
Hi Sakari,
On Thu, 2017-05-04 at 10:17 +0300, Sakari Ailus wrote:
> Hi Philipp,
>
> On Thu, May 04, 2017 at 09:07:32AM +0200, Philipp Zabel wrote:
> > On Wed, 2017-05-03 at 22:28 +0300, Sakari Ailus wrote:
> > > Hi Philipp,
> > >
> > > Thanks for continuing working on this!
> > >
> > > I have
On Thu, May 04, 2017 at 11:48:51AM +0300, Sakari Ailus wrote:
> On Wed, May 03, 2017 at 03:06:52PM -0700, Chiranjeevi Rapolu wrote:
> > Provides single source pad with up to 2576x1936 pixels at 10-bit raw
> > bayer format over MIPI CSI2 two lanes at 640Mbps/lane.
> > Supports up to 30fps at 5M
Hi Chiranjeevi,
Thanks for the patch.
On Wed, May 03, 2017 at 03:06:52PM -0700, Chiranjeevi Rapolu wrote:
> Provides single source pad with up to 2576x1936 pixels at 10-bit raw
> bayer format over MIPI CSI2 two lanes at 640Mbps/lane.
> Supports up to 30fps at 5M pixels, up to 60fps at 1080p.
>
Hello Mauro,
On 04.05.17 00:33, Mauro Carvalho Chehab wrote:
Em Wed, 3 May 2017 09:53:03 -0300
Mauro Carvalho Chehab escreveu:
Em Tue, 2 May 2017 22:30:29 +0200
Gregor Jasny escreveu:
I just used your patch and another to hopefully fix
Hi Hugues,
On 04/20/2017 06:07 PM, Hugues Fruchet wrote:
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
Hi Philipp,
On Thu, May 04, 2017 at 09:07:32AM +0200, Philipp Zabel wrote:
> On Wed, 2017-05-03 at 22:28 +0300, Sakari Ailus wrote:
> > Hi Philipp,
> >
> > Thanks for continuing working on this!
> >
> > I have some minor comments below...
>
> Thank you for the comments.
>
> [...]
> > Could
On Wed, 2017-05-03 at 22:28 +0300, Sakari Ailus wrote:
> Hi Philipp,
>
> Thanks for continuing working on this!
>
> I have some minor comments below...
Thank you for the comments.
[...]
> Could you rebase this on the V4L2 fwnode patchset here, please?
>
>
65 matches
Mail list logo