[PATCH 2/2] net: ethernet: renesas: ravb: use new api ethtool_{get|set}_link_ksettings

2016-08-19 Thread Philippe Reynes
The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/renesas/ravb_main.c | 16 +--- 1 files changed, 9 insertions(+), 7 deletions(-) diff --git a/drivers/net/ethernet/rene

[PATCH 1/2] net: ethernet: renesas: ravb: use phydev from struct net_device

2016-08-19 Thread Philippe Reynes
The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy_dev in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes --- drivers/net/etherne

[PATCH 2/2] ARM: dts: r8a7792: add VSP1V support

2016-08-19 Thread Sergei Shtylyov
Describe 3 instances (VSPS, VSPD0, and VSPD1) of the VSP1V in the R8A7792 device tree. Signed-off-by: Sergei Shtylyov --- arch/arm/boot/dts/r8a7792.dtsi | 24 1 file changed, 24 insertions(+) Index: renesas/arch/arm/boot/dts/r8a7792.dtsi

[PATCH 1/2] ARM: dts: r8a7792: add VSP1V clocks

2016-08-19 Thread Sergei Shtylyov
Describe the VSP1V clocks in the R8A7792 device tree. Signed-off-by: Sergei Shtylyov --- arch/arm/boot/dts/r8a7792.dtsi | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) Index: renesas/arch/arm/boot/dts/r8a7792.dtsi

[PATCH 0/2] Add R8A7792 VSP1V support

2016-08-19 Thread Sergei Shtylyov
Hello. Here's the set of 2 patches against Simon Horman's 'renesas.git' repo, 'renesas-devel-20160817-v4.8-rc2' tag. We're adding the R8A7792 VSP1V clocks and device nodes. The 2nd patch depends on the VSP1 driver patch in order for the VSP1V core to be recognized by the driver. The patches hav

[PATCH] vsp1: add R8A7792 VSP1V support

2016-08-19 Thread Sergei Shtylyov
Add support for the R8A7792 VSP1V cores which are different from the other gen2 VSP1 cores... Signed-off-by: Sergei Shtylyov --- This patch is against the 'media_tree.git' repo's 'master' branch. drivers/media/platform/vsp1/vsp1_drv.c | 20 drivers/media/platform/vsp1/

[PATCH] ARM: dts: blanche: add DU support

2016-08-19 Thread Sergei Shtylyov
Define the Blanche board dependent part of the DU device node. Add the device nodes for the Analog Devices ADV7511W HDMI transmitter (connected to DU0) and ADV7123 video DAC (connected to DU1). Add the necessary subnodes to interconnect DU, HDMI/VDAC devices, and HDMI/VGA connectors. Signed-o

[GIT PULL FOR renesas-drivers] IPMMU + DU

2016-08-19 Thread Laurent Pinchart
Hi Geert, This pull request contains the latest driver work for the IPMMU + DU targeting Gen3. Gen3 support as such isn't included as IPMMU is known to be broken on H3, but the driver should work on both Gen2 and Gen3. The following changes since commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:

Re: [PATCH 2/2] thermal: rcar-thermal: enable hwmon when thermal_zone

2016-08-19 Thread Zhang Rui
On 二, 2016-07-19 at 10:01 +, Kuninori Morimoto wrote: > From: Kuninori Morimoto > > rcar-thermal is supporting both thermal_zone_of_sensor_register() and > thermal_zone_device_register(). But thermal_zone_of_sensor_register() > doesn't enable hwmon as default. > This patch enables it to keep

Re: [PATCH v3 0/4] Initial r8a7796 PFC support

2016-08-19 Thread Geert Uytterhoeven
Hi Ulrich, On Thu, Aug 18, 2016 at 3:12 PM, Ulrich Hecht wrote: > This implements a minimal set of PFC functionality for the M3 and sits on > top of renesas-drivers-2016-08-09-v4.8-rc1. It includes the SCIF pin groups > and enables pin control for the serial console (SCIF2) on the Salvator-X > b

Re: [PATCH/HACK 5/7] [HACK] ARM: shmobile: r8a7790: Link the VSP1 and DU

2016-08-19 Thread Laurent Pinchart
Hi Geert, On Friday 19 Aug 2016 09:06:57 Geert Uytterhoeven wrote: > On Thu, Aug 18, 2016 at 6:03 PM, Laurent Pinchart wrote: > > In order to test VSP+DU integration for Gen3 on Gen2, link the VSPD > > instances to the DU and modify their features to match the Gen3 VSPD. > > Why do you modify the

Re: [PATCH 1/6] drm: Don't implement empty prepare_fb()/cleanup_fb()

2016-08-19 Thread Daniel Vetter
On Fri, Aug 19, 2016 at 11:39:29AM +0300, Laurent Pinchart wrote: > The plane .prepare_fb() and .cleanup_fb() helpers are optional, there's > no need to implement empty stubs, and no need to explicitly set the > function pointers to NULL either. > > Signed-off-by: Laurent Pinchart Rebased onto C

Re: [PATCH 3/6] v4l: rcar-fcp: Don't get/put module reference

2016-08-19 Thread Geert Uytterhoeven
On Fri, Aug 19, 2016 at 10:39 AM, Laurent Pinchart wrote: > Direct callers of the FCP API hold a reference to the FCP module due to > module linkage, there's no need to take another one manually. Take a > reference to the device instead to ensure that it won't disappear being ... behind > the ca

[PATCH 3/6] v4l: rcar-fcp: Don't get/put module reference

2016-08-19 Thread Laurent Pinchart
Direct callers of the FCP API hold a reference to the FCP module due to module linkage, there's no need to take another one manually. Take a reference to the device instead to ensure that it won't disappear being the caller's back. Signed-off-by: Laurent Pinchart --- drivers/media/platform/rcar-

[PATCH 2/6] drm: Unconstify state argument to prepare_fb()/cleanup_fb()

2016-08-19 Thread Laurent Pinchart
The functions might need to modify the state to store memory-related data. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 4 ++-- drivers/gpu/drm/i915/intel_display.c| 4 ++-- drivers/gpu/drm/i915/intel_drv.h| 4 ++-- drivers/gpu

[PATCH 5/6] v4l: vsp1: Add API to map and unmap DRM buffers through the VSP

2016-08-19 Thread Laurent Pinchart
The display buffers must be mapped for DMA through the device that performs memory access. Expose an API to map and unmap memory through the VSP device to be used by the DU. Signed-off-by: Laurent Pinchart --- drivers/media/platform/vsp1/vsp1_drm.c | 24 include/media/vs

[PATCH 1/6] drm: Don't implement empty prepare_fb()/cleanup_fb()

2016-08-19 Thread Laurent Pinchart
The plane .prepare_fb() and .cleanup_fb() helpers are optional, there's no need to implement empty stubs, and no need to explicitly set the function pointers to NULL either. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/arc/arcpgu_crtc.c | 2 -- drivers/gpu/drm/fsl-dcu/fsl_d

[PATCH 6/6] drm: rcar-du: Map memory through the VSP device

2016-08-19 Thread Laurent Pinchart
For planes handled by a VSP instance, map the framebuffer memory through the VSP to ensure proper IOMMU handling. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 74 --- drivers/gpu/drm/rcar-du/rcar_du_vsp.h | 2 + 2 files changed, 70

[PATCH 0/6] R-Car DU: Fix IOMMU operation when connected to VSP

2016-08-19 Thread Laurent Pinchart
Hello, This patch series fixes the rcar-du-drm driver to support VSP plane sources with an IOMMU. It is available for convenience at git://linuxtv.org/pinchartl/media.git iommu/devel/du On R-Car Gen3 the DU has no direct memory access but sources planes through VSP instances. When an IOM

[PATCH 4/6] v4l: rcar-fcp: Add an API to retrieve the FCP device

2016-08-19 Thread Laurent Pinchart
The new rcar_fcp_get_device() function retrieves the struct device related to the FCP device. This is useful to handle DMA mapping through the right device. Signed-off-by: Laurent Pinchart --- drivers/media/platform/rcar-fcp.c | 6 ++ include/media/rcar-fcp.h | 5 + 2 files chan

Re: [PATCH v3 4/4] arm64: dts: r8a7796: salvator: add serial console pins

2016-08-19 Thread Geert Uytterhoeven
On Thu, Aug 18, 2016 at 3:12 PM, Ulrich Hecht wrote: > Adds pin control for SCIF2. > > Signed-off-by: Ulrich Hecht Reviewed-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal

Re: [PATCH/HACK 5/7] [HACK] ARM: shmobile: r8a7790: Link the VSP1 and DU

2016-08-19 Thread Geert Uytterhoeven
Hi Laurent, On Thu, Aug 18, 2016 at 6:03 PM, Laurent Pinchart wrote: > In order to test VSP+DU integration for Gen3 on Gen2, link the VSPD > instances to the DU and modify their features to match the Gen3 VSPD. Why do you modify the feature properties? AFAIK the driver doesn't look at them anywa