[PATCH] ARM: dts: r8a7794: link DU to VSPD

Add the "vsps" property to the DU device node in order to link this node to the (single) VSPD node. Signed-off-by: Sergei Shtylyov --- This patch is against the 'renesas-devel-20161220-v4.9' of Simon Horman's 'renesas.git' repo. It's only meaningful if the

[PATCH 2/2] drm: rcar-du: enable VSPD on R8A7794

We're going to use R8A7794 VSPD to control DU, so set the corresponding flag and the newly added field, 'num_vspds'... Signed-off-by: Sergei Shtylyov --- drivers/gpu/drm/rcar-du/rcar_du_drv.c |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)

[PATCH 1/2] drm: rcar-du: support less VSPs than CRTCs

Renesas R-Car E2 (R8A7791) SoC only has 1 VSPD but still 2 DU ports. Since we are going to use the R-Car gen2 VSPDs as the DU compositors, we'll have to also support this case. Now that the number of VSPDs can be less than the number of the DU ports, 'struct rcar_du_device_info' needs a new

[PATCH 0/2] Enable R8A7794 DU VSPD compositor

Hello. Here's the set of 2 patches against the 'drm-next' branch of David Airlie's 'linux.git' repo. We're switching to the DU compositor for the DU driver on the Renesas R8A7794 SoC. [1/2] drm: rcar-du: support less VSPs than CRTCs [2/2] drm: rcar-du: enable VSPD on R8A7794 MBR, Sergei

Re: [PATCH 1/1] [media] v4l: rcar_fdp1: use %4.4s to format a 4-byte string

Hi Nicolas, Thankyou for the patch This looks like a good catch, On 26/12/16 13:31, Nicolas Iooss wrote: > Using %4s to format f->fmt.pix_mp.pixelformat in fdp1_try_fmt() and > fdp1_s_fmt() may lead to more characters being printed (when the byte > following field pixelformat is not zero). > >