While it's very common to use RPMSG for communicating with firmware
running on these remoteprocs there is no functional dependency on RPMSG.
As such RPMSG should be selected by the system integrator and not
automatically by the remoteproc drivers.
This does solve problems reported with circular Kc
Hi Nikolaus,
On Tue, Jun 27, 2017 at 07:46:51AM +0200, H. Nikolaus Schaller wrote:
> Hi,
>
> > Am 26.06.2017 um 22:12 schrieb Sakari Ailus :
> >
> > Hi Nikolaus,
> >
> > On Mon, Jun 26, 2017 at 07:54:19PM +0200, H. Nikolaus Schaller wrote:
> >> If a camera module driver specifies a format that
> Am 26.06.2017 um 13:16 schrieb Pavel Machek :
>
> Hi!
>
>>> You may want to try this one:
>>>
>>> commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
>>> Author: Pavel
>>> Date: Mon Feb 13 21:26:51 2017 +0100
>>>
>>> omap3isp: fix VP2SDR bit so capture (not preview) works
>>>
>>> This is
> Am 26.06.2017 um 22:04 schrieb Sylwester Nawrocki :
>
> On 06/26/2017 12:35 PM, Hugues FRUCHET wrote:
>>> What I am missing to support the GTA04 camera is the control of the
>>> optional "vana-supply".
>>> So the driver does not power up the camera module when needed and therefore
>>> probing
Hi,
> Am 26.06.2017 um 22:12 schrieb Sakari Ailus :
>
> Hi Nikolaus,
>
> On Mon, Jun 26, 2017 at 07:54:19PM +0200, H. Nikolaus Schaller wrote:
>> If a camera module driver specifies a format that is not
>> supported by omap3isp this ends in a NULL pointer
>> dereference instead of a simple fail.
Daniel Scheller writes:
> Am Mon, 26 Jun 2017 11:59:20 +0200
> schrieb Ralph Metzler :
>
> > Mauro Carvalho Chehab writes:
> > >
> > > Splitting it is OK. Including a *.c file no. It shouldn't be hard
> > > to
> > [...]
> > > change the makefile to:
> > > obj-ddbridge = dd
On Mon, Jun 26, 2017 at 07:46:34PM +0200, H. Nikolaus Schaller wrote:
> Hi,
>
> > Am 26.06.2017 um 18:31 schrieb Sakari Ailus :
> >
> > Hi Hugues,
> >
> > On Thu, Jun 22, 2017 at 05:05:38PM +0200, Hugues Fruchet wrote:
> >> @@ -1545,15 +1577,22 @@ static int ov965x_remove(struct i2c_client *clie
Hi Mauro,
(v2, this time with the appropriate git tags, plus rebased on current media
tree master. No other changes.)
This set includes converting the ov6650 driver to V4L2 sub-device driver
(from SoC camera).
Rebased w/o conflicts on more recent media tree master.
Please pull.
The following 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: Tue Jun 27 05:00:17 CEST 2017
media-tree git hash:2748e76ddb2967c4030171342ebdd3faa6a5e8e8
media_build gi
On 2017/06/26 10:24, Mauro Carvalho Chehab wrote:
> Em Sun, 25 Jun 2017 09:15:06 -0300
> Mauro Carvalho Chehab escreveu:
>
>> Em Fri, 23 Jun 2017 10:02:39 -0300
>> Mauro Carvalho Chehab escreveu:
>>
>>> Em Mon, 19 Jun 2017 16:56:13 +0900
>>> "Takiguchi, Yasunari" escreveu:
>>>
>> +stat
Remove useless variables wait_t and wait_sym and code related.
Also, fix some coding style issues.
Addresses-Coverity-ID: 1226947
Signed-off-by: Gustavo A. R. Silva
---
drivers/media/dvb-frontends/mb86a16.c | 25 +++--
1 file changed, 7 insertions(+), 18 deletions(-)
diff -
Hi there,
My name is Shaobo He and I am a graduate student at University of Utah.
I am using a static analysis tool to search for null pointer
dereferences and came across a couple of potentially invalid memory
accesses in the file drivers/media/v4l2-core/videobuf-core.c. Basically
the expans
Hi Nikolaus,
On Mon, Jun 26, 2017 at 07:54:19PM +0200, H. Nikolaus Schaller wrote:
> If a camera module driver specifies a format that is not
> supported by omap3isp this ends in a NULL pointer
> dereference instead of a simple fail.
Has this happened in practice? If it does, it is probably a dri
On 06/26/2017 12:35 PM, Hugues FRUCHET wrote:
>> What I am missing to support the GTA04 camera is the control of the optional
>> "vana-supply".
>> So the driver does not power up the camera module when needed and therefore
>> probing fails.
>>
>> - vana-supply: a regulator to power up the cam
Hi Sergei,
On Mon, Jun 26, 2017 at 9:56 PM, Sergei Shtylyov
wrote:
> On 06/26/2017 10:49 PM, Rob Herring wrote:
>>> From: Konstantin Kozhevnikov
>>>
>>> The image renderer, or the distortion correction engine, is a drawing
>>> processor with a simple instruction system capable of referencing vid
Hello!
On 06/26/2017 10:49 PM, Rob Herring wrote:
From: Konstantin Kozhevnikov
The image renderer, or the distortion correction engine, is a drawing
processor with a simple instruction system capable of referencing video
capture data or data in an external memory as the 2D texture data and
pe
On Fri, Jun 23, 2017 at 11:34:44PM +0300, Sergei Shtylyov wrote:
> From: Konstantin Kozhevnikov
>
> The image renderer, or the distortion correction engine, is a drawing
> processor with a simple instruction system capable of referencing video
> capture data or data in an external memory as the 2
On Fri, Jun 23, 2017 at 10:25:02AM +0100, Ramesh Shanmugasundaram wrote:
> Add r8a7796 DRIF bindings.
>
> Signed-off-by: Ramesh Shanmugasundaram
>
> ---
> Hi DT & Media maintainers, All,
>
>This patch adds DRIF bindings for R8A7796 SoC.
>It is based on media_tree - commit 76724b30f222
>
On Fri, Jun 23, 2017 at 12:25:33PM +0200, H. Nikolaus Schaller wrote:
> Hi Hugues,
>
> > Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
> >
> > From: "H. Nikolaus Schaller"
> >
> > This adds documentation of device tree bindings
> > for the OV965X family camera sensor module.
> >
> > Signed-o
On Thu, Jun 22, 2017 at 05:05:37PM +0200, Hugues Fruchet wrote:
> From: "H. Nikolaus Schaller"
>
> This adds documentation of device tree bindings
> for the OV965X family camera sensor module.
>
> Signed-off-by: H. Nikolaus Schaller
> Signed-off-by: Hugues Fruchet
> ---
> .../devicetree/bindi
Am Mon, 26 Jun 2017 11:45:08 +0200
schrieb Ralph Metzler :
> Mauro Carvalho Chehab writes:
>
> > Would it be possible to change things at the dddvb tree to make
> > it to use our coding style (for example, replacing CamelCase by the
> > kernel_style), in order to minimize the amount of work to
On R-Car H3 ES2.0, DU channels 0 and 3 are served by two separate
pipelines from the same VSP. Support this in the DU driver.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 2 +-
drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 3 ++
drivers/gpu/drm/rcar-du/rcar_du_kms.c
The display list headers are filled using information from the display
list only. Lower the display list manager spinlock contention by filling
the headers without holding the lock.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_dl.c | 6 --
1 file changed, 4 insertions
The R-Car H3 ES2.0 VSP-DL instance has two LIF entities and can drive
two display pipelines at the same time. Refactor the VSP DRM code to
support that by introducing a vsp_drm_pipeline object that models one
display pipeline.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_
The Blend/ROP Sub Unit (BRS) is a stripped-down version of the BRU found
in several VSP2 instances. Compared to a regular BRU, it supports two
inputs only, and thus has no ROP unit.
Add support for the BRS by modeling it as a new entity type, but reuse
the vsp1_bru object underneath. Chaining the
The H3 ES1.x exhibits dot clock duty cycle stability issues. We can work
around them by configuring the DPLL to twice the desired frequency,
coupled with a /2 post-divider. This isn't needed on other SoCs and
breaks HDMI output on M3-W for a currently unknown reason, so restrict
the workaround to H
The VSP supports both header and headerless display lists. The latter is
easier to use when the VSP feeds data directly to the DU in continuous
mode, and the driver thus uses headerless display lists for DU operation
and header display lists otherwise.
Headerless display lists are only available o
On Gen3 SoCs DPAD0 routing is configured through the last CRTC group,
unlike on Gen2 where it is configured through the first CRTC group. Fix
the driver accordingly.
Fixes: 2427b3037710 ("drm: rcar-du: Add R8A7795 device support")
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_
When the VSP1 is used in a DRM pipeline the driver doesn't register the
media device. Links between entities are not exposed to userspace, but
are still used internally for the sole purpose of setting up internal
source to sink pointers through the link setup handler.
Instead of going through this
The internal VSP entity source and sink pointers are stored as
media_entity pointers, which are then cast to a vsp1_entity. As all
sources and sinks are vsp1_entity instances, we can store the
vsp1_entity pointers directly.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_drm
New Gen3 SoCs come with two new VSP2 variants names VSP2-BS and VSP2-DL,
as well as a new VSP2-D variant on V3M and V3H SoCs. Add new entries for
them in the VSP device info table.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_drv.c | 24
drivers/
The VSP2-DL instance (present in the H3 ES2.0 and M3-N SoCs) has two LIF
instances. Adapt the driver infrastructure to support multiple LIFs.
Support for multiple display pipelines will be added separately.
The change to the entity routing table removes the ability to connect
the LIF output to the
When the display start interrupt occurs, we know that the hardware has
finished loading the active display list. The driver then proceeds to
recycle the list, assuming it won't be needed anymore.
This assumption holds true for headerless display lists, as the VSP
doesn't reload the list for the ne
The sink pointer is used to configure routing inside the VSP, and as
such must point to the next VSP entity in the pipeline. The WPF being a
pipeline terminal sink, its output route can't be configured. The
routing configuration code already handles this correctly without
referring to the sink poin
In the H3 ES2.0 SoC the VSP2-DL instance has two connections to DU
channels that need to be configured independently. Extend the VSP-DU API
with a pipeline index to identify which pipeline the caller wants to
operate on.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_vsp.c
2.0 Salvator-X: Enable DU support in DT"
patch series
For convenience, a branch merging this series with all dependencies is
available from
git://linuxtv.org/pinchartl/media.git drm/next/h3-es2/merged
with the DT and driver series split in two branches respectively tagged
drm-h3-es2-
smatch produce this warning:
drivers/media/v4l2-core/v4l2-fwnode.c:76
v4l2_fwnode_endpoint_parse_csi_bus() error: buffer overflow 'array' 5 <= u16max
That's because, in thesis, the routine might have called with
some value at bus->num_data_lanes. That's not the current
case.
Yet, better
If a camera module driver specifies a format that is not
supported by omap3isp this ends in a NULL pointer
dereference instead of a simple fail.
Signed-off-by: H. Nikolaus Schaller
---
drivers/media/platform/omap3isp/ispccdc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/
Hi,
> Am 26.06.2017 um 18:31 schrieb Sakari Ailus :
>
> Hi Hugues,
>
> On Thu, Jun 22, 2017 at 05:05:38PM +0200, Hugues Fruchet wrote:
>> @@ -1545,15 +1577,22 @@ static int ov965x_remove(struct i2c_client *client)
>> }
>>
>> static const struct i2c_device_id ov965x_id[] = {
>> -{ "OV9650",
Hi Mauro,
This set includes converting the ov6650 driver to V4L2 sub-device driver
(from SoC camera).
Rebased w/o conflicts on more recent media tree master.
Please pull.
The following changes since commit 430e29d9c0f65d9653a0b7f7a56f1c6cd374b84b:
media: dvb-frontends/stv0367: Improve DVB-C
Hi Sylwester,
On 25-06-2017 22:13, Sylwester Nawrocki wrote:
> Hi Jose,
>
> Thank you for addressing my review comments. Couple more suggestions below.
>
> On 06/20/2017 07:26 PM, Jose Abreu wrote:
>> This adds support for the Synopsys Designware HDMI RX PHY e405. This
>> phy receives and decodes
Hi Rob,
On 23-06-2017 22:58, Rob Herring wrote:
> On Tue, Jun 20, 2017 at 06:26:12PM +0100, Jose Abreu wrote:
>> Document the bindings for the Synopsys Designware HDMI RX.
>>
>> Signed-off-by: Jose Abreu
>> Cc: Carlos Palminha
>> Cc: Rob Herring
>> Cc: Mark Rutland
>> Cc: Mauro Carvalho Cheha
Hi Hugues,
On Thu, Jun 22, 2017 at 05:05:40PM +0200, Hugues Fruchet wrote:
> Align resolution sequences on initialization sequence using
> i2c_rv structure NULL terminated .This add flexibility
> on resolution sequence size.
> Document resolution related registers by using corresponding
> define i
Hi Hugues,
On Thu, Jun 22, 2017 at 05:05:38PM +0200, Hugues Fruchet wrote:
> @@ -1545,15 +1577,22 @@ static int ov965x_remove(struct i2c_client *client)
> }
>
> static const struct i2c_device_id ov965x_id[] = {
> - { "OV9650", 0 },
> - { "OV9652", 0 },
> + { "OV9650", 0x9650 },
> +
Hi Adam,
On Wed, Jun 21, 2017 at 04:34:41PM -0500, Adam Ford wrote:
> I have a Leopard Imaging LI-5M03 camera attached in 8-bit mode, and I
> am trying to capture an image on camera and stream it to the LCD
> (/dev/fb0) without using the DSP or proprietary codecs.
>
> I was hoping to do it with
[snip]
On Monday 26 Jun 2017 16:14:47 Kieran Bingham wrote:
> >> +int adv748x_txa_power(struct adv748x_state *state, bool on)
> >> +{
> >> +int val;
> >> +
> >> +val = txa_read(state, ADV748X_CSI_FS_AS_LS);
> >> +if (val < 0)
> >> +return val;
> >> +
> >> +/*
> >> + * T
Le lundi 26 juin 2017 à 22:51 +0800, Jacob Chen a écrit :
> Rockchip RGA is a separate 2D raster graphic acceleration unit. It
> accelerates 2D graphics operations, such as point/line drawing, image
> scaling, rotation, BitBLT, alpha blending and image blur/sharpness.
>
> The drvier is mostly base
Am Mon, 26 Jun 2017 06:19:20 -0300
schrieb Mauro Carvalho Chehab :
> Yes, config flags work, but please don't use a config flag like this:
>
> if (initflags & TDA18212_INIT_DDSTV)
>
> The flags should identify the required functionality, not if the
> caller is ddbridge driver. On a quick
Am Mon, 26 Jun 2017 10:55:34 +0200
schrieb Ralph Metzler :
> Daniel Scheller writes:
> > From: Daniel Scheller
> >
> > Original code at least has some signed/unsigned issues, resulting
> > in values like 32dBm.
>
> I will look into that.
>
> > Change signal strength readout to work with
2017-06-18 kbuild test robot :
> Hi Gustavo,
>
> [auto build test ERROR on linuxtv-media/master]
> [also build test ERROR on v4.12-rc5 next-20170616]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/
On 26/06/17 17:14, Kieran Bingham wrote:
> Hi Hans,
>
> Thankyou for your review, and apologies for the delay - I was OoO last week.
>
>
> On 19/06/17 10:13, Hans Verkuil wrote:
>> On 06/13/2017 02:35 AM, Kieran Bingham wrote:
>>> From: Kieran Bingham
>>>
>>> Provide support for the ADV7481 and
Resend since I received bad-mail-address bounces, sorry for any
duplicated email.
Am Mon, 26 Jun 2017 11:59:20 +0200
schrieb Ralph Metzler :
> Mauro Carvalho Chehab writes:
> >
> > Splitting it is OK. Including a *.c file no. It shouldn't be hard
> > to
> [...]
> > change the makefile to:
>
Hi Nicolas,
2017-06-16 Nicolas Dufresne :
> Le vendredi 16 juin 2017 à 16:39 +0900, Gustavo Padovan a écrit :
> > > From: Gustavo Padovan
> >
> > For explicit synchronization (and soon for HAL3/Request API) we need
> > the v4l2-driver to guarantee the ordering which the buffer were queued
> > b
Hi Hans,
Thankyou for your review, and apologies for the delay - I was OoO last week.
On 19/06/17 10:13, Hans Verkuil wrote:
> On 06/13/2017 02:35 AM, Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Provide support for the ADV7481 and ADV7482.
>>
>> The driver is modelled with 4 subdevices
Rockchip RGA is a separate 2D raster graphic acceleration unit. It
accelerates 2D graphics operations, such as point/line drawing, image
scaling, rotation, BitBLT, alpha blending and image blur/sharpness.
The drvier is mostly based on s5p-g2d v4l2 m2m driver.
And supports various operations from t
Hi Tomasz,
A few more comments, better late than never I guess.
On Mon, Jun 12, 2017 at 06:59:18PM +0900, Tomasz Figa wrote:
...
> > +/*
> > + * The CSI2 receiver has several parameters affecting
> > + * the receiver timings. These depend on the MIPI bus frequency
> > + * F in Hz (sensor transmit
This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering based
2d graphics acceleration module.
Before, my colleague yakir have write a drm RGA drvier and send it to the lists.
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-March/416769.html
I have been asked to find
On 06/26/2017 12:07 PM, Hans Verkuil wrote:
> On 26/06/17 11:53, Hugues FRUCHET wrote:
>> Hi Hans, thanks for review.
>>
>> Reply below.
>>
>> BR
>> Hugues.
>>
>> On 06/22/2017 05:19 PM, Hans Verkuil wrote:
>>> On 06/22/2017 05:12 PM, Hugues Fruchet wrote:
Add flexibility on supported resolu
Nikolaus,
some comments about pixel format/resolution below:
On 06/26/2017 10:39 AM, Pavel Machek wrote:
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no image :(
>>
As reported by this warning:
drivers/media/usb/pvrusb2/pvrusb2-encoder.c:263 pvr2_encoder_cmd()
warn: continue to end of do { ... } while(0); loop
There's an issue at the retry logic there: the current logic is:
do {
if (need_to_retry)
cont
Get rid of those two warnings:
drivers/media/platform/davinci/vpif_capture.c: In function 'vpif_remove':
drivers/media/platform/davinci/vpif_capture.c:1722:21: warning: variable
'common' set but not used [-Wunused-but-set-variable]
struct common_obj *common;
^~
drivers/m
As warned by gcc:
drivers/media/v4l2-core/v4l2-fwnode.c:76
v4l2_fwnode_endpoint_parse_csi_bus() error: buffer overflow 'array' 5 <= u16max
That's because, in thesis, the routine might have called with
some value at bus->num_data_lanes.
While this doesn't happen, in practice, some code ch
As warned by gcc:
drivers/media/v4l2-core/v4l2-fwnode.c:76
v4l2_fwnode_endpoint_parse_csi_bus() error: buffer overflow 'array' 5 <= u16max
That's because, in thesis, the routine might have called with
some value at bus->num_data_lanes.
While this doesn't happen, in practice, some code ch
On 06/26/2017 08:03 AM, H. Nikolaus Schaller wrote:
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> Add a first support of OV9655 variant.
>> Because of register set slightly different from OV9650/9652,
>> not all of the driver features are supported (controls).
>> Supported resolutio
On 16/06/17 21:45, Janusz Krzysztofik wrote:
> Remove the soc_camera dependencies and move the diver to i2c
>
> Lost features, fortunately not used or not critical on test platform:
> - soc_camera power on/off callback - replaced with clock enable/disable
> only, no support for platform provided
Hi!
> > You may want to try this one:
> >
> > commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
> > Author: Pavel
> > Date: Mon Feb 13 21:26:51 2017 +0100
> >
> >omap3isp: fix VP2SDR bit so capture (not preview) works
> >
> >This is neccessary for capture (not preview) to work properly
Tomi,
* Tomi Valkeinen [170428 04:15]:
> On 14/04/17 13:25, Hans Verkuil wrote:
> > From: Hans Verkuil
> >
> > The CEC pin was always pulled up, making it impossible to use it.
...
> Tony, can you queue this? It's safe to apply separately from the rest of
> the HDMI CEC work.
So the dts chang
Thanks Rob,
Comments addressed, and a new version 6 to be posted soon.
On 22/06/17 22:34, Rob Herring wrote:
> On Wed, Jun 14, 2017 at 08:58:12PM +0100, Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Provide support for the ADV7481 and ADV7482.
>>
>> The driver is modelled with 4 subdevices
Em Mon, 26 Jun 2017 11:45:08 +0200
Ralph Metzler escreveu:
> Mauro Carvalho Chehab writes:
> > Em Thu, 22 Jun 2017 23:35:27 +0200
> > Ralph Metzler escreveu:
> >
> > > Daniel Scheller writes:
> > > > Am Tue, 20 Jun 2017 16:10:43 -0300
> > > > schrieb Mauro Carvalho Chehab :
> > >
On 06/23/2017 12:25 PM, H. Nikolaus Schaller wrote:
> Hi Hugues,
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> From: "H. Nikolaus Schaller"
>>
>> This adds documentation of device tree bindings
>> for the OV965X family camera sensor module.
>>
>> Signed-off-by: H. Nikolaus Schaller
Mauro Carvalho Chehab writes:
> Em Mon, 26 Jun 2017 10:55:34 +0200
> Ralph Metzler escreveu:
>
> > Daniel Scheller writes:
> > > From: Daniel Scheller
> > >
> > > Original code at least has some signed/unsigned issues, resulting in
> > > values like 32dBm.
> >
> > I will look i
Em Mon, 26 Jun 2017 11:59:20 +0200
Ralph Metzler escreveu:
> Mauro Carvalho Chehab writes:
> > Em Sun, 25 Jun 2017 19:52:59 +0200
> > Daniel Scheller escreveu:
> >
> > > Am Sat, 24 Jun 2017 13:50:01 -0300
> > > schrieb Mauro Carvalho Chehab :
> > >
> > > > Em Thu, 22 Jun 2017 23:35:
On 26/06/17 11:53, Hugues FRUCHET wrote:
> Hi Hans, thanks for review.
>
> Reply below.
>
> BR
> Hugues.
>
> On 06/22/2017 05:19 PM, Hans Verkuil wrote:
>> On 06/22/2017 05:12 PM, Hugues Fruchet wrote:
>>> Add flexibility on supported resolutions by cropping sensor
>>> image to fit user resoluti
Hi Nikolaus,
On 06/22/2017 05:41 PM, H. Nikolaus Schaller wrote:
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>> plugged on connector P1 of STM32F746G-DISCO board.
Em Mon, 26 Jun 2017 10:55:34 +0200
Ralph Metzler escreveu:
> Daniel Scheller writes:
> > From: Daniel Scheller
> >
> > Original code at least has some signed/unsigned issues, resulting in
> > values like 32dBm.
>
> I will look into that.
>
> > Change signal strength readout to work wit
Ok course, thanks Julia.
On 06/25/2017 10:00 PM, Julia Lawall wrote:
> Braces are probably missing aroud lines 1618-1620.
>
> julia
>
> -- Forwarded message --
> Date: Sun, 25 Jun 2017 23:06:03 +0800
> From: kbuild test robot
> To: kbu...@01.org
> Cc: Julia Lawall
> Subject: Re
Mauro Carvalho Chehab writes:
> Em Sun, 25 Jun 2017 19:52:59 +0200
> Daniel Scheller escreveu:
>
> > Am Sat, 24 Jun 2017 13:50:01 -0300
> > schrieb Mauro Carvalho Chehab :
> >
> > > Em Thu, 22 Jun 2017 23:35:27 +0200
> > > Ralph Metzler escreveu:
> > >
> > > Would it be possible to c
Hi Pavel,
> Am 26.06.2017 um 10:39 schrieb Pavel Machek :
>
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no image :(
The latter is likely a setup issue of
Hi Hans, thanks for review.
Reply below.
BR
Hugues.
On 06/22/2017 05:19 PM, Hans Verkuil wrote:
> On 06/22/2017 05:12 PM, Hugues Fruchet wrote:
>> Add flexibility on supported resolutions by cropping sensor
>> image to fit user resolution format request.
>>
>> Signed-off-by: Hugues Fruchet
>> -
Mauro Carvalho Chehab writes:
> Em Thu, 22 Jun 2017 23:35:27 +0200
> Ralph Metzler escreveu:
>
> > Daniel Scheller writes:
> > > Am Tue, 20 Jun 2017 16:10:43 -0300
> > > schrieb Mauro Carvalho Chehab :
> > > ...
> > > > > - Maybe for 4.14: Support for the CineS2 V7 and FlexV4 line o
On 26/06/17 11:26, Sakari Ailus wrote:
> VIDIOC_S_FMT may return EBUSY if the device is streaming or there are
> buffers allocated. Document this.
>
> Signed-off-by: Sakari Ailus
Acked-by: Hans Verkuil
Can you also add this to S_STD, S_INPUT, S_OUTPUT and S_CROP?
And update the EBUSY descript
VIDIOC_S_FMT may return EBUSY if the device is streaming or there are
buffers allocated. Document this.
Signed-off-by: Sakari Ailus
---
Documentation/media/uapi/v4l/vidioc-g-fmt.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/media/uapi/v4l/vidioc-g-fmt.rst
b/Documen
Hi all,
In case someone wants to play with the driver I've pushed a git tree at
[1] which contains few patches on top of the driver. Those patches are
on upstreaming phase but doesn't merged yet.
[1] https://github.com/svarbanov/linux/tree/master-venus-v11
On 06/15/2017 07:31 PM, Stanimir Varban
Em Sun, 25 Jun 2017 19:52:59 +0200
Daniel Scheller escreveu:
> Am Sat, 24 Jun 2017 13:50:01 -0300
> schrieb Mauro Carvalho Chehab :
>
> > Em Thu, 22 Jun 2017 23:35:27 +0200
> > Ralph Metzler escreveu:
> >
> > Would it be possible to change things at the dddvb tree to make
> > it to use our cod
Daniel Scheller writes:
> From: Daniel Scheller
>
> Original code at least has some signed/unsigned issues, resulting in
> values like 32dBm.
I will look into that.
> Change signal strength readout to work without asking
> the attached tuner, and use a lookup table instead of log calc. V
On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
> Hi Pavel,
>
> > Am 25.06.2017 um 11:18 schrieb Pavel Machek :
> >
> > Hi!
> >
> >> * unfortunately we still get no image :(
> >>
> >> The latter is likely a setup issue of our camera interface (OMAP3 ISP =
> >> Image Signal Processor) w
On Fri, Jun 23, 2017 at 11:25 AM, Ramesh Shanmugasundaram
wrote:
> Add r8a7796 DRIF bindings.
>
> Signed-off-by: Ramesh Shanmugasundaram
>
Acked-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-
87 matches
Mail list logo
