Hi Jacopo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16-rc2 next-20180220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Fixes: 42b7d5be5f1f ("media: i2c: ov772x: Support frame interval handling")
Signed-off-by: Fengguang Wu
---
ov772x.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/ov772x.c b/drivers/media/i2c/ov772x.c
index eba71d97..0d8ce2a 100644
--- a/drivers/media/i
Hi Jacopo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16-rc2 next-20180220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Hi Jacopo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.16-rc2 next-20180220]
[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 Wed, Feb 14, 2018 at 6:04 PM, Laurent Pinchart
wrote:
> The internal LVDS encoders now have their own DT bindings. Before
> switching the driver infrastructure to those new bindings, implement
> backward-compatibility through live DT patching.
>
> Patching is disabled and will be enabled along
Hi Hans,
Thanks for your feedback.
[snip]
> > >>> Can you then fix v4l2-compliance to stop testing colorspace
> > >>> against 0xff
> > >>> ?
> > >>
> > >> For now I can simply relax this test for subdevs with sources and sinks.
> > >
> > > You also need to relax it for video nodes with MC dri
On Mon, Feb 19, 2018 at 06:49:50PM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Feb 19, 2018 at 6:47 PM, Simon Horman wrote:
> > On Tue, Feb 20, 2018 at 12:02:58AM +0800, kbuild test robot wrote:
> >> tree: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
> >> soc-
On 02/19/2018 12:12 PM, Simon Horman wrote:
Add the initial device tree for the R8A77980 SoC based Condor board.
The board has 1 debug serial port (SCIF0); include support for it, so
that the serial console can work.
Based on the original (and large) patch by Vladimir Ba
Hi Jacopo,
Thank you for the patch.
On Monday, 19 February 2018 18:59:44 EET Jacopo Mondi wrote:
> The sensor driver sets mbus format colorspace information and sizes,
> but not ycbcr encoding, quantization and xfer function. When supplied
> with an badly initialized mbus frame format structure,
From: Takeshi Kihara
Add initial support for the Renesas Salvator-XS (Salvator-X 2nd version)
development board equipped with an R-Car M3-N SiP.
Most features are enabled through the shared salvator-xs.dtsi board
description. The memory configuration is specific to the M3-N SiP.
Signed-off-by:
From: Takeshi Kihara
Add initial support for the Renesas Salvator-XS (Salvator-X 2nd version)
development board equipped with an R-Car M3-N SiP.
Most features are enabled through the shared salvator-xs.dtsi board
description. The memory configuration is specific to the M3-N SiP.
Signed-off-by:
Hi Simon,
On Mon, Feb 19, 2018 at 6:47 PM, Simon Horman wrote:
> On Tue, Feb 20, 2018 at 12:02:58AM +0800, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
>> soc-for-v4.17
>> head: 8b49a80541c565d5d8482f15350ab861f60455a1
>> commit: 8b49a80
On Tue, Feb 20, 2018 at 12:02:58AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
> soc-for-v4.17
> head: 8b49a80541c565d5d8482f15350ab861f60455a1
> commit: 8b49a80541c565d5d8482f15350ab861f60455a1 [6/6] soc: renesas:
> rcar-sysc: add
Hello,
finally I addressed Laurent's comment on ov772x frame rate handling, which
I almost forgot about :)
Also, Sergei reported that the ceu node name should be generic, so I changed it
to "ceu: camera@e821".
All patches but the trivial [11/11] one are now reviewed/acked. Hope this is
las
Add renesas-ceu header file.
Do not remove the existing sh_mobile_ceu.h one as long as the original
driver does not go away.
Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
include/media/drv-intf/renesas-ceu.h | 26 ++
1 file change
Add bindings documentation for Renesas Capture Engine Unit (CEU).
Signed-off-by: Jacopo Mondi
Reviewed-by: Rob Herring
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
.../devicetree/bindings/media/renesas,ceu.txt | 81 ++
1 file changed, 81 insertions(+)
cre
Add driver for Renesas Capture Engine Unit (CEU).
The CEU interface supports capturing 'data' (YUV422) and 'images'
(NV[12|21|16|61]).
This driver aims to replace the soc_camera-based sh_mobile_ceu one.
Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ
platform GR-Peach.
T
Add Capture Engine Unit (CEU) node to device tree.
Signed-off-by: Jacopo Mondi
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Laurent Pinchart
Acked-by: Hans Verkuil
---
arch/arm/boot/dts/r7s72100.dtsi | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/arm
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Remove soc_camera framework dependencies from ov772x sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Change image format colorspace from JPEG to SRGB as the two use the
same colorspace information but JPEG makes assumpti
Add support to ov772x driver for frame intervals handling and enumeration.
Tested with 10MHz and 24MHz input clock at VGA and QVGA resolutions for
10, 15 and 30 frame per second rates.
Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
---
drivers/media/i2c/ov772x.c | 212 +++
Remove soc_camera framework dependencies from tw9910 sensor driver.
- Handle clock and gpios
- Register async subdevice
- Remove soc_camera specific g/s_mbus_config operations
- Add kernel doc to driver interface header file
- Adjust build system
This commit does not remove the original soc_camera
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
Acked-by: Laurent Pin
Migo-R platform uses sh_mobile_ceu camera driver, which is now being
replaced by a proper V4L2 camera driver named 'renesas-ceu'.
Move Migo-R platform to use the v4l2 renesas-ceu camera driver
interface and get rid of soc_camera defined components used to register
sensor drivers and of platform sp
The sensor driver sets mbus format colorspace information and sizes,
but not ycbcr encoding, quantization and xfer function. When supplied
with an badly initialized mbus frame format structure, those fields
need to be set explicitly not to leave them uninitialized. This is
tested by v4l2-compliance
From: Sergei Shtylyov
Date: Sun, 18 Feb 2018 18:21:05 +0300
> The *while* loop in this function can be turned into a normal *for* loop.
> And getting rid of the single return point saves us a few more LoCs...
>
> Signed-off-by: Sergei Shtylyov
Applied to net-next, thanks Sergei.
> The patc
tree: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
soc-for-v4.17
head: 8b49a80541c565d5d8482f15350ab861f60455a1
commit: 8b49a80541c565d5d8482f15350ab861f60455a1 [6/6] soc: renesas: rcar-sysc:
add R8A77980 support
config: i386-allmodconfig (attached as .config)
compiler: g
On Mon, Jan 29, 2018 at 07:21:19PM +0100, Simon Horman wrote:
> Describe frequencies, other than the default for CA53 cores. This is a
> pre-requisite for using providing alternative frequencies for use with
> CPUFreq with these cores.
>
> CPUFreq requires Z and Z2 clock support to function.
> Th
On Thu, Feb 08, 2018 at 07:05:53PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 02/08/2018 06:47 PM, Niklas Söderlund wrote:
>
> > Add the LVDS device to r8a77970.dtsi in a disabled state. Also connect
> > the it to the LVDS output of the DU. While at it align the endpoint name
> > of the du to
From: Magnus Damm
Add support for the on-board voltage regulator hooked up to GPIO3_20
on r8a7779 Marzen. The board schematics describes the regulator as U4
TPS2110A. Input wise, U4 has D0 fixed to ground, D1 tied to GPIO3_20
while IN1 is fixed to 3.3V and IN2 is fixed to 1.8V. OUT goes to the
pu
Here's V3 of prototype support for the r8a77965 Salvator-X.
This version is based on "renesas-drivers-2018-02-13-v4.16-rc1".
By up-porting this patch I am able to track which part of M3-N support
that yet to be merged in mainline. If all goes well then new versions of
this patch will reduce in si
From: Magnus Damm
Extend the Silk board support to include U14 which is an I2C based EEPROM
hooked up to the I2C1 bus.
Signed-off-by: Magnus Damm
---
arch/arm/boot/dts/r8a7794-silk.dts |6 ++
1 file changed, 6 insertions(+)
--- 0001/arch/arm/boot/dts/r8a7794-silk.dts
+++ work/arch/ar
ARM: dts: silk: Add EEPROM and GPIO keys
[PATCH 01/02] ARM: dts: silk: Add r1ex24002 EEPROM to DT
[PATCH 02/02] ARM: dts: silk: Add GPIO keys to DT
This series updates the DTS for the R-Car E2-based Silk board to support an
EEPROM connected via I2C and GPIO based tactile switches. Based on the Go
From: Magnus Damm
Extend the Silk board support to include SW3, SW4, SW6 and SW12. They
are all connected via GPIO lines and handled by the gpio-keys driver.
Signed-off-by: Magnus Damm
---
arch/arm/boot/dts/r8a7794-silk.dts | 55
1 file changed, 55 inser
On Sun, Feb 18, 2018 at 08:52:13PM -0600, Rob Herring wrote:
> On Wed, Feb 14, 2018 at 11:01:53AM +0100, Simon Horman wrote:
> > On Tue, Feb 13, 2018 at 10:45:48AM +0100, Jacopo Mondi wrote:
> > > Add device tree bindings documentation for Renesas R-Car M3-N (r8a77965)
> > > SoC.
> > >
> > > Signe
On Fri, Feb 16, 2018 at 09:25:30PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> Here's the set of 11 patches against Simon Horman's 'renesas.git' repo's
> 'renesas-devel-20180216-v4.16-rc1' tag. I'm adding the device tree support
> for the R8A77980-based Condor board (note that NFS root would only w
On Mon, Feb 19, 2018 at 11:34:41AM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 2/19/2018 11:30 AM, Geert Uytterhoeven wrote:
>
> > > Add the initial device tree for the R8A77980 SoC based Condor board.
> > > The board has 1 debug serial port (SCIF0); include support for it, so
> > > that the
On Mon, Feb 19, 2018 at 09:38:15AM +0100, Geert Uytterhoeven wrote:
> On Fri, Feb 16, 2018 at 9:09 PM, Sergei Shtylyov
> wrote:
> > According to the figure 9.2(b) of the R-Car Series, 3rd Generation User’s
> > Manual: Hardware Rev. 0.80 the A2IRn and A2SCn power areas in R8A77970 have
> > the A3IR
On Sat, Feb 17, 2018 at 03:06:41AM +0100, Marek Vasut wrote:
> Pull the complex condition in regulator_quirk_notify() into
> regulator_quirk_check(). Moreover, do not hard-code the I2C
> address, but rather use the one in da9xxx_msgs[].
>
> Signed-off-by: Marek Vasut
> Cc: Geert Uytterhoeven
> C
On Fri, Feb 16, 2018 at 03:26:08PM +0100, Ulrich Hecht wrote:
> Hi!
>
> Straight from the BSP, TMU pins for r8a7795{,-es1} and r8a7796. Magic
> numbers verified according to "pinfunction" document revisions 0.54 (M3-W)
> and 0.553 (H3).
Reviewed-by: Simon Horman
Hi Marek,
On Sat, Feb 17, 2018 at 12:46 PM, Marek Vasut wrote:
> On 02/17/2018 09:18 AM, Wolfram Sang wrote:
>>> -if ((client->addr == 0x58 && !strcmp(client->name, "da9063")) ||
>>> -(client->addr == 0x68 && !strcmp(client->name, "da9210")) ||
>>> -(client->addr == 0x70 && !s
On 02/19/2018 09:42 AM, Geert Uytterhoeven wrote:
> On Sat, Feb 17, 2018 at 3:06 AM, Marek Vasut wrote:
>> Porter needs the regulator quirk, just like the other boards,
>> the DA9063 and DA9210 IRQ line is connected to CPU IRQ2 . But
>> unlike the other boards, the DA9063 is at 0x5a on Porter.
>>
On Fri, Feb 16, 2018 at 03:25:39PM +0100, Ulrich Hecht wrote:
> Hi!
>
> Straight from the BSP, HDMI pins for r8a7795{,-es1} and r8a7796. Magic
> numbers verified according to "pinfunction" document revisions 0.54 (M3-W)
> and 0.553 (H3).
Reviewed-by: Simon Horman
On Sat, Feb 17, 2018 at 3:06 AM, Marek Vasut wrote:
> Porter needs the regulator quirk, just like the other boards,
> the DA9063 and DA9210 IRQ line is connected to CPU IRQ2 . But
> unlike the other boards, the DA9063 is at 0x5a on Porter.
>
> Signed-off-by: Marek Vasut
> Cc: Geert Uytterhoeven
On Fri, Feb 16, 2018 at 03:25:01PM +0100, Ulrich Hecht wrote:
> Hi!
>
> This series contains fixes to the PFC register definitions for r8a7795 and
> r8a7796 from the BSP that are not upstream yet.
> As far as I could tell, these changes check out with the Gen3 datasheet
> revision 0.80.
Agreed.
On Sun, Feb 18, 2018 at 4:21 PM, Sergei Shtylyov
wrote:
> The *while* loop in this function can be turned into a normal *for* loop.
> And getting rid of the single return point saves us a few more LoCs...
>
> Signed-off-by: Sergei Shtylyov
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
On Fri, Feb 16, 2018 at 9:09 PM, Sergei Shtylyov
wrote:
> According to the figure 9.2(b) of the R-Car Series, 3rd Generation User’s
> Manual: Hardware Rev. 0.80 the A2IRn and A2SCn power areas in R8A77970 have
> the A3IR area as a parent, thus the SYSC driver has those parents wrong...
>
> Fixes:
On Fri, Feb 16, 2018 at 7:32 PM, Sergei Shtylyov
wrote:
> Define the generic R8A77980 part of the EtherAVB device node.
>
> Based on the original (and large) patch by Vladimir Barinov.
>
> Signed-off-by: Vladimir Barinov
> Signed-off-by: Sergei Shtylyov
Reviewed-by: Geert Uytterhoeven
Gr{oetj
Hello!
On 2/19/2018 11:30 AM, Geert Uytterhoeven wrote:
Add the initial device tree for the R8A77980 SoC based Condor board.
The board has 1 debug serial port (SCIF0); include support for it, so
that the serial console can work.
Based on the original (and large) patch by Vladimir Barinov.
S
Hi Sergei,
On Fri, Feb 16, 2018 at 7:35 PM, Sergei Shtylyov
wrote:
> Add the initial device tree for the R8A77980 SoC based Condor board.
> The board has 1 debug serial port (SCIF0); include support for it, so
> that the serial console can work.
>
> Based on the original (and large) patch by Vl
Hi Arnd,
On Fri, Feb 16, 2018 at 4:27 PM, Arnd Bergmann wrote:
> When we build this driver with on x86-32, gcc produces a false-positive
> warning:
>
> drivers/clk/renesas/clk-sh73a0.c: In function 'sh73a0_cpg_clocks_init':
> drivers/clk/renesas/clk-sh73a0.c:155:10: error: 'parent_name' may be u
Hi,
> From: Ulrich Hecht, Sent: Thursday, February 15, 2018 9:02 PM
>
> When the TTY buffers fill up to the configured maximum, a system lockup
> occurs:
>
> [ 598.820128] INFO: rcu_preempt detected stalls on CPUs/tasks:
> [ 598.825796] 0-...!: (1 GPs behind) idle=5a6/2/0 softirq=1974/1974 fq
Hi Greg,
On Fri, Feb 16, 2018 at 7:44 PM, Greg KH wrote:
> On Thu, Feb 15, 2018 at 01:02:27PM +0100, Ulrich Hecht wrote:
>> When the TTY buffers fill up to the configured maximum, a system lockup
>> occurs:
>>
>> [ 598.820128] INFO: rcu_preempt detected stalls on CPUs/tasks:
>> [ 598.825796] 0
Hi Uli,
On Fri, Feb 16, 2018 at 3:27 PM, Ulrich Hecht
wrote:
> On Thu, Feb 15, 2018 at 2:12 PM, Wolfram Sang wrote:
>>> This can be prevented by doing a dummy read of the RX data register.
>>
>> Just so I understand the issue correctly: We are reading the register to
>> throw the content away to
54 matches
Mail list logo