Re: Applied "spi: sh-msiof: Add compatible strings for r8a774[35]" to the spi tree

Hi Mark, Geert, everyone, On Wed, Sep 27, 2017 at 2:30 AM, Mark Brown wrote: > On Mon, Sep 25, 2017 at 09:15:53PM +0200, Geert Uytterhoeven wrote: > >> My rebuttal is threefold: >> 1. Listing the fallback property is mandatory for new SoCs. We only keep >> the per-SoC compatible values in

RE: [PATCH 2/2] arm64: dts: renesas: r8a77995: draak: enable EthernetAVB

Hi Simon-san, > From: Simon Horman > Sent: Monday, September 25, 2017 4:08 PM > > On Thu, Sep 21, 2017 at 10:37:15AM +, Yoshihiro Shimoda wrote: > > Hi Simon-san, > > > > > From: Simon Horman > > > Sent: Friday, September 15, 2017 4:35 PM > > > > > > On Wed, Sep 13, 2017 at 11:58:47PM +,

Re: [PATCH v3 0/7] clocksource: sh_cmt: Update driver for DT binding rework

On 26/09/2017 10:26, Laurent Pinchart wrote: > Reviewed-by: Laurent Pinchart Thanks. I applied the whole series. -- Daniel -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook |

Re: Applied "spi: sh-msiof: Add compatible strings for r8a774[35]" to the spi tree

On Mon, Sep 25, 2017 at 09:15:53PM +0200, Geert Uytterhoeven wrote: > My rebuttal is threefold: > 1. Listing the fallback property is mandatory for new SoCs. We only keep > the per-SoC compatible values in the driver for older SoCs that predate > the introduction of fallback properties

Re: [RFC 09/13] v4l: rcar-fcp: Configure the number of outstanding read transactions

Hi Laurent, On Tue, Sep 26, 2017 at 3:01 PM, Laurent Pinchart wrote: > On Tuesday, 26 September 2017 14:50:46 EEST Geert Uytterhoeven wrote: >> On Tue, Sep 26, 2017 at 12:06 PM, Laurent Pinchart wrote: >> > static const struct of_device_id rcar_fcp_of_match[] = { >> > { .compatible = "re

Re: [RFC 09/13] v4l: rcar-fcp: Configure the number of outstanding read transactions

Hi Geert, On Tuesday, 26 September 2017 14:50:46 EEST Geert Uytterhoeven wrote: > On Tue, Sep 26, 2017 at 12:06 PM, Laurent Pinchart wrote: > > The FCPV has a selectable number of outstanding read transactions. > > According to the documentation the value must be set based on the type > > of the V

Re: [RFC 02/13] dt-bindings: media: renesas-fcp: Add a compatible string for VSPI FCP

Hi Geert, On Tuesday, 26 September 2017 15:46:59 EEST Geert Uytterhoeven wrote: > On Tue, Sep 26, 2017 at 2:39 PM, Laurent Pinchart wrote: > > On Tuesday, 26 September 2017 14:47:35 EEST Geert Uytterhoeven wrote: > >> On Tue, Sep 26, 2017 at 12:05 PM, Laurent Pinchart wrote: > >> > The FCP instanc

Re: [RFC 02/13] dt-bindings: media: renesas-fcp: Add a compatible string for VSPI FCP

Hi Laurent, On Tue, Sep 26, 2017 at 2:39 PM, Laurent Pinchart wrote: > On Tuesday, 26 September 2017 14:47:35 EEST Geert Uytterhoeven wrote: >> On Tue, Sep 26, 2017 at 12:05 PM, Laurent Pinchart wrote: >> > The FCP instances associated with a VSPI must be treated differently >> > than the ones as

Re: [RFC 02/13] dt-bindings: media: renesas-fcp: Add a compatible string for VSPI FCP

Hi Geert, On Tuesday, 26 September 2017 14:47:35 EEST Geert Uytterhoeven wrote: > On Tue, Sep 26, 2017 at 12:05 PM, Laurent Pinchart wrote: > > The FCP instances associated with a VSPI must be treated differently > > than the ones associated with another type of VSP. Add a new compatible > > strin

RE: Applied "spi: sh-msiof: Add compatible strings for r8a774[35]" to the spi tree

Hi Mark, I am very sorry about the confusion. Geert has a good point so please drop this patch. Thanks, Fabrizio > -Original Message- > From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] On > Behalf Of Geert Uytterhoeven > Sent: 25 September 2017 20:16 > To: Mark

Re: [RFC 09/13] v4l: rcar-fcp: Configure the number of outstanding read transactions

Hi Laurent, On Tue, Sep 26, 2017 at 12:06 PM, Laurent Pinchart wrote: > The FCPV has a selectable number of outstanding read transactions. > According to the documentation the value must be set based on the type > of the VSP the FCPV is connected to. Set the register accordingly at > probe time.

Re: [RFC 02/13] dt-bindings: media: renesas-fcp: Add a compatible string for VSPI FCP

Hi Laurent, On Tue, Sep 26, 2017 at 12:05 PM, Laurent Pinchart wrote: > The FCP instances associated with a VSPI must be treated differently > than the ones associated with another type of VSP. Add a new compatible > string to allow telling them apart. > > Signed-off-by: Laurent Pinchart > --- >

[RFC 11/13] v4l: rcar-fcp: Support FCNL decompression

Create child devices associated with the lossy decompression reserved memory areas and return them as decompression bus masters. Signed-off-by: Laurent Pinchart --- drivers/media/platform/rcar-fcp.c | 165 +- 1 file changed, 161 insertions(+), 4 deletions(-)

[RFC 08/13] v4l: rcar-fcp: Check device revision at probe time

Verify that the device revision register reports a valid value, otherwise reject the device. Signed-off-by: Laurent Pinchart --- drivers/media/platform/rcar-fcp.c | 139 -- 1 file changed, 132 insertions(+), 7 deletions(-) diff --git a/drivers/media/platform/

[RFC 09/13] v4l: rcar-fcp: Configure the number of outstanding read transactions

The FCPV has a selectable number of outstanding read transactions. According to the documentation the value must be set based on the type of the VSP the FCPV is connected to. Set the register accordingly at probe time. Signed-off-by: Laurent Pinchart --- drivers/media/platform/rcar-fcp.c | 25 ++

[RFC 06/13] arm64: dts: r8a7795: Reference the lossy memory region from the FCPss

The FCPV instances can perform transparent near-lossless compression internally but need the DDR controller to perform decompression. Reference the DDR controller lossy decompression memory region to model that relationship. Signed-off-by: Laurent Pinchart --- arch/arm64/boot/dts/renesas/r8a7795

[RFC 12/13] v4l: vsp1: Add support for near-lossless compression (FCNL) in the WPF

Visual near-lossless compression is a technique used to lower the memory bandwidth consumption by transparently (de)compressing frames when reading them from or writing them to memory. When writing frames to memory the VSPI, VSPBC and VSPBD (through their connnected FCP) can transparently compress

[RFC 07/13] arm64: dts: r8a7795: Add dma-ranges property in the /soc node

DMA address translation requires a dma-ranges property in bus nodes. While some operating systems work around the absence of such property in an attempt to implement compatibility with incorrect DT, the property is nonetheless required. Add the dma-ranges property to the /soc node that contains al

[RFC 13/13] v4l: vsp1: Add support for near-lossless compression (FCNL) in the RPF

Visual near-lossless compression is a technique used to lower the memory bandwidth consumption by transparently (de)compressing frames when reading them from or writing them to memory. When reading frames from memory the DDR controller can transparently decompress them using FCNL. Implement suppor

[RFC 10/13] v4l: rcar-fcp: Prepare driver API for FCNL support

To support transparent FCNL decompression the FCP users will need to use different bus master devices for compressed and uncompressed formats. Rename the rcar_fcp_get_device() function to rcar_fcp_get_bus_master() and add a new argument to select the bus master in order to prepare for that change.

[RFC 05/13] arm64: dts: r8a7795: Add lossy decompression reserved memory nodes

The secure mode boot loader on R8A7795 platforms can program the DDR controller to perform transparent image decompression when accessing certain areas of RAM. Those areas must be kept out of system memory. Add place-holder nodes for the boot loader to fill with the list of lossy decompression are

[RFC 02/13] dt-bindings: media: renesas-fcp: Add a compatible string for VSPI FCP

The FCP instances associated with a VSPI must be treated differently than the ones associated with another type of VSP. Add a new compatible string to allow telling them apart. Signed-off-by: Laurent Pinchart --- Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++- 1 file changed, 2

[RFC] [U-BOOT] board: salvator-x: Add reserved lossy decompression areas to DT

From: Laurent Pinchart Lossy decompression memory areas can't be used as normal system memory as reading from them will automatically perform lossy decompression. The decompression areas are configured by the BL2 in registers that are accessible from secure mode only, and thus can't be read by U

[RFC 01/13] dt-bindings: reserved-memory: Add binding for the Renesas lossy decompression area

The Renesas R-Car Gen3 DDR3/4 controller supports transparent decompression of data stored in the Renesas near-lossless image compression format (FCNL). Decompression is controlled based on system memory ranges configured by the secure mode boot loader. As any data located within those memory range

[RFC 00/13] R-Car: Enable lossy compression in VSP video pipelines

Hello, These patches are a proof-of-concept implementation of lossy compression and decompression support for the VSP driver. Patches for the whole stack are needed, in the ARM trusted firmware BL2, U-Boot and the Linux kernel. For convenience, and because this is an RFC, I've included them all i

[RFC] [FW] bl2: plat: renesas: rcar: Enable all lossy decompression areas

From: Laurent Pinchart Enable lossy decompression areas 1 and 2 with a memory region of 48MB each to support the RGB32 and packed YUV formats. Signed-off-by: Laurent Pinchart --- plat/renesas/rcar/bl2_rcar_setup.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a

[RFC 03/13] dt-bindings: media: renesas-fcp: Add memory-region property

The FCP can't perform lossy decompression by itself, but relies instead on the DDR controller to provide that feature. To do so, it needs to allocate buffers from a special lossy decompression reserved memory area. This DT property references that memory area. Signed-off-by: Laurent Pinchart ---

[RFC 04/13] arm64: dts: renesas: Use renesas,fcpvi compatible string

The FCP instances associated with a VSPI must be treated differently than the ones associated with another type of VSP. Use the appropriate compatible string. The fallback renesas,fcpv compatible string allows for backward compatibility with platforms that don't recognize the new compatible string

Re: [PATCH v3 0/7] clocksource: sh_cmt: Update driver for DT binding rework

Hi Geert, Thank you for the patches. On Monday, 18 September 2017 16:46:40 EEST Geert Uytterhoeven wrote: > Hi Daniel, Thomas, Rob, Mark, Magnus, > > This patch series updates the sh_cmt clocksource driver for the recent DT > binding rework that was merged in v4.14-rc1. > > This series is