Re: [PATCH] pcie-rcar: try setting PCIe speed to 5 GT/s at boot

2016-09-20 Thread Sergei Shtylyov
Hello. On 09/14/2016 11:54 PM, Bjorn Helgaas wrote: From: Grigory Kletsko Initially, the PCIe link speed is set up only at 2.5 GT/s. For better performance, we're trying to increase link speed to 5 GT/s. [Sergei Shtylyov: indented the macro definitions

[PATCH v2 1/3] ARM: dts: r7s72100: add mmcif to device tree

2016-09-20 Thread Chris Brandt
Signed-off-by: Chris Brandt --- v2: * added card detect as 3rd interupt source --- arch/arm/boot/dts/r7s72100.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi index e18d4e6..50f9f3b

[PATCH v2 2/3] mmc: sh_mmcif: Document r7s72100 DT bindings

2016-09-20 Thread Chris Brandt
Signed-off-by: Chris Brandt --- v2: * added interrupt description --- Documentation/devicetree/bindings/mmc/renesas,mmcif.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt

[PATCH v2 3/3] ARM: dts: rskrza1: add mmc DT support

2016-09-20 Thread Chris Brandt
Since the MMC and SDHI1 on the RSK share the same socket connector (CN1), you cannot enable MMC and SDHI1 at the same time. Therefore the status has been set to disabled because SDHI is more popular with this board. However, keeping this code in here serves as a good way to document how the MMC on

[PATCH v2 0/3] r7s72100: dts: enable mmcif

2016-09-20 Thread Chris Brandt
This series enables the mmc driver for the RZ/A1. Nothing needed to be changed with the actual sh_mmcif driver. It worked fine as-is. As you can see, the status in the rskrza1 dst was left as disabled because I wanted to leave that code in there for refernce for someone later that actually has a

Re: [PATCH/RFC] iommu/ipmmu-vmsa: Update ->add_device() return value

2016-09-20 Thread Magnus Damm
Hi Robin, Thanks for your feedback!! On Tue, Sep 20, 2016 at 10:18 PM, Robin Murphy wrote: > Hi Magnus, > > On 20/09/16 13:41, Magnus Damm wrote: >> From: Magnus Damm >> >> Update the IPMMU driver to return -ENODEV when adding devices >> not

Re: [PATCH/RFC v2 1/7] spi: Document DT bindings for SPI controllers in slave mode

2016-09-20 Thread Rob Herring
On Mon, Sep 12, 2016 at 10:50:40PM +0200, Geert Uytterhoeven wrote: > Signed-off-by: Geert Uytterhoeven > --- > v2: > - Do not create a child node in SPI slave mode. Instead, add an > "spi-slave" property, and put the mode properties in the controller > node. >

[PATCH v5 01/07] iommu/ipmmu-vmsa: Remove platform data handling

2016-09-20 Thread Magnus Damm
From: Magnus Damm The IPMMU driver is using DT these days, and platform data is no longer used by the driver. Remove unused code. Signed-off-by: Magnus Damm Reviewed-by: Laurent Pinchart --- Changes

[PATCH v5 04/07] iommu/ipmmu-vmsa: Break out domain allocation code

2016-09-20 Thread Magnus Damm
From: Magnus Damm Break out the domain allocation code into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm --- Changes since V4: - None Changes since V3: - None Changes since V2: -

[PATCH v5 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code

2016-09-20 Thread Magnus Damm
From: Magnus Damm Break out the utlb parsing code and dev_data allocation into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm --- Changes since V4: - Dropped hunk with fix to apply on top

[PATCH v5 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context

2016-09-20 Thread Magnus Damm
From: Magnus Damm Introduce a bitmap for context handing and convert the interrupt routine to handle all registered contexts. At this point the number of contexts are still limited. Also remove the use of the ARM specific mapping variable from ipmmu_irq() to allow

[PATCH v5 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V5

2016-09-20 Thread Magnus Damm
build on multiple architectures. In the process of doing so the interrupt code gets reworked and the foundation for supporting multiple contexts are added. Changes since V4: - Updated patch 3/7 to work on top on the following commit in next-20160920: b1e2afc iommu/ipmmu-vmsa: Fix wrong error

[PATCH v5 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency

2016-09-20 Thread Magnus Damm
From: Magnus Damm Neither the ARM page table code enabled by IOMMU_IO_PGTABLE_LPAE nor the IPMMU_VMSA driver actually depends on ARM_LPAE, so get rid of the dependency. Tested with ipmmu-vmsa on r8a7794 ALT and a kernel config using: # CONFIG_ARM_LPAE is not set

[PATCH v5 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

2016-09-20 Thread Magnus Damm
From: Magnus Damm Not all architectures have an iommu member in their archdata, so use #ifdefs support build wit COMPILE_TEST on any architecture. Signed-off-by: Magnus Damm --- Changes since V4: - None Changes since V3: - New patch

[PATCH v5 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops

2016-09-20 Thread Magnus Damm
From: Magnus Damm Introduce an alternative set of iommu_ops suitable for 64-bit ARM as well as 32-bit ARM when CONFIG_IOMMU_DMA=y. Also adjust the Kconfig to depend on ARM or IOMMU_DMA. Signed-off-by: Magnus Damm --- Changes since V4:

[renesas-drivers:topic/gen3-latest 12/52] drivers/gpu/drm/i915/intel_ddi.c:453:3: error: 'n_hdmi_entries' undeclared

2016-09-20 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git topic/gen3-latest head: c78265667b735cc07e53731abd2140d1bf4e7a41 commit: 8c26677f9f655eea278f4fc5395a3a0251db9c65 [12/52] Merge remote-tracking branch 'drm/drm-next' into renesas-drivers config:

Re: [PATCH/RFC] iommu/ipmmu-vmsa: Update ->add_device() return value

2016-09-20 Thread Robin Murphy
aviour described in the comment of > the add_iommu_group() function in iommu.c: > > /* > * We ignore -ENODEV errors for now, as they just mean that the > * device is not translated by an IOMMU. We still care about > * other errors and fail to initialize when they happen. > *

[PATCH/RFC] iommu/ipmmu-vmsa: Update ->add_device() return value

2016-09-20 Thread Magnus Damm
/* * We ignore -ENODEV errors for now, as they just mean that the * device is not translated by an IOMMU. We still care about * other errors and fail to initialize when they happen. */ Signed-off-by: Magnus Damm <damm+rene...@opensource.se> --- Applies to next-20160920 on top of:

[PATCH] arm64: dts: r8a7796: salvator-x: Populate EXTALR

2016-09-20 Thread Geert Uytterhoeven
It can be used for the watchdog. Based on similar work for r8a7795/salvator-x by Wolfram Sang. Signed-off-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts | 4 1 file changed, 4 insertions(+) diff --git

[PATCH/RFC] ARM: dts: r8a7790: IPMMU-DS SYS-DMAC prototype

2016-09-20 Thread Magnus Damm
From: Magnus Damm Hook up the SYS-DMAC devices to IPMMU-DS on r8a7790 and enable that particular IPMMU instance. Depending on kernel version LPAE may need to be enabled before the IPMMU driver becomes available. Useful to test the IPMMU with the devices hooked up to

[PATCH/RFC] ARM: dts: r8a7790: IPMMU-MX DU prototype

2016-09-20 Thread Magnus Damm
From: Magnus Damm These two hunks of code enable the r8a7790 IPMMU-MX instance together with the DU device on r8a7790. Depending on kernel version LPAE may need to be enabled before the IPMMU driver becomes available. Useful to test the IPMMU with the DU via the VGA

[PATCH/RFC] iommu/ipmmu-vmsa: IPMMU SYS-DMAC iova mapping workaround

2016-09-20 Thread Magnus Damm
From: Magnus Damm Here's some prototype code that works around the lack of software support for mapping I/O devices to the SYS-DMAC hardware via the DMA Engine framework when using IOMMU. The code itself is one big layering violation that goes through the DT and

Re: [PATCH v3 4/6] mmc: tmio: add eMMC support

2016-09-20 Thread Jaehoon Chung
On 09/20/2016 05:57 AM, Wolfram Sang wrote: > We need to add R1 without CRC support, refactor the bus width routine a > little and extend a quirk check. To support "non-removable;" we need a > workaround which will be hopefully removed when reworking PM soon. > > Signed-off-by: Wolfram Sang

Re: [PATCH v3 2/6] mmc: rtsx_pci: use new macro for R1 without CRC

2016-09-20 Thread Jaehoon Chung
Hi Wolfram, Add the commit message. On 09/20/2016 05:57 AM, Wolfram Sang wrote: > Signed-off-by: Wolfram Sang > --- > drivers/mmc/host/rtsx_pci_sdmmc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/mmc/host/rtsx_pci_sdmmc.c

Re: [PATCH v3 1/6] mmc: add define for R1 response without CRC

2016-09-20 Thread Jaehoon Chung
Hi Wolfram, On 09/20/2016 05:57 AM, Wolfram Sang wrote: > The core uses it for polling. Give drivers a proper define handle this > case like for other response types. > > Signed-off-by: Wolfram Sang > --- > include/linux/mmc/core.h | 3 +++ > 1 file changed, 3

Re: [PATCH 0/4] ARM: dts: rcar-gen2: Correct SCIFB reg properties to cover all

2016-09-20 Thread Simon Horman
On Mon, Sep 19, 2016 at 04:18:52PM +0200, Geert Uytterhoeven wrote: > Hi Simon, Magnus, > > Several SCIFB registers reside outside the register ranges as specified > by the "reg" properties of the various R-Car Gen2 DTSes. Fortunately > this works (on Linux), due to the PAGE_SIZE

Re: [PATCH 1/3] clk: shmobile: r8a7796: Add SCIF clocks

2016-09-20 Thread Geert Uytterhoeven
On Thu, Sep 15, 2016 at 8:30 PM, Geert Uytterhoeven wrote: > On Wed, Sep 14, 2016 at 6:46 PM, Ulrich Hecht > wrote: >> Signed-off-by: Ulrich Hecht > > Reviewed-by: Geert Uytterhoeven

Re: [PATCH 1/3] clk: renesas: r8a7796: Add SYS-DMAC clocks

2016-09-20 Thread Geert Uytterhoeven
On Thu, Sep 15, 2016 at 1:19 PM, Geert Uytterhoeven wrote: > On Wed, Sep 14, 2016 at 6:45 PM, Ulrich Hecht > wrote: >> Signed-off-by: Ulrich Hecht >> --- >> drivers/clk/renesas/r8a7796-cpg-mssr.c | 3 +++ >>

Re: [PATCH] [media] vsp1: fix CodingStyle violations on multi-line comments

2016-09-20 Thread Laurent Pinchart
Hi Mauro, On Monday 19 Sep 2016 16:10:31 Mauro Carvalho Chehab wrote: > Em Mon, 19 Sep 2016 21:35:36 +0300 Laurent Pinchart escreveu: > > On Monday 19 Sep 2016 15:26:19 Mauro Carvalho Chehab wrote: > >> Several multi-line comments added at the vsp1 patch series > >> violate the Kernel