[PATCH 1/2] sh_eth: get rid of 'sh_eth_cpu_data::shift_rd0'

After checking all the available manuals, I have enough information to conclude that the 'shift_rd0' flag is only relevant for the Ether cores supporting so called "intelligent checksum" (and hence having CSMR) which is indicated by the 'hw_crc' flag. Since all the relevant SoCs now have

[PATCH 2/2] sh_eth: rename 'sh_eth_cpu_data::hw_crc'

The 'struct sh_eth_cpu_data' field indicating the "intelligent checksum" support was misnamed 'hw_crc' -- rename it to 'hw_checksum'. Signed-off-by: Sergei Shtylyov --- drivers/net/ethernet/renesas/sh_eth.c | 12 ++--

[PATCH 0/2] sh_eth: "intgelligent checksum" related cleanups

Hello. Here's a set of 2 patches against DaveM's 'net.git' repo, as they are based on a couple patches merged there recently; however, the patches are destined for 'net-next.git' (once 'net.git' gets merged there next time). I'm cleaning up the "intelligent checksum" related code (however, the

Re: [PATCH] sh_eth: R8A7740 supports packet shecksumming

From: Sergei Shtylyov Date: Thu, 5 Jan 2017 12:33:21 +0300 >Oops, typo in the subject, "shecksumming". David, should I resend? I accidently pushed this out without fixing the typo, sorry about that but that's going to be how it is I'm afraid :-)

Re: [PATCH] sh_eth: R8A7740 supports packet shecksumming

From: Sergei Shtylyov Date: Thu, 05 Jan 2017 00:29:32 +0300 > The R8A7740 GEther controller supports the packet checksum offloading > but the 'hw_crc' (bad name, I'll fix it) flag isn't set in the R8A7740 > data, thus CSMR isn't cleared... > > Fixes:

Re: [PATCH] sh_eth: fix EESIPR values for SH77{34|63}

From: Sergei Shtylyov Date: Wed, 04 Jan 2017 22:18:24 +0300 > As the SH77{34|63} manuals are freely available, I've checked the EESIPR > values written against the manuals, and they appeared to set the reserved > bits 11-15 (which should be 0 on write). Fix

Re: [PATCH/RFC v2 net-next] ravb: unmap descriptors when freeing rings

Hello! On 01/05/2017 01:43 PM, Simon Horman wrote: From: Kazuya Mizuguchi "swiotlb buffer is full" errors occur after repeated initialisation of a device - f.e. suspend/resume or ip link set up/down. This is because memory mapped using dma_map_single() in

[PATCH] arm64: do not set dma masks that device connection can't handle

It is possible that device is capable of 64-bit DMA addresses, and device driver tries to set wide DMA mask, but bridge or bus used to connect device to the system can't handle wide addresses. With swiotlb, memory above 4G still can be used by drivers for streaming DMA, but *dev->mask and

Re: [PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Jose, On Friday 06 Jan 2017 10:07:03 Jose Abreu wrote: > Hi Laurent, > > Sorry for the delayed answer but I am quite busy at the moment. No worries, your help is really appreciated. > On 06-01-2017 01:48, Laurent Pinchart wrote: > > [snip] > > The TX_READY signal is documented in the

Re: About VSPD

Hello Jithin, On Friday 06 Jan 2017 07:15:27 Jithin T Raj wrote: > hello Laurent and all, > > Can anybody give me an insight to VSPD .Recently I am going through > the term VSPD..Is it associated with Display Unit ? ..It will be a help if > someone share some links about VSPD..I am a beginner in

[PATCH] arm64: do not set dma masks that device connection can't handle

It is possible that device is capable of 64-bit DMA addresses, and device driver tries to set wide DMA mask, but bridge or bus used to connect device to the system can't handle wide addresses. With swiotlb, memory above 4G still can be used by drivers for streaming DMA, but *dev->mask and

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

>>> Just a guess, but if the inbound translation windows in the host >>> bridge are wider than 32-bit, the reason for setting up a single >>> 32-bit window is probably because that is what the parent bus supports. I've re-checked rcar-pcie hardware documentation. It indeed mentions that AXI bus

Re: [PATCH 1/2] serial: sh-sci: Fix early deassertion of dedicated RTS

Hi Geert, Thank you for the patch. On Friday 02 Dec 2016 13:35:10 Geert Uytterhoeven wrote: > If a UART has dedicated RTS/CTS pins, there are some issues: > > 1. When changing hardware control flow, the new AUTORTS state is not >immediately reflected in the hardware, but only when RTS is

Re: [PATCH 2/2] serial: sh-sci: Fix hang in sci_reset()

Hi Geert, Thank you for the patch. On Friday 02 Dec 2016 13:35:11 Geert Uytterhoeven wrote: > When the .set_termios() callback resets the UART, it first waits until > all characters in the transmit FIFO have been transmitted, to prevent a > port configuration change from impacting these

[PATCH v1.1 19/19] serial: sh-sci: Compute the regshift value for SCI ports

SCI instances found in SH SoCs have different spacing between registers depending on the SoC. The platform data contains a regshift field that tells the driver by how many bits to shift the register offset to compute its address. We can compute the regshift value automatically based on the memory

[PATCH v4 3/4] v4l: vsp1: Repair suspend resume operations for video pipelines

When a suspend/resume action is taken, the pipeline is reset and never reconfigured. To correct this, we establish a new flag pipe->configured and utilise this to establish when we write a full configuration set to the current display list. Signed-off-by: Kieran Bingham

[PATCH v4 1/4] v4l: vsp1: Prevent multiple streamon race commencing pipeline early

With multiple inputs through the BRU it is feasible for the streams to race each other at stream-on. Multiple VIDIOC_STREAMON calls racing each other could have process N-1 skipping over the pipeline setup section and then start the pipeline early, if videobuf2 has already enqueued buffers to the

[PATCH v4 2/4] v4l: vsp1: Move vsp1_video_setup_pipeline()

Move the static vsp1_video_setup_pipeline() function in preparation for the callee updates so that the vsp1_video_pipeline_run() call can configure pipelines following suspend resume actions. This commit is just a code move for clarity performing no functional change. Signed-off-by: Kieran

[PATCH v4 4/4] v4l: vsp1: Remove redundant pipe->dl usage from drm

The pipe->dl is used only inside vsp1_du_atomic_flush(), and can be obtained and stored locally to simplify the code. Signed-off-by: Kieran Bingham --- drivers/media/platform/vsp1/vsp1_drm.c | 20 ++--

[PATCH v4 0/4] v4l: vsp1: Fix suspend/resume and race on M2M pipelines

This small patchset helps rework the VSP1 driver to repair an issue on suspend/resume operations whereby the pipeline does not get reconfigured after it has been re-initialised following a resume operation. Along side this, there was an intrinsic race in the vsp1_video_start_streaming() function

[PATCH v1.1 08/19] serial: sh-sci: Fix register offsets for the IRDA serial port

Even though most of its registers are 8-bit wide, the IRDA has two 16-bit registers that make it a 16-bit peripheral and not a 8-bit peripheral with addresses shifted by one. Fix the registers offset in the driver and the platform data regshift value. Signed-off-by: Laurent Pinchart

[PATCH 1/4] ARM: shmobile: defconfig: Enable CONFIG_VIDEO_ADV7604

From: Niklas Söderlund The adv7612 is used on Gen2 boards (Lager, Koelsch and Gose) for HDMI input. Enable support for this chip in shmobile_defconfig. Signed-off-by: Niklas Söderlund Signed-off-by: Simon Horman

[PATCH 14/16] arm64: dts: r8a7796: salvator-x: Enable EthernetAVB

From: Laurent Pinchart Signed-off-by: Laurent Pinchart [geert: Add pinctrl] Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman ---

[PATCH 3/4] ARM: shmobile: defconfig: Enable r8a774[35] SoCs

Enable recently added r8a7743 (RZ/G1M) and r8a7745 (RZ/G1E) SoCs. Signed-off-by: Simon Horman Acked-by: Geert Uytterhoeven --- arch/arm/configs/shmobile_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 16/16] arm64: dts: r8a7795: Add PWM support

From: Laurent Pinchart Add the 7 PWM channels to the r8a7795 device tree, in the disabled state. Signed-off-by: Laurent Pinchart Reviewed-by: Geert Uytterhoeven Signed-off-by: Simon

[PATCH 15/16] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for msiof nodes

Use recently added R-Car Gen 3 fallback binding for msiof nodes in DT for r8a7796 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7796 and the fallback binding for R-Car Gen 3. Signed-off-by: Simon Horman

[PATCH 03/16] arm64: dts: r8a7796: Add CAN support

From: Chris Paterson Adds CAN controller nodes for r8a7796. Based on a patch for r8a7795 by Ramesh Shanmugasundaram. Signed-off-by: Chris Paterson Reviewed-by: Geert Uytterhoeven Acked-by: Marc Kleine-Budde

[GIT PULL] Renesas ARM Based SoC DT Updates for v4.11

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC DT updates for v4.11. The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) are available in the git repository at:

[PATCH 04/16] arm64: dts: r8a7796: Add CAN FD support

From: Chris Paterson Adds CAN FD controller node for r8a7796. Based on a patch for r8a7795 by Ramesh Shanmugasundaram. Signed-off-by: Chris Paterson Reviewed-by: Geert Uytterhoeven Acked-by: Marc Kleine-Budde

[PATCH 11/16] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for i2c nodes

Use recently added R-Car Gen 3 fallback binding for i2c nodes in DT for r8a7796 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7796 and the fallback binding for R-Car Gen 3. Signed-off-by: Simon Horman

[PATCH 09/16] arm64: dts: r8a7795: Use Gen 3 fallback compat string for PCIE

Use recently added en 3 fallback compat string for PCIE in r8a7795 DT. Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff

[PATCH 13/16] arm64: dts: renesas: r8a7796: Add EthernetAVB instance

From: Laurent Pinchart Signed-off-by: Laurent Pinchart Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman ---

[PATCH 05/16] arm64: renesas: r8a7796/salvator-x: Add board part number to DT bindings

From: Geert Uytterhoeven Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman --- Documentation/devicetree/bindings/arm/shmobile.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 06/16] arm64: dts: r8a7795: Use renesas,rcar-gen3-usb2-phy fallback binding

A fallback binding for the Renesas R-Car Gen3 for USB2.0 PHY driver was added by commit cde7bc367f09 ("phy: rcar-gen3-usb2: add fallback binding"). This patch makes use of this binding in the DT for the r8a7795 SoC. Signed-off-by: Simon Horman Reviewed-by: Geert

[PATCH 2/4] ARM: shmobile: defconfig: Enable CMA for DMA

From: Niklas Söderlund To be able to use VIN with larger frame sizes CMA memory are needed for DMA. If this is not enabled trying to capture large frames can result in errors such as: rcar-vin e6ef.video: dma_alloc_coherent of size 8388608 failed A

[PATCH 4/4] ARM: multi_v7_defconfig: Enable r8a774[35] SoCs

Enable recently added r8a7743 (RZ/G1M) and r8a7745 (RZ/G1E) SoCs. Signed-off-by: Simon Horman Acked-by: Geert Uytterhoeven --- arch/arm/configs/multi_v7_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 07/16] arm64: dts: r8a7795: add sound CTU support

From: Kuninori Morimoto This patch adds CTU (= Channel Transfer Unit) support which is needed to sound mixing. Signed-off-by: Kuninori Morimoto Signed-off-by: Simon Horman ---

[PATCH 08/16] arm64: dts: r8a7795: add sound MIX support

From: Kuninori Morimoto This patch adds MIX (= Mixer) support. Signed-off-by: Kuninori Morimoto Signed-off-by: Simon Horman --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 1 +

[PATCH 10/16] arm64: dts: r8a7795: Use R-Car Gen 3 fallback binding for i2c nodes

Use recently added R-Car Gen 3 fallback binding for i2c nodes in DT for r8a7795 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7795 and the fallback binding for R-Car Gen 3. Signed-off-by: Simon Horman

[PATCH 01/16] arm64: dts: r8a7796: Add all MSIOF nodes

From: Geert Uytterhoeven Add the device nodes for all MSIOF SPI controllers. Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman --- arch/arm64/boot/dts/renesas/r8a7796.dtsi | 54

Re: [PATCHv3 2/4] v4l: vsp1: Refactor video pipeline configuration

Hi Laurent, I've been reworking this series to split things out and adapt for the comments you've provided, but I have the following queries outstanding: On 15/12/16 11:50, Kieran Bingham wrote: > Hi Laurent, > > On 14/12/16 16:30, Laurent Pinchart wrote: >> Hi Kieran, >> >> Thank you for the

[GIT PULL] Renesas ARM64 Based SoC DT Updates for v4.11

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM64 based SoC DT updates for v4.11. This is based on v4.10-rc2 as v4.10-rc1 does not compile using the defconfig. The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88: Linux 4.10-rc2 (2017-01-01 14:31:53

[PATCH 12/16] arm64: dts: r8a7796: salvator-x: Update memory node to 4 GiB map

From: Takeshi Kihara This patch updates memory region: - After changes, the new map of the Salvator-X board on R8A7796 SoC Bank0: 2GiB RAM : 0x4800 -> 0x000bfff Bank1: 2GiB RAM : 0x0006 -> 0x0067fff - Before changes, the old

[GIT PULL] Renesas ARM Based SoC Defconfig Updates for v4.11

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC defconfig updates for v4.11. The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) are available in the git repository at:

[PATCH 02/16] arm64: dts: r8a7796: Add CAN external clock support

From: Chris Paterson Adds external CAN clock node for r8a7796. This clock can be used as fCAN clock of CAN and CAN FD controller. Based on a patch for r8a7795 by Ramesh Shanmugasundaram. Signed-off-by: Chris Paterson Reviewed-by: Geert

[PATCH 04/25] ARM: dts: r8a7745: Add device node for PRR

From: Geert Uytterhoeven Add a device node for the Product Register, which provides SoC product and revision information. Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman ---

[PATCH 13/25] ARM: dts: r8a7778: Use R-Car Gen 1 fallback binding for i2c nodes

Use recently added R-Car Gen 1 fallback binding for i2c nodes in DT for r8a7778 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7778 and the fallback binding for R-Car Gen 1. Signed-off-by: Simon Horman

[PATCH 05/25] ARM: dts: r8a73a4: Use SoC-specific compat string for mmcif

Use the SoC-specific compat string for mmcif in DT for the r8a73a4 SoC. This is in keeping with the use of compat strings for mmcif for other Renesas ARM based SoCs. Signed-off-by: Simon Horman Acked-by: Geert Uytterhoeven ---

[PATCH 02/25] ARM: dts: r8a7745: Move RST node before SYSC node

From: Geert Uytterhoeven To preserve both alphabetical (label) and numerical ordering (unit address). Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman --- arch/arm/boot/dts/r8a7745.dtsi | 10 +-

[PATCH 06/25] ARM: dts: r8a7778: Use SoC-specific compat string for mmcif

Use the SoC-specific compat string for mmcif in DT for the r8a7778 SoC. This is in keeping with the use of compat strings for mmcif for other Renesas ARM based SoCs. Signed-off-by: Simon Horman Acked-by: Geert Uytterhoeven ---

[PATCH 09/25] ARM: dts: r8a7790: Use renesas,rcar-gen2-usb-phy fallback binding

A fallback binding for the Renesas R-Car Gen2 PHY driver was added by commit cb8ba08d ("phy: rcar-gen2: add fallback binding"). This patch makes use of this binding in the DT for the r8a7790 SoC. Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven

[PATCH 03/25] ARM: dts: r8a7743: Add device node for PRR

From: Geert Uytterhoeven Add a device node for the Product Register, which provides SoC product and revision information. Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman ---

[PATCH 07/25] ARM: dts: sh73a0: Use SoC-specific compat string for mmcif

Use the SoC-specific compat string for mmcif in DT for the sh73a0 SoC. This is in keeping with the use of compat strings for mmcif for other Renesas ARM based SoCs. Signed-off-by: Simon Horman Acked-by: Geert Uytterhoeven ---

[PATCH 10/25] ARM: dts: r8a7791: Use renesas,rcar-gen2-usb-phy fallback binding

A fallback binding for the Renesas R-Car Gen2 PHY driver was added by commit cb8ba08d ("phy: rcar-gen2: add fallback binding"). This patch makes use of this binding in the DT for the r8a7791 SoC. Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven

[PATCH 01/25] ARM: dts: r8a7743: Move RST node before SYSC node

From: Geert Uytterhoeven To preserve both alphabetical (label) and numerical ordering (unit address). Signed-off-by: Geert Uytterhoeven Signed-off-by: Simon Horman --- arch/arm/boot/dts/r8a7743.dtsi | 10 +-

[PATCH 22/25] ARM: dts: r8a7794: Use R-Car Gen 2 fallback binding for iic nodes

Use recently added R-Car Gen 2 fallback binding for iic nodes in DT for r8a7794 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7794 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 12/25] ARM: dts: r8a7779: Use R-Car Gen 1 fallback binding for i2c nodes

Use recently added R-Car Gen 1 fallback binding for i2c nodes in DT for r8a7779 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7779 and the fallback binding for R-Car Gen 1. Signed-off-by: Simon Horman

[PATCH 11/25] ARM: dts: r8a7794: Use renesas,rcar-gen2-usb-phy fallback binding

A fallback binding for the Renesas R-Car Gen2 PHY driver was added by commit cb8ba08d ("phy: rcar-gen2: add fallback binding"). This patch makes use of this binding in the DT for the r8a7794 SoC. Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven

[PATCH 1/5] ARM: shmobile: apmu: Add more register documentation

From: Geert Uytterhoeven Signed-off-by: Geert Uytterhoeven Tested-by: Hiep Cao Minh Signed-off-by: Simon Horman --- arch/arm/mach-shmobile/platsmp-apmu.c | 14 ++ 1 file changed, 10

[PATCH 24/25] ARM: dts: r8a7792: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7792 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7792 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 17/25] ARM: dts: r8a7793: Use R-Car Gen 2 fallback binding for i2c nodes

Use recently added R-Car Gen 2 fallback binding for i2c nodes in DT for r8a7793 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7793 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[GIT PULL] Renesas ARM Based SoC Updates for v4.11

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC updates for v4.11. The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) are available in the git repository at:

[PATCH 08/25] ARM: dts: gose: Add da9063 PMIC device node for system restart

From: Geert Uytterhoeven Enable i2c6, and add a device node for the da9063 PMIC, with subnodes for rtc and wdt. Regulator support is not yet included. This allows the system to be restarted when the watchdog timer times out, or when a system restart is requested.

[PATCH 15/25] ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for i2c nodes

Use recently added R-Car Gen 2 fallback binding for i2c nodes in DT for r8a7791 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7791 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 16/25] ARM: dts: r8a7792: Use R-Car Gen 2 fallback binding for i2c nodes

Use recently added R-Car Gen 2 fallback binding for i2c nodes in DT for r8a7792 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7792 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 20/25] ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for iic nodes

Use recently added R-Car Gen 2 fallback binding for iic nodes in DT for r8a7791 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7791 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 23/25] ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7791 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7791 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 25/25] ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7790 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7790 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 14/25] ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for i2c nodes

Use recently added R-Car Gen 2 fallback binding for i2c nodes in DT for r8a7790 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7790 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 21/25] ARM: dts: r8a7793: Use R-Car Gen 2 fallback binding for iic nodes

Use recently added R-Car Gen 2 fallback binding for iic nodes in DT for r8a7793 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7793 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 18/25] ARM: dts: r8a7794: Use R-Car Gen 2 fallback binding for i2c nodes

Use recently added R-Car Gen 2 fallback binding for i2c nodes in DT for r8a7794 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7794 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 19/25] ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for iic nodes

Use recently added R-Car Gen 2 fallback binding for iic nodes in DT for r8a7790 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7790 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH 3/5] ARM: shmobile: apmu: Allow booting secondary CPU cores in debug mode

From: Geert Uytterhoeven Now debug resource reset is handled properly, allow booting secondary CPU cores when hardware debug mode is enabled (MD21=1) on SoCs using the "renesas,apmu" enable method. Signed-off-by: Geert Uytterhoeven Tested-by:

[PATCH 2/5] ARM: shmobile: apmu: Add debug resource reset for secondary CPU boot

From: Geert Uytterhoeven In debug mode (MD21=1), reset requests derived from power-shutoff to the AP-system CPU cores must be enabled before the AP-system CPU cores resume from power-shutoff for the first time. Else resume may fail, causing the system to hang during

[PATCH 4/5] ARM: shmobile: r8a7791: Allow booting secondary CPU cores in debug mode

From: Geert Uytterhoeven Now debug resource reset is handled properly, allow booting secondary CPU cores when hardware debug mode is enabled (MD21=1, SW8-4=OFF on koelsch) on legacy r8a7791. Signed-off-by: Geert Uytterhoeven Signed-off-by:

[PATCH 5/5] ARM: shmobile: rcar-gen2: Remove unused rcar_gen2_read_mode_pins()

From: Geert Uytterhoeven After 1. commit 9f5ce39ddb8f68b3 ("ARM: shmobile: rcar-gen2: Obtain extal frequency from DT"), 2. commit 80951f04c3f92533 ("ARM: shmobile: rcar-gen2: Stop passing mode pins state to clock driver"), 3. and handling of debug

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

On Wednesday, January 4, 2017 6:29:39 PM CET Nikita Yushchenko wrote: > > Just a guess, but if the inbound translation windows in the host > > bridge are wider than 32-bit, the reason for setting up a single > > 32-bit window is probably because that is what the parent bus supports. > > Well

Re: [PATCH 18/19] serial: sh-sci: Remove unused platform data capabilities field

Hi Geert, On Friday 06 Jan 2017 11:59:58 Geert Uytterhoeven wrote: > On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > > The field isn't set by any platform but is only used internally in the > > driver to hold data parsed from DT. Move it to the sci_port structure. > > This does mean

Re: [PATCH 18/19] serial: sh-sci: Remove unused platform data capabilities field

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The field isn't set by any platform but is only used internally in the > driver to hold data parsed from DT. Move it to the sci_port structure. This does mean legacy platform data

Re: [PATCH 19/19] serial: sh-sci: Compute the regshift value for SCI ports

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > SCI instances found in SH SoCs have different spacing between registers > depending on the SoC. The platform data contains a regshift field that > tells the driver by how many bits

Re: [PATCH 00/19] sh-sci: Platform data simplification

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > Most of the patches in this series have been sitting in my development tree > for three years now. While rebasing all my development branches I decided it > was time to send them out

Re: [PATCH 17/19] serial: sh-sci: Remove manual break debouncing

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The sh-sci driver implements manual break debouncing for a few SH > platforms by reading the value of the RX pin port register. This feature > is optional and the driver considers all negative or

Re: [PATCH 16/19] serial: sh-sci: Remove the platform data dma slave rx/tx channel IDs

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > Only SH platforms still use platform data for the sh-sci, and none of > them declare DMA channels connected to the SCI. Remove the corresponding > platform data fields and simplify the driver

Re: [PATCH 15/19] serial: sh-sci: Extend sci_port_params with more port parameters

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The fifo size, overrun register and mask, sampling rate mask and error > mask all depend on the port type only and don't need to be computed at > runtime. Add them to the

Re: [PATCH 13/19] serial: sh-sci: Replace regmap array with port parameters

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > Turn the regmap two-dimensional array to an array of port parameters and > store a pointer to the port parameters in the sci_port structure. This > will allow handling additional port type

Re: [PATCH 14/19] serial: sh-sci: Constify platform data

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The driver modifies platform data for internal purpose only. Fix that > and make the platform data structure const. > > Signed-off-by: Laurent Pinchart

Re: [PATCH 10/19] sh: Don't set the sh-sci platform data scscr CKE0 bit

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The bit is only set by platforms that also set the CKE1 but, in which > case its value is ignored by the device. Don't set it, this simplifies > platform data and only leaves the CKE1 bit to be

Re: [PATCH 12/19] serial: sh-sci: Remove initialization of zero fields in sci_port_params

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The compiler zeros uninitialized fields, don't zero them manually. > > Signed-off-by: Laurent Pinchart Reviewed-by: Geert Uytterhoeven

Re: [PATCH 11/19] sh: Don't set the sh-sci platform data REIE bit when not implemented

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > According to the datasheets, the sh7760 SIM and sh7723 SCIFA instances > don't implement the REIE bit. Don't set it in platform data. > > Signed-off-by: Laurent Pinchart

Re: [PATCH 08/19] sh: sh3: sh770x: Fix platform data for the IRDA serial port

Hi Geert, On Friday 06 Jan 2017 11:18:32 Geert Uytterhoeven wrote: > On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > > Even though most of its registers are 8-bit wide, the IRDA has two > > 16-bit registers that make it a 16-bit peripheral and not a 8-bit > > peripheral with addresses

Re: [PATCH 08/19] sh: sh3: sh770x: Fix platform data for the IRDA serial port

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > Even though most of its registers are 8-bit wide, the IRDA has two > 16-bit registers that make it a 16-bit peripheral and not a 8-bit > peripheral with addresses shifted by one. Fix

Re: [PATCH 09/19] sh: Don't set the sh-sci platform data regshift field

Hi Laurent, On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The regshift value is computed automatically by the driver, there's no > need to set it in platform data. Specify the associated memory resource > lengths to ensure proper

Re: [PATCH 07/19] sh: Don't set sh-sci port_reg

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The driver considers all negative or zero values of the port_reg field > as invalid. The four platforms that set the field to a register address > all use an address higher than 0x7fff, which

Re: [PATCH 06/19] sh: Don't set the sh-sci pdata UPF_BOOT_AUTOCONF flags

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The flag is set by the driver internally, don't set it in platform data. > > Signed-off-by: Laurent Pinchart Reviewed-by: Geert Uytterhoeven

Re: [PATCH 05/19] sh: sh726[49]: Don't set sh-sci pdata scscr TOIE bit

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The SCIF ports on sh7264 and sh7269 don't support the TOIE bit according > to the datasheets. > > Signed-off-by: Laurent Pinchart Looks OK for sh7269

Re: [PATCH 01/19] serial: sh-sci: Set the SCSCR TE and RE bits in the driver

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The Transmit Enable and Receive Enable bits are set in the scscr field > of all instances of the sh-sci platform data. Set them in the driver > directly to prepare for their removal from platform

Re: [PATCH 02/19] serial: sh-sci: Don't rely on platform data flags when not needed

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The UPF_BOOT_AUTOCONF platform data flag is set by all platforms, > hardcode it. > > The UPF_IOREMAP flag is set by a single SH platform and thus needs to be > kept. However, for ARM platforms,

Re: [PATCH 04/19] sh: Don't set sh-sci pdata scscr TIE and RIE bits

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The scscr platform data field is used by the driver in three locations. > One of them masks out all bits except SCSCR_REIE. The two other are the > set_termios handler and the console write

Re: [PATCH 03/19] sh: Don't set sh-sci pdata scscr TE and RE bits

On Wed, Jan 4, 2017 at 12:06 AM, Laurent Pinchart wrote: > The bits are set by the driver internally, don't set them in platform > data. > > Signed-off-by: Laurent Pinchart Reviewed-by: Geert Uytterhoeven

Re: [PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Laurent, Sorry for the delayed answer but I am quite busy at the moment. On 06-01-2017 01:48, Laurent Pinchart wrote: [snip] The TX_READY signal is documented in the i.MX6 datasheet as being a PHY output signal, but there seems to be no HDMI TX register from which its state

  1   2   >