Re: [PATCH 1/4] arm64: dts: r8a7795: Add HSUSB device node

Hi Shimoda-san, On Tue, May 24, 2016 at 6:57 AM, Yoshihiro Shimoda wrote: > Signed-off-by: Yoshihiro Shimoda > --- > arch/arm64/boot/dts/renesas/r8a7795.dtsi | 17 + > 1 file changed, 17 insertions(+) > > diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi > b/arch/arm64/boot

Re: [PATCH 2/4] arm64: dts: salvator-x: enable usb2_phy of channel 0

Hi Shimoda-san, On Tue, May 24, 2016 at 6:57 AM, Yoshihiro Shimoda wrote: > This patch also adds a regulator node for USB2.0 to handle VBUS on/off > by the phy-rcar-gen3-usb2 driver. > > Signed-off-by: Yoshihiro Shimoda > --- > arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 24 >

Re: [PATCH v2 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support

Hi Geert, On 5/24/2016 1:35 PM, Geert Uytterhoeven wrote: Hi Khiem, On Mon, May 23, 2016 at 9:51 AM, Khiem Nguyen wrote: Using 1.0 will open Suspend-to-RAM support if secure firmware supports that feature. However, we might need additional work in drivers to support suspend/resume handlers. S

RE: [PATCH 1/4] arm64: dts: r8a7795: Add HSUSB device node

Hi Geert-san, > From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] On > Behalf Of Geert Uytterhoeven > Sent: Tuesday, May 24, 2016 4:10 PM > > Hi Shimoda-san, > > On Tue, May 24, 2016 at 6:57 AM, Yoshihiro Shimoda > wrote: > > Signed-off-by: Yoshihiro Shimoda > > --- > >

RE: [PATCH 2/4] arm64: dts: salvator-x: enable usb2_phy of channel 0

Hi Geert-san, > From: linux-renesas-soc-ow...@vger.kernel.org > [mailto:linux-renesas-soc-ow...@vger.kernel.org] On Behalf Of Geert > Uytterhoeven > Sent: Tuesday, May 24, 2016 4:13 PM > > Hi Shimoda-san, > > On Tue, May 24, 2016 at 6:57 AM, Yoshihiro Shimoda > wrote: > > This patch also adds

Re: [PATCH v2 11/23] ARM: dts: armadillo800eva: Fix W=1 dtc warnings

Hi Simon, On Tue, May 24, 2016 at 2:33 AM, Simon Horman wrote: >> > >> --- a/arch/arm/boot/dts/r8a7740-armadillo800eva.dts >> > >> +++ b/arch/arm/boot/dts/r8a7740-armadillo800eva.dts > I have queued this up with the above hunk changed to the following. > Please check the resulting patch and let

[PATCH v2 1/4] arm64: dts: r8a7795: Add HSUSB device node

Signed-off-by: Yoshihiro Shimoda --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi index 26df300..a4f9170 100644 --- a/arch/arm64/boot/dts/renesas

[PATCH v2 0/4] arm64: dts: r8a7795: Add HSUSB device node and enable channel 0 of USB2.0

This patch is based on the renesas-drivers / renesas-drivers-2016-05-17-v4.6 tag. Changes from v1: - fix compatible string of hsusb in patch 1. - fix patch 2 for "make dtbs W=1" warning. Yoshihiro Shimoda (4): arm64: dts: r8a7795: Add HSUSB device node arm64: dts: salvator-x: enable usb2_p

[PATCH v2 2/4] arm64: dts: salvator-x: enable usb2_phy of channel 0

This patch also adds a regulator node for USB2.0 to handle VBUS on/off by the phy-rcar-gen3-usb2 driver. Signed-off-by: Yoshihiro Shimoda --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 24 ++ 1 file changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/renesas

[PATCH v2 4/4] arm64: dts: salvator-x: enable HSUSB

Since related drivers doesn't support OTG framework yet, the renesas_usbhs driver cannot detect VBUS in particular situations. And then a gadget driver doesn't work correctly (even if a USB cable is connected to a USB host, nothing happens). However, we can avoid such a situation if we operate the

[PATCH v2 3/4] arm64: dts: salvator-x: enable USB 2.0 Host channel 0

We have to set SW15 to pin 2-3 side on the board before we use CN9 as USB host or peripheral. Signed-off-by: Yoshihiro Shimoda --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts b/

Re: [PATCH] drm: rcar-du: EPROBE_DEFER case doesn't need error message

Hi Morimoto-san, Thank you for the patch. On Tuesday 24 May 2016 14:24:09 Kuninori Morimoto wrote: > From: Kuninori Morimoto > > EPROBE_DEFER is not error, thus, error message on kernel log on this > case is confusable for user. Prints it only error cases. > > Signed-off-by: Kuninori Morimoto

Re: [PATCH/RFC v2 1/4] v4l: Add metadata buffer type and format

Hi Hans, On Mon, May 23, 2016 at 12:09:16PM +0200, Hans Verkuil wrote: > On 05/12/2016 02:18 AM, Laurent Pinchart wrote: > > The metadata buffer type is used to transfer metadata between userspace > > and kernelspace through a V4L2 buffers queue. It comes with a new > > metadata capture capability

Re: [PATCH/RFC v2 1/4] v4l: Add metadata buffer type and format

On 05/24/2016 05:28 PM, Sakari Ailus wrote: > Hi Hans, > >> Should it be mentioned here that changing the video format might change >> the buffersize? In case the buffersize is always a multiple of the width? > > Isn't that the case in general, as with pixel formats? buffersize could also > be so

Re: [PATCH/RFC v2 1/4] v4l: Add metadata buffer type and format

Hi Hans, On Tue, May 24, 2016 at 05:36:42PM +0200, Hans Verkuil wrote: > On 05/24/2016 05:28 PM, Sakari Ailus wrote: > > Hi Hans, > > > >> Should it be mentioned here that changing the video format might change > >> the buffersize? In case the buffersize is always a multiple of the width? > > >

Re: [PATCH] drm: rcar-du: EPROBE_DEFER case doesn't need error message

Hi Laurent > > From: Kuninori Morimoto > > > > EPROBE_DEFER is not error, thus, error message on kernel log on this > > case is confusable for user. Prints it only error cases. > > > > Signed-off-by: Kuninori Morimoto > > --- > > drivers/gpu/drm/rcar-du/rcar_du_drv.c | 6 -- > > 1 file c

[PATCH 0/2 v2] drm: rcar-du: EPROBE_DEFER case doesn't need error message

Hi David, Laurent These removes unneeded error message from Renesas DU driver. Current this unneeded error message makes user confuse. Kuninori Morimoto (2): drm: rcar-du: error message is not needed for drm_vblank_init() drm: rcar-du: error message is not needed for EPROBE_DEFER d

[PATCH 1/2 v2] drm: rcar-du: error message is not needed for drm_vblank_init()

From: Kuninori Morimoto The only reason drm_vblank_init() could return an error at the moment is a kcalloc() failure. So we can remove current error message completely. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - just removed error message drivers/gpu/drm/rcar-du/rcar_du_drv.c | 4 +---

[PATCH 2/2 v2] drm: rcar-du: error message is not needed for EPROBE_DEFER

From: Kuninori Morimoto EPROBE_DEFER is not error, thus, error message on kernel log on this case is confusable. Print it only error cases Signed-off-by: Kuninori Morimoto --- v1 -> v2 - only for rcar_du_modeset_init() drivers/gpu/drm/rcar-du/rcar_du_drv.c | 3 ++- 1 file changed, 2 inserti

Re: [PATCH v3 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support

Hi Dirk, On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote: > Hi Simon, [...] > With Renesas R-Car3 we will get a whole family of SoCs. I.e. different > computing power (e.g. different number of Cores) with more or less similar > peripherals. > > I would think that we want to reflect t

Re: [PATCH] ARM: shmobile: rcar-gen2: Use ICRAM1 for jump stub on all SoCs

On Tue, May 17, 2016 at 05:15:33PM +0200, Geert Uytterhoeven wrote: > Currently the different SoCs in the R-Car Gen2 family use different > types of on-chip RAM for the jump stub: > - R-Car H2 uses Media RAM, > - R-Car M2-W uses another type of optional On-chip RAM, as it doesn't > have Med

[PATCH] rm64: dts: r8a7795: Drop 0x from unit address of gic

Drop 0x from unit address of gic as this is the desired form for a unit address. Signed-off-by: Simon Horman --- As suggested by Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/renesas/r8a7795

Re: [PATCH v3 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support

Hi Simon, On 25.05.2016 02:48, Simon Horman wrote: Hi Dirk, On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote: Hi Simon, [...] With Renesas R-Car3 we will get a whole family of SoCs. I.e. different computing power (e.g. different number of Cores) with more or less similar peripher

[PATCH 7/7] watchdog: softdog: improve coding style

From: Wolfram Sang Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c index 5e3a30b99d4415..b067edf246dff2 100644 --- a/drivers/watchdog/softdog.c +++ b/driv

[PATCH 4/7] watchdog: softdog: remove forward declaration

From: Wolfram Sang Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c index 0a29f5a0833787..42faa3d424d5ca 100644 --- a/drivers/watchdog/softdog.c +++ b/dr

[PATCH 6/7] watchdog: softdog: drop superfluous set_timeout callback

From: Wolfram Sang If we leave set_timeout empty, the core will do exactly what is implemented here anyway. Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c index ab0e02f

[PATCH 0/7] watchdog: softdog: cleanups

While working on another series where I need the softdog, this series already came out of it. It gets the driver prepared for the interesting stuff (coming later today hopefully) but is orthogonal from that. Buildbot is happy, branch is here: git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linu

[PATCH 2/7] watchdog: softdog: use watchdog core to init timeout value

From: Wolfram Sang Error string and comment say we fall back to a default, but in reality we bailed out. Refactor the code to use the core helper which then matches the described behaviour. While updating the init message anyhow, shorten it while we are here; no need for versioning there as well

[PATCH 1/7] watchdog: softdog: remove obsolete comments

From: Wolfram Sang The history is obsolete, especially since we switched to watchdog framework. The section markers also don't make sense anymore given the small size of the driver. Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 33 - 1 file change

[PATCH 5/7] watchdog: softdog: sort includes to avoid duplicates

From: Wolfram Sang Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c index 42faa3d424d5ca..ab0e02fc81a276 100644 --- a/drivers/watchdog/softdog.c +++ b

[PATCH 3/7] watchdog: softdog: consistently use softdog_ prefix

From: Wolfram Sang And move module_init/exit to the proper place while here. Signed-off-by: Wolfram Sang --- drivers/watchdog/softdog.c | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c index a9ad