On Tue, Jul 04, 2017 at 05:08:19PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > > Are there any news about the fwnode branch?
> > > > >
> > > > > I have quite usable camera, but it is still based on
> > > > > 982e8e40390d26430ef106fede41594139a4111c (that's v4.10). It would be
> > > > > good to
Fix checkpath errors
Signed-off-by: Ivan Menshykov
---
drivers/staging/media/atomisp/i2c/ov5693/ov5693.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/media/atomisp/i2c/ov5693/ov5693.c
[add linux-media list and Mauro Carvalho Chehab]
According to GregKH's suggestion [1], we tried to simply sort out the
FM driver source code which has been using in the internal projects.
Hopes it can help for fixing the problem raised in [1].
[1] https://lkml.org/lkml/2017/6/28/222
Chunyan
On 4 July 2017 at 18:51, Arnd Bergmann wrote:
> On Tue, Jul 4, 2017 at 12:15 PM, Chunyan Zhang
> wrote:
>> This patch added FM radio driver for Spreadtrum's SC2342, which's
>> a WCN SoC, also added a new directory for Spreadtrum's WCN SoCs.
>>
>>
On Wed, Jul 5, 2017 at 12:18 PM, Chunyan Zhang wrote:
> On 4 July 2017 at 18:51, Arnd Bergmann wrote:
>> On Tue, Jul 4, 2017 at 12:15 PM, Chunyan Zhang
> Like I mentioned, SC2342 includes many functions, this patch is only
> adding FM radio function included
Set media entity function to MEDIA_ENT_F_CAM_SENSOR.
Signed-off-by: Todor Tomov
---
drivers/media/i2c/ov5645.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/ov5645.c b/drivers/media/i2c/ov5645.c
index d1e844f..bb3dd0d 100644
---
Add suport for standard V4L2_CID_PIXEL_RATE control. The pixel clock
frequency value is specific for each sensor mode so the sensor mode
structure is extended to add this. The control is read-only and its
value is updated when the sensor mode is changed - on set_format.
Signed-off-by: Todor Tomov
Add suport for standard integer menu V4L2_CID_LINK_FREQ control.
The CSI2 link frequency value is specific for each sensor mode so the
sensor mode structure is extended to add this. The control is made
read-only and its value is updated when the sensor mode is changed -
on set_format.
On 07/05/2017 04:03 PM, Rob Herring wrote:
> On Mon, Jul 03, 2017 at 11:16:02AM +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
On Mon, Jul 03, 2017 at 11:16:02AM +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:
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.13-1
For:
- Addition of fwnode support at V4L2 core;
- Addition of a few more SDR formats;
- New imx driver to support i.MX6 cameras;
- New driver for Qualcon venus codecs;
- New I2C
On 29/06/2017 19:50, Sean Young wrote:
> The only thing that stands out is RC5_TIME_BASE. If that is the bit
> length or shortest pulse/space? In the latter case it should be 888 usec.
IR_RC5_DECODER_CLK_DIV
Length of 1 bit of the RC5 code in units of 27 MHz clks
Default value = 0xbb86 =>
Remove unnecessary static on local variable rtype.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
@bad
On Mon, Jul 03, 2017 at 11:27:32AM +0200, Marek Szyprowski wrote:
> The main question here if we want to merge incomplete solution or not. As
> for now, there is no support in ARM/ARM64 for NON_CONSISTENT attribute.
> Also none of the v4l2 drivers use it. Sadly support for NON_CONSISTENT
>
On Wed, Jun 28, 2017 at 10:58:44PM +0300, Sergei Shtylyov wrote:
> Add support for the image renderer light extended 3 (IMR-LX3) found only in
> the R-Car V2H (R8A7792) SoC. It's mostly the same as IMR-LSX3 but doesn't
> support video capture data as a source of 2D textures.
>
> Signed-off-by:
On Wed, Jul 05, 2017 at 11:44:49AM +0300, Todor Tomov wrote:
> @@ -1231,6 +1246,13 @@ static int ov5645_probe(struct i2c_client *client,
> _ctrl_ops,
> V4L2_CID_PIXEL_RATE,
>
Remove unnecessary static on local variable delt.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
@bad
On 07/04/2017 04:11 PM, Jose Abreu wrote:
> Document the bindings for the Synopsys Designware HDMI RX.
>
> Signed-off-by: Jose Abreu
> ---
> .../devicetree/bindings/media/snps,dw-hdmi-rx.txt | 70
> ++
> 1 file changed, 70 insertions(+)
> create
Hello!
On 07/03/2017 03:25 PM, Hans Verkuil 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
Remove unnecessary static on local variable t_params.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
@bad
Check that we do have a valid port in an endpoint, return an error if not.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/omap3isp/isp.c
Hi Pavel and others,
Most of these patches have been posted to the list in some form or other
already but a lot has happened since. Thus reposting. There are more
patches in my ccp2 branch but they're not quite ready as such, for the
reasons discussed previously.
Pavel Machek (1):
smiapp: add
From: Sakari Ailus
In the vast majority of cases the bus type is known to the driver(s)
since a receiver or transmitter can only support a single one. There
are cases however where different options are possible, or the bus type
cannot be automatically detected.
The
The CSI-2 phy driver did initialise mutexes in its init function but there
was no corresponding cleanup function destroying them. Fix that. Also
clean up ISP module initialisation a little.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.c
Document the CSI1/CCP2 property strobe. It signifies the clock or
strobe mode.
Signed-off-by: Sakari Ailus
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pavel Machek
Reviewed-By: Sebastian Reichel
From: Sakari Ailus
CCP2 and CSI-1, are older single data lane serial busses.
Signed-off-by: Sakari Ailus
Signed-off-by: Pavel Machek
---
drivers/media/platform/pxa_camera.c | 3 ++
From: Sakari Ailus
Just obtain it. It'll actually get used soon with CSI-1/CCP2.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-fwnode.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
The function to parse CSI2 bus parameters was called
v4l2_fwnode_endpoint_parse_csi_bus(), rename it as
v4l2_fwnode_endpoint_parse_csi2_bus() in anticipation of CSI1/CCP2
support.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-fwnode.c | 6 +++---
1
From: Pavel Machek
Add support for CCP2 connected SMIA sensors as found
on the Nokia N900.
Signed-off-by: Sebastian Reichel
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pavel Machek
Signed-off-by: Sakari Ailus
29 matches
Mail list logo