Re: [PATCH] v4l: vsp1: Start and stop DRM pipeline independently of planes

Hi Kieran, On Monday, 25 September 2017 20:25:14 EEST Kieran Bingham wrote: > On 15/08/17 23:57, Laurent Pinchart wrote: > > The KMS API supports enabling a CRTC without any plane. To enable that > > use case, we need to start the pipeline when configuring the LIF, > > instead of when enabling

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

Hi all, last call for comments before I merge this series. Thanks. -- Daniel -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter |

[PATCH] arm64: dts: salvator-common: add 12V regulator to backlight

From: Ulrich Hecht This fixes the warning "pwm-backlight backlight: backlight supply power not found, using dummy regulator". Fixes: b33be33670217533 ("arm64: dts: salvator-x: Add panel backlight support") Reported-by: Geert Uytterhoeven

[PATCH 2/3] soc: renesas: identify R-Car V3M

From: Sergei Shtylyov Add support for identifying the R-Car V3M (R8A77970) SoC. Signed-off-by: Sergei Shtylyov Reviewed-by: Geert Uytterhoeven Signed-off-by: Simon Horman

[PATCH 1/3] soc: renesas: rcar-rst: add R8A77970 support

From: Sergei Shtylyov Add support for R-Car V3M (R8A77970) to the R-Car RST driver -- this driver is needed for the clock driver to work. Signed-off-by: Sergei Shtylyov Reviewed-by: Geert Uytterhoeven

[PATCH 3/3] ARM: shmobile: rcar-gen2: Make sure CNTVOFF is initialized on CA7/15

From: Geert Uytterhoeven On Cortex-A7, the arch timer CNTVOFF register is uninitialized. Ideally it should be initialized by the boot loader, but it isn't. For the boot CPU, CNTVOFF is initialized by Linux since commit 9ce3fa6816c2fb59 ("ARM: shmobile: rcar-gen2: Add

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

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC defconfig updates for v4.15. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

[GIT PULL] Renesas ARM Based SoC Fixes for v4.14

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC fixes for v4.14. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

[PATCH] ARM: multi_v7_defconfig: Enable BQ32000 RTC driver

From: Biju Das The iWave RZ/G1M Q7 SOM supports RTC (TI BQ32000). To increase hardware support enable the driver in the multi_v7_defconfig multiplatform configuration. Signed-off-by: Biju Das Signed-off-by: Simon Horman

[PATCH 3/3] soc: renesas: rcar-sysc: add R8A77970 support

From: Sergei Shtylyov Add support for R-Car V3M (R8A77970) SoC power areas to the R-Car SYSC driver. Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov

[PATCH 2/3] ARM: Add definition for monitor mode

From: Geert Uytterhoeven provides *_MODE definitions for the various processor modes, but monitor mode was missing. Add MON_MODE to avoid code using the hardcoded value. Suggested-by: Marc Zyngier Signed-off-by: Geert Uytterhoeven

[PATCH 1/3] ARM: debug-ll: Add support for r8a7745

From: Fabrizio Castro Enable low-level debugging support for RZ/G1E (r8a7745). RZ/G1E uses SCIF4 for the debug console. Signed-off-by: Fabrizio Castro Reviewed-by: Chris Paterson Reviewed-by: Geert

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

Hi Olof, Hi Kevin, Hi Arnd, Please consider these Renesas ARM based SoC drivers updates for v4.15. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

[PATCH 0/3] usb: gadget: udc: renesas_usb3: bugfix for v4.14

This patch set is based on the Felipe's usb.git / testing/fixes branch (The commit is 7661ca09b2ff98f48693f431bb01fed62830e433). Yoshihiro Shimoda (3): usb: gadget: udc: renesas_usb3: fix for no-data control transfer usb: gadget: udc: renesas_usb3: fix Pn_RAMMAP.Pn_MPKT value usb: gadget:

[PATCH 1/3] usb: gadget: udc: renesas_usb3: fix for no-data control transfer

When bRequestType & USB_DIR_IN is false and req.length is 0 in control transfer, since it means non-data, this driver should not set the mode as control write. So, this patch fixes it. Fixes: 746bfe63bba3 ("usb: gadget: renesas_usb3: add support for Renesas USB3.0 peripheral controller") Cc:

[PATCH 2/3] usb: gadget: udc: renesas_usb3: fix Pn_RAMMAP.Pn_MPKT value

According to the datasheet of R-Car Gen3, the Pn_RAMMAP.Pn_MPKT should be set to one of 8, 16, 32, 64, 512 and 1024. Otherwise, when a gadget driver uses an interrupt endpoint, unexpected behavior happens. So, this patch fixes it. Fixes: 746bfe63bba3 ("usb: gadget: renesas_usb3: add support for

[PATCH 3/3] usb: gadget: udc: renesas_usb3: Fix return value of usb3_write_pipe()

This patch fixes an issue that this driver cannot go status stage in control read when the req.zero is set to 1 and the len in usb3_write_pipe() is set to 0. Otherwise, if we use g_ncm driver, usb enumeration takes long time (5 seconds or more). Fixes: 746bfe63bba3 ("usb: gadget: renesas_usb3:

Re: [PATCH v6 19/25] rcar-vin: add group allocator functions

On 23/08/17 01:26, Niklas Söderlund wrote: > In media controller mode all VIN instances needs to be part of the same > media graph. There is also a need to each VIN instance to know and in > some cases be able to communicate with other VIN instances. > > Add a allocator framework where the first

Re: [PATCH v6 20/25] rcar-vin: add chsel information to rvin_info

On 23/08/17 01:26, Niklas Söderlund wrote: > Each Gen3 SoC has a limited set of predefined routing possibilities for > which CSI-2 device and virtual channel can be routed to which VIN > instance. Prepare to store this information in the struct rvin_info. > > Signed-off-by: Niklas Söderlund

Re: [PATCH v6 22/25] rcar-vin: add link notify for Gen3

On 23/08/17 01:26, Niklas Söderlund wrote: > Add the ability to process media device link change request. Link > enablement are a bit complicated on Gen3, if it's possible to enable a enablement are -> enabling is if -> whether or not > link depends on what other links already are enabled. On

Re: [PATCH v6 24/25] rcar-vin: enable support for r8a7795

On 23/08/17 01:26, Niklas Söderlund wrote: > Add the SoC specific information for Renesas r8a7795. > > Signed-off-by: Niklas Söderlund Reviewed-by: Hans Verkuil Regards, Hans > --- >

Re: [PATCH v6 23/25] rcar-vin: extend {start,stop}_streaming to work with media controller

On 23/08/17 01:26, Niklas Söderlund wrote: > The procedure to start or stop streaming using the none MC single none MC -> non-MC > subdevice and the MC graph and multiple subdevices are quiet different. quiet -> quite > Create a new function to abstract which method is used based on which >

Re: [PATCH v6 25/25] rcar-vin: enable support for r8a7796

On 23/08/17 01:26, Niklas Söderlund wrote: > Add the SoC specific information for Renesas r8a7796. > > Signed-off-by: Niklas Söderlund Reviewed-by: Hans Verkuil Regards, Hans > --- >

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

The patch spi: sh-msiof: Add compatible strings for r8a774[35] has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

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

The patch spi: sh-msiof: Add r8a774[35] to the compatible list has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Re: [PATCH 0/3] R-Car DU: Clip planes to screen boundaries

Hi Laurent, Thankyou for the patches, On 16/08/17 00:03, Laurent Pinchart wrote: > Hello, > > This patch series fixes support for planes that cross the screen boundaries. > The KMS API supports such a configuration, but the DU and VSP hardware > doesn't. This leads to different kind of dispay

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

Hi Mark, On Mon, Sep 25, 2017 at 6:16 PM, Mark Brown wrote: > The patch > >spi: sh-msiof: Add compatible strings for r8a774[35] > > has been applied to the spi tree at > >git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git > > All being well this means that

Re: [PATCH] v4l: vsp1: Start and stop DRM pipeline independently of planes

Hi Laurent, Thankyou for the patch. On 15/08/17 23:57, Laurent Pinchart wrote: > The KMS API supports enabling a CRTC without any plane. To enable that > use case, we need to start the pipeline when configuring the LIF, > instead of when enabling the first plane. Tested and verified on

Re: [PATCH 1/3] drm: rcar-du: Share plane atomic check code between Gen2 and Gen3

Hi Laurent, On 16/08/17 00:03, Laurent Pinchart wrote: > The plane atomic check implementation is identical on Gen2 (DU planes) > and Gen3 (VSP planes), but two separate functions exist as they operate > on different data structures. Refactor the code to share the > implementation. > >

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

On Mon, Sep 25, 2017 at 07:48:44PM +0200, Geert Uytterhoeven wrote: > Please drop this patch, as there's no need to add explicit matching for these > compatible values. The family-specific compatible values (which the driver > already matches against) are sufficient. While the patch is not

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

Hi Mark, On Mon, Sep 25, 2017 at 8:45 PM, Mark Brown wrote: > On Mon, Sep 25, 2017 at 07:48:44PM +0200, Geert Uytterhoeven wrote: >> Please drop this patch, as there's no need to add explicit matching for these >> compatible values. The family-specific compatible values

Re: [PATCH v6 03/25] rcar-vin: move chip information to own struct

On 23/08/17 01:26, Niklas Söderlund wrote: > When Gen3 support is added to the driver more then chip id will be then -> than > different for the different Soc. To avoid a lot of if statements in the > code create a struct chip_info to contain this information. > > Signed-off-by: Niklas

Re: [PATCH v6 06/25] rcar-vin: move functions regarding scaling

On 23/08/17 01:26, Niklas Söderlund wrote: > In preparation of refactoring the scaling code move the code regarding > scaling to to the top of the file to avoid the need to add forward > declarations. No code is changed in this commit only whole functions > moved inside the same file. > >

Re: [PATCH v6 05/25] rcar-vin: change name of video device

On 23/08/17 01:26, Niklas Söderlund wrote: > The rcar-vin driver needs to be part of a media controller to support > Gen3. Give each VIN instance a unique name so it can be referenced from > userspace. > > Signed-off-by: Niklas Söderlund > Reviewed-by:

Re: [PATCH v6 04/25] rcar-vin: move max width and height information to chip information

On 23/08/17 01:26, Niklas Söderlund wrote: > On Gen3 the max supported width and height will be different from Gen2. > Move the limits to the struct rvin_info to prepare for Gen3 support. > > Signed-off-by: Niklas Söderlund > Reviewed-by: Kieran Bingham

Re: [PATCH v6 07/25] rcar-vin: all Gen2 boards can scale simplify logic

On 23/08/17 01:26, Niklas Söderlund wrote: > The logic to preserve the requested format width and height are too > complex and come from a premature optimization for Gen3. All Gen2 SoC > can scale and the Gen3 implementation will not use these functions at > all so simply preserve the width and

Re: [PATCH v6 09/25] rcar-vin: do not allow changing scaling and composing while streaming

On 23/08/17 01:26, Niklas Söderlund wrote: > It is possible on Gen2 to change the registers controlling composing and > scaling while the stream is running. Is however not a good idea to do so Is -> It > and could result in trouble. There are also no good reason to allow reason -> reasons >

Re: [PATCH v6 08/25] rcar-vin: do not reset crop and compose when setting format

On 23/08/17 01:26, Niklas Söderlund wrote: > It was a bad idea to reset the crop and compose settings when a new > format is set. This would overwrite any crop/compose set by s_select and > cause unexpected behaviors, remove it. Also fold the reset helper in to > the only remaining caller. > >

Re: [PATCH v6 10/25] rcar-vin: read subdevice format for crop only when needed

On 23/08/17 01:26, Niklas Söderlund wrote: > Instead of caching the subdevice format each time the video device > format is set read it directly when its needed. As it turns out the its -> it's > format is only needed when figuring out the max rectangle for cropping. > > This simplify the code

Re: [PATCH v6 11/25] rcar-vin: fix handling of single field frames (top, bottom and alternate fields)

On 23/08/17 01:26, Niklas Söderlund wrote: > It was never proper support in the VIN driver to deliver ALTERNATING It -> There > field format to user-space, remove this field option. For sources using > this field format instead use the VIN hardware feature of combining the > fields to an

Re: [PATCH v6 12/25] rcar-vin: move media bus configuration to struct rvin_info

On 23/08/17 01:26, Niklas Söderlund wrote: > Bus configuration will once the driver is extended to to support Gen3 to to -> to > contain information not specific to only the directly connected parallel > subdevice. Move it to struct rvin_info to show it's not always coupled > to the parallel

Re: [PATCH v6 13/25] rcar-vin: enable Gen3 hardware configuration

On 23/08/17 01:26, Niklas Söderlund wrote: > Add the register needed to work with Gen3 hardware. This patch adds > the logic for how to work with the Gen3 hardware. More work is required > to enable the subdevice structure needed to configure capturing. > > Signed-off-by: Niklas Söderlund

Re: [PATCH] clk/Renesas: Delete an error message for a failed memory allocation in three functions

Hi Markus, On Mon, Sep 25, 2017 at 10:34 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 25 Sep 2017 10:10:51 +0200 > > The script "checkpatch.pl" pointed information out like the following. > > WARNING: Possible

Re: [PATCH v6 14/25] rcar-vin: add functions to manipulate Gen3 CHSEL value

On 23/08/17 01:26, Niklas Söderlund wrote: > On Gen3 the CSI-2 routing is controlled by the VnCSI_IFMD register. One > feature of this register is that it's only present in the VIN0 and VIN4 > instances. The register in VIN0 controls the routing for VIN0-3 and the > register in VIN4 controls

Re: [PATCH v6 15/25] rcar-vin: add flag to switch to media controller mode

On 23/08/17 01:26, Niklas Söderlund wrote: > On Gen3 a media controller API needs to be used to allow userspace to > configure the subdevices in the pipeline instead of directly controlling > a single source subdevice, which is and will continue to be the mode of > operation on Gen2. > > Prepare

Re: [PATCH v6 16/25] rcar-vin: break out format alignment and checking

On 23/08/17 01:26, Niklas Söderlund wrote: > Part of the format aliment and checking can be shared with the Gen3 aliment -> alignment > format handling. Break that part out to it's own function. While doing it's -> its > this clean up the checking and add more checks. > > Signed-off-by:

Re: [PATCH v6 17/25] rcar-vin: use different v4l2 operations in media controller mode

On 23/08/17 01:26, Niklas Söderlund wrote: > When the driver runs in media controller mode it should not directly > control the subdevice instead userspace will be responsible for > configuring the pipeline. To be able to run in this mode a different set > of v4l2 operations needs to be used. > >

Re: [PATCH v6 18/25] rcar-vin: prepare for media controller mode initialization

On 23/08/17 01:26, Niklas Söderlund wrote: > When running in media controller mode a media pad is needed, register > one. Also set the media bus format to CSI-2. > > Signed-off-by: Niklas Söderlund Reviewed-by: Hans Verkuil

RE: [PATCH v2] ARM: dts: iwg22d: Enable SDHI0 controller

Hello Simon, > From: Simon Horman [mailto:ho...@verge.net.au] > Sent: 25 September 2017 08:18 > > On Fri, Sep 22, 2017 at 01:33:39PM +, Fabrizio Castro wrote: > > Hello Simon, > > > > just to clarify the changes between v1 and v2, we can't use SDR50 and > SDR104 (due to an HW issue)

[PATCH] clk/Renesas: Delete an error message for a failed memory allocation in three functions

From: Markus Elfring Date: Mon, 25 Sep 2017 10:10:51 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus fix affected source code places. Signed-off-by: Markus Elfring

[PATCH 1/2] spi: sh-msiof: Add compatible strings for r8a774[35]

Signed-off-by: Fabrizio Castro --- drivers/spi/spi-sh-msiof.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/spi/spi-sh-msiof.c b/drivers/spi/spi-sh-msiof.c index 0eb1e95..0080844 100644 --- a/drivers/spi/spi-sh-msiof.c +++

[PATCH 0/2] spi: sh-msiof: Add r8a774[35] bindings

This series adds compatible strings and device tree bindings in order to enable msiof support for r8a7743 and r8a7745. Fabrizio Castro (2): spi: sh-msiof: Add compatible strings for r8a774[35] dt-bindings: spi: sh-msiof: Add r8a774[35] to the compatible list

[PATCH 2/2] dt-bindings: spi: sh-msiof: Add r8a774[35] to the compatible list

Signed-off-by: Fabrizio Castro --- Documentation/devicetree/bindings/spi/sh-msiof.txt | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/spi/sh-msiof.txt b/Documentation/devicetree/bindings/spi/sh-msiof.txt

Re: [PATCH] arm64: defconfig: enable R8A77970 SoC

On Sat, Sep 23, 2017 at 01:05:25PM +0200, Geert Uytterhoeven wrote: > On Fri, Sep 22, 2017 at 11:36 PM, Sergei Shtylyov > wrote: > > Enable the Renesas R-Car V3M (R8A77970) SoC in the ARM64 defconfig. > > > > Suggested-by: Simon Horman > >

Re: [PATCH 2/2] dt-bindings: spi: sh-msiof: Add r8a774[35] to the compatible list

On Mon, Sep 25, 2017 at 10:54 AM, Fabrizio Castro wrote: > Signed-off-by: Fabrizio Castro > --- > Documentation/devicetree/bindings/spi/sh-msiof.txt | 6 -- Reviewed-by: Geert Uytterhoeven

Re: [PATCH 1/2] spi: sh-msiof: Add compatible strings for r8a774[35]

Hi Fabrizio, On Mon, Sep 25, 2017 at 10:54 AM, Fabrizio Castro wrote: > Signed-off-by: Fabrizio Castro This patch is not needed... > --- > drivers/spi/spi-sh-msiof.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

RE: [PATCH 1/2] spi: sh-msiof: Add compatible strings for r8a774[35]

Hello Geert, Thank you for getting back to me. > -Original Message- > From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] On > Behalf Of Geert Uytterhoeven > Sent: 25 September 2017 12:22 > To: Fabrizio Castro > Cc: Mark Brown

Re: [PATCH] ARM: shmobile: remove inconsistent ; from documentation

On Thu, Sep 21, 2017 at 12:04:27PM +0200, Geert Uytterhoeven wrote: > On Thu, Sep 21, 2017 at 11:44 AM, Simon Horman > wrote: > > Consistently do not suffix compat string documentation with a ';' > > > > Signed-off-by: Simon Horman > >

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

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 +, Yoshihiro Shimoda wrote: > > > Hi Geert-san, > > > > > > > From: Geert Uytterhoeven > > > >

Re: [PATCH 4/4] arm64: dts: renesas: r8a77995: draak: enable USB2.0 Host (EHCI/OHCI)

On Thu, Sep 21, 2017 at 11:12:12AM +0200, Geert Uytterhoeven wrote: > On Thu, Sep 21, 2017 at 10:58 AM, Simon Horman wrote: > > [CC Geert] > > > > On Thu, Sep 14, 2017 at 07:30:43PM +0900, Yoshihiro Shimoda wrote: > >> This patch enables USB2.0 Host (EHCI/OHCI) for r8a77995. >

Re: [PATCH 2/2] arm64: dts: renesas: r8a7796: add USB3.0 peripheral device node

On Thu, Sep 21, 2017 at 02:46:37PM +0200, Geert Uytterhoeven wrote: > On Thu, Sep 21, 2017 at 7:31 AM, Yoshihiro Shimoda > wrote: > > This patch adds USB3.0 peripheral channel 0 device node for r8a7796. > > > > Signed-off-by: Yoshihiro Shimoda

Re: [PATCH 1/2] arm64: dts: renesas: r8a7795: add USB3.0 peripheral device node

On Thu, Sep 21, 2017 at 02:46:18PM +0200, Geert Uytterhoeven wrote: > On Thu, Sep 21, 2017 at 7:31 AM, Yoshihiro Shimoda > wrote: > > This patch adds USB3.0 peripheral channel 0 device node for r8a7795. > > > > Signed-off-by: Yoshihiro Shimoda

Re: [PATCH v2] ARM: dts: iwg22d: Enable SDHI0 controller

On Fri, Sep 22, 2017 at 01:33:39PM +, Fabrizio Castro wrote: > Hello Simon, > > just to clarify the changes between v1 and v2, we can't use SDR50 and SDR104 > (due to an HW issue) therefore the pinctrl for UHS has been removed and we > dropped property "sd-uhs-sdr104". High Speed has been