Re: [PATCH 06/12] usb: dwc3: omap: Replace the extcon API

Hi Felipe, On 2016년 11월 30일 19:36, Felipe Balbi wrote: > > Hi, > > Chanwoo Choi writes: >> This patch uses the resource-managed extcon API for >> extcon_register_notifier() >> and replaces the deprecated extcon API as following: >> - extcon_get_cable_state_() ->

Re: [PATCH 05/12] usb: chipdata: Replace the extcon API

On Wed, Nov 30, 2016 at 02:57:33PM +0900, Chanwoo Choi wrote: > This patch uses the resource-managed extcon API for extcon_register_notifier() > and replaces the deprecated extcon API as following: > - extcon_get_cable_state_() -> extcon_get_state() > > Signed-off-by: Chanwoo Choi

Re: [RFC] mmc: tmio: use SDIO master interrupt bit only when allowed

On Fri, 02 Dec 2016 00:08:13 +0900, Wolfram Sang wrote: > > The master bit to enable SDIO interrupts can only be accessed if > SCLKDIVEN bit allows that. However, the core uses the SDIO enable > callback at times when SCLKDIVEN forbids the change. This leads to > "timeout waiting for SD bus idle"

[PATCH v2] pinctrl: sh-pfc: r8a7791: Add ADI pinconf support

Add pin configuration support for Gyro-ADC, named ADI on r8a7791 SoC. The Gyro-ADC supports three different configurations: a single ADC (adi and adi_b groups), 2 ADCs selectable through a single channel select signal (adi_chsel1 and adi_chsel1_b groups), up to 4 ADCs through 2 channel select

[PATCH 11/22] drm: bridge: dw-hdmi: Refactor hdmi_phy_configure resolution parameter

From: Kieran Bingham The current code hard codes the call of hdmi_phy_configure() to be 8bpp and provides extraneous error checking to verify that this hardcoded value is correct. Simplify the passing of the data by setting the parameter to be of the

[PATCH 17/22] drm: rcar-du: Skip disabled outputs

When a DT node connected to a DU output is disabled no bridge will ever be instantiated for it. Skip the output in that case. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_kms.c | 7 +++ 1 file changed, 7 insertions(+) diff

[PATCH 14/22] dt-bindings: display: dw-hdmi: Clean up DT bindings documentation

Make it clear that the core bridge/dw_hdmi.txt document isn't a device tree binding by itself but is meant to be referenced by platform device tree bindings, and update the Rockchip and Freescale DWC HDMI TX bindings to reference it. Signed-off-by: Laurent Pinchart

[PATCH 01/22] drm: bridge: dw-hdmi: Merge __hdmi_phy_i2c_write and hdmi_phy_i2c_write

The latter is just an int wrapper around the former void function that unconditionally returns 0. As the return value is never checked, merge the two functions into one. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 9 +

[PATCH 18/22] drm: rcar-du: Add DPLL support

From: Koji Matsuoka The implementation hardcodes a workaround for the H3 ES1.x SoC regardless of the SoC revision, as the workaround can be safely applied on all devices in the Gen3 family without any side effect. Signed-off-by: Koji Matsuoka

[PATCH 12/22] drm: bridge: dw-hdmi: Abstract the platform PHY configuration

From: Kieran Bingham Platforms implement the dw-hdmi with a separate PHY entity. It is configured over it's own I2C bus. To allow for different PHY's to be configured from the dw-hdmi driver, abstract the actual programming of the PHY to its own

[PATCH 00/22] R-Car Gen3 HDMI output support

Hello, This patch series implements support for the HDMI output on Renesas R-Car Gen3 SoCs, and more specifically on the R-Car H3. R-Car Gen3 SoCs include one or multiple Synopsys DWC HDMI TX controllers. The series thus starts with 13 cleanup or feature patches for the dw-hdmi driver. Patches

[PATCH 20/22] arm64: dts: r8a7795: Add HDMI encoder support

From: Ulrich Hecht Add DT nodes for the two HDMI encoders in disabled state. Based on work by Koji Matsuoka. Signed-off-by: Ulrich Hecht Signed-off-by: Laurent Pinchart ---

[PATCH 15/22] dt-bindings: display: renesas: Add R-Car Gen3 HDMI TX DT bindings

The Renesas R-Car Gen3 SoCs use a Synopsys DWC HDMI TX encoder IP. Add corresponding device tree bindings based on the DWC HDMI TX bindings model. Signed-off-by: Laurent Pinchart --- .../bindings/display/bridge/renesas,dw-hdmi.txt| 75

[PATCH 16/22] drm: rcar-du: Add Gen3 HDMI encoder support

From: Koji Matsuoka The R-Car Gen3 SoCs include on-chip DesignWare HDMI encoders. Support them with a platform driver to provide platform glue data to the dw-hdmi driver. The driver is a complete rewrite of code coming from the Renesas BSP, save for the values in

[PATCH 02/22] drm: bridge: dw-hdmi: Remove unneeded arguments to bind/unbind functions

The master argument isn't used. The data argument, a void pointer, is used by the bind function only where it's cast to a drm_device pointer, which can easily be obtained from the encoder argument instead. Remove them. Signed-off-by: Laurent Pinchart

[PATCH 09/22] drm: bridge: dw-hdmi: Create connector in the bridge attach operation

The DRM device is not guaranteed by the bridge API to be available before the attach callback. The driver performs properly at the moment as it doesn't use the drm_bridge_add() registration method. As this will be changed later, move connector creation to attach time to ensure compatibility with

[PATCH 06/22] drm: bridge: dw-hdmi: Don't forward HPD events to DRM core before attach

Hotplug events should only be forwarded to the DRM core by the interrupt handler when the bridge has been attached, otherwise the DRM device pointer will be NULL, resulting in a crash. Signed-off-by: Laurent Pinchart ---

[PATCH 13/22] drm: bridge: dw-hdmi: Replace device type with platform quirks

From: Kieran Bingham The dw-hdmi driver declares a dev_type to distinguish platform specific changes. Replace this with a quirk field, so that the platform can specify the required quirks for the driver, rather than the driver becoming conditional on

[PATCH 07/22] drm: bridge: dw-hdmi: Move IRQ and IO resource allocation to common code

There's no need to duplicate identical code in multiple drivers (two at the moment, one more to come soon). Move it to the dw-hdmi core where it can be shared. If resource allocation ever becomes device-specific later we'll always have the option of splitting it out again. While it at pass the

[PATCH 08/22] drm: bridge: dw-hdmi: Reorder functions to prepare for next commit

The next commit will reference structures and functions in a way that currently requires forward declarations. Reorder the functions to avoid that. No functional change to the code is performed. Signed-off-by: Laurent Pinchart ---

[PATCH 19/22] drm: rcar-du: Add HDMI outputs to R8A7795 device description

From: Koji Matsuoka Update the device description with the two available HDMI outputs. Signed-off-by: Koji Matsuoka Signed-off-by: Laurent Pinchart ---

[PATCH 21/22] arm64: dts: r8a7795: salvator-x: Enable HDMI outputs

From: Koji Matsuoka Instantiate the HDMI connectors and enable the encoders. Signed-off-by: Koji Matsuoka Signed-off-by: Ulrich Hecht Signed-off-by: Laurent Pinchart

[PATCH 22/22] arm64: dts: r8a7795: salvator-x: Add DU1 and DU2 external dot clocks

The DU1 and DU2 external dot clocks are fixed frequency clock generators running at 33MHz. Signed-off-by: Laurent Pinchart --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 23 ++ 1 file changed, 23 insertions(+) diff --git

[PATCH 04/22] drm: bridge: dw-hdmi: Embed drm_bridge in struct dw_hdmi

The drm_bridge instance is always needed, there's no point in allocating it separately. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git

[PATCH 10/22] drm: bridge: dw-hdmi: Implement DRM bridge registration

As an option for drivers not based on the component framework, register the bridge with the DRM core with the DRM bridge API. Existing drivers based on dw_hdmi_bind() and dw_hdmi_unbind() are not affected as those functions are preserved with their current behaviour. Signed-off-by: Laurent

[PATCH 05/22] drm: bridge: dw-hdmi: Remove encoder field from struct dw_hdmi

The field isn't needed, remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/dw-hdmi.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/bridge/dw-hdmi.c b/drivers/gpu/drm/bridge/dw-hdmi.c

[PATCH v3] pinctrl: sh-pfc: r8a7791: Add ADI pinconf support

Add pin configuration support for Gyro-ADC, named ADI on r8a7791 SoC. Signed-off-by: Jacopo Mondi --- Compiled only, not tested with an actual ADC. For reference only, these are the changes introduced by Geert's private review of first sketch of this patch: * separate ADI

[PATCH v4 4/4] arm64: dts: r8a7796: Add R-Car Gen3 thermal support

Signed-off-by: Hien Dang Signed-off-by: Thao Nguyen Signed-off-by: Khiem Nguyen Signed-off-by: Wolfram Sang --- arch/arm64/boot/dts/renesas/r8a7796.dtsi | 58

[PATCH v4 2/4] thermal: rcar_gen3_thermal: Add R-Car Gen3 thermal driver

Add support for R-Car Gen3 thermal sensors. Polling only for now, interrupts will be added incrementally. Same goes for reading fuses. This is documented already, but no hardware available for now. Signed-off-by: Hien Dang Signed-off-by: Thao Nguyen

[PATCH v4 3/4] arm64: dts: r8a7795: Add R-Car Gen3 thermal support

Signed-off-by: Hien Dang Signed-off-by: Thao Nguyen Signed-off-by: Khiem Nguyen Signed-off-by: Wolfram Sang --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 58

[PATCH v4 1/4] thermal: rcar_gen3_thermal: Document the R-Car Gen3

Signed-off-by: Hien Dang Signed-off-by: Khiem Nguyen Signed-off-by: Wolfram Sang --- .../bindings/thermal/rcar-gen3-thermal.txt | 56 ++ 1 file changed, 56 insertions(+) create

[PATCHv2 4/5] tests: Test suspend/resume on idle pipelines

From: Kieran Bingham Provide a test to verify the hardware is functional both before and after entering a suspend / resume cycle. Make use of the /sys/power/pm_test functionality provided by CONFIG_PM_DEBUG to perform the testing Signed-off-by: Kieran Bingham

[PATCHv2 3/5] logger: Log to the FTrace buffer if tracing is enabled

From: Kieran Bingham Extend the logger such that it will detect the tracing system, and also append print statement to this ring buffer. This provides the relevant logging output interspersed in the ftrace logs for an effective solution to identifying the

[PATCHv2 0/5] VSP-Tests: Add suspend resume tests and helpers

From: Kieran Bingham Following on from previous useful feedback, I have reworked the supporting scripts and tests. Provide two tests for suspend/resume cycles. One will verify the VSP1 is functional with a test before and after a suspend cycle. The other will

[PATCHv2 1/5] scripts: Test suite runner

From: Kieran Bingham Provide a utility script to execute all vsp unit tests, as well as the option to execute multiple iterations of the suite. Signed-off-by: Kieran Bingham --- v2 - remove spurious uses of ';' - fix output

[PATCHv2 2/5] scripts: Provide bin2png.sh helper

From: Kieran Bingham Identify the size and format from the test output filename, and pass to raw2rgbpnm for conversion to a PNM file. >From there we can convert easily to a PNG output file. Signed-off-by: Kieran Bingham ---

[PATCHv2 5/5] tests: Test suspend/resume on active pipelines

From: Kieran Bingham Provide a test to verify the hardware completes a functional test whilst performing a suspend resume cycle in parallel. Make use of the /sys/power/pm_test functionality provided by CONFIG_PM_DEBUG to perform the testing Signed-off-by: Kieran

Re: [patch] net: renesas: ravb: unintialized return value

Hello! On 12/01/2016 11:57 PM, Dan Carpenter wrote: We want to set the other "err" variable here so that we can return it later. My version of GCC misses this issue but I caught it with a static checker. Fixes: 9f70eb339f52 ("net: ethernet: renesas: ravb: fix fixed-link phydev leaks")

[patch] net: renesas: ravb: unintialized return value

We want to set the other "err" variable here so that we can return it later. My version of GCC misses this issue but I caught it with a static checker. Fixes: 9f70eb339f52 ("net: ethernet: renesas: ravb: fix fixed-link phydev leaks") Signed-off-by: Dan Carpenter ---

RE: [PATCH v2] sh_eth: remove unchecked interrupts

Hi Geert, On 12/1/2016, Sergei Shtylyov wrote: > > On 12/01/2016 05:42 PM, Geert Uytterhoeven wrote: > > >> --- a/drivers/net/ethernet/renesas/sh_eth.c > >> +++ b/drivers/net/ethernet/renesas/sh_eth.c > >> @@ -518,7 +518,7 @@ static struct sh_eth_cpu_data r7s72100_data = { > >> > >>

[PATCH v3] sh_eth: remove unchecked interrupts for RZ/A1

When streaming a lot of data and the RZ/A1 can't keep up, some status bits will get set that are not being checked or cleared which cause the following messages and the Ethernet driver to stop working. This patch fixes that issue. irq 21: nobody cared (try booting with the "irqpoll" option)

Re: [PATCH v2] sh_eth: remove unchecked interrupts

On 12/01/2016 09:24 PM, Chris Brandt wrote: One thing you've missed so far is mentioning R7S72100 (RZ/A1) in the subject. This driver supports many SoCs, you're only fixing one of them... For the last sh_eth.c patch I submitted, I had: "net: ethernet: renesas: sh_eth: add POST registers

RE: [PATCH v2] sh_eth: remove unchecked interrupts

On 12/1/2016, Sergei Shtylyov wrote: > One thing you've missed so far is mentioning R7S72100 (RZ/A1) in the > subject. This driver supports many SoCs, you're only fixing one of them... For the last sh_eth.c patch I submitted, I had: "net: ethernet: renesas: sh_eth: add POST registers for rz"

Re: [PATCH] pinctrl: sh-pfc: r8a7791: Add ADI pinconf support

Hi Laurent, Geert, thanks for review On 29/11/2016 22:39, Geert Uytterhoeven wrote: Hi Laurent, On Tue, Nov 29, 2016 at 8:30 PM, Laurent Pinchart wrote: On Tuesday 29 Nov 2016 10:11:56 Jacopo Mondi wrote: Add pin configuration support for Gyro-ADC,

Re: [PATCH v2] sh_eth: remove unchecked interrupts

On 12/01/2016 08:36 PM, Sergei Shtylyov wrote: When streaming a lot of data and the RZ can't keep up, some status bits will get set that are not being checked or cleared which cause the following messages and the Ethernet driver to stop working. This patch fixes that issue. irq 21: nobody

Re: [PATCH v2] sh_eth: remove unchecked interrupts

On 12/01/2016 05:42 PM, Geert Uytterhoeven wrote: --- a/drivers/net/ethernet/renesas/sh_eth.c +++ b/drivers/net/ethernet/renesas/sh_eth.c @@ -518,7 +518,7 @@ static struct sh_eth_cpu_data r7s72100_data = { .ecsr_value = ECSR_ICD, .ecsipr_value = ECSIPR_ICDIP, -

Re: [PATCH v2] sh_eth: remove unchecked interrupts

On 12/01/2016 05:06 PM, Chris Brandt wrote: When streaming a lot of data and the RZ can't keep up, some status bits will get set that are not being checked or cleared which cause the following messages and the Ethernet driver to stop working. This patch fixes that issue. irq 21: nobody cared

Re: [PATCH/RFC v2 i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

On Thu, Dec 01, 2016 at 04:55:13PM +0100, Geert Uytterhoeven wrote: > Hi Simon, > > On Thu, Dec 1, 2016 at 4:41 PM, Simon Horman > wrote: > > In the case of Renesas R-Car hardware we know that there are generations of > > SoCs, e.g. Gen 2 and Gen 3. But beyond that

[PATCH pci/next] PCI: rcar: Add gen3 fallback compatibility string for pcie-rcar

Add fallback compatibility string for the R-Car Gen 3 family. This is in keeping with the both the existing fallback compatibility string for the R-Car Gen 2 family and the fallback scheme being adopted wherever appropriate for drivers for Renesas SoCs. Signed-off-by: Simon Horman

Re: [PATCH/RFC v2 i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

Hi Simon, On Thu, Dec 1, 2016 at 4:41 PM, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP blocks might be. For example, I

[PATCH/RFC v2 i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant

Re: [PATCH/RFC i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

On Thu, Dec 01, 2016 at 04:18:14PM +0100, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP blocks might be. For example, I believe that > r8a7790 is older

Re: [PATCH/RFC i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

Hi Simon, On Thu, Dec 1, 2016 at 4:18 PM, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP blocks might be. For example, I

[PATCH/RFC i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant

[RFC] mmc: tmio: use SDIO master interrupt bit only when allowed

The master bit to enable SDIO interrupts can only be accessed if SCLKDIVEN bit allows that. However, the core uses the SDIO enable callback at times when SCLKDIVEN forbids the change. This leads to "timeout waiting for SD bus idle" messages. We now activate the master bit in probe once if SDIO is

Re: mmc: tmio: why enable/disable SDIO irq on every transaction with IOMOD?

Hi, > Is Arnd Hannemann, the author, around these days by any chance? According to git history, he is sending a patch occasionally, but all his SH involvement was from 2010. I don't know him. > We don't have it yet. A question we have is that where should we > enable / disable the IOMOD? I

Re: [PATCH 0/4] ARM, arm64: dts: Use usb-phy fallback bindings

On Thu, Dec 1, 2016 at 3:25 PM, Simon Horman wrote: > this short series makes use of fallback bindings for Renesas R-Car PHY > drivers in the DT of SoCs which already use those drivers. > > Simon Horman (4): > ARM: dts: r8a7790: Use renesas,rcar-gen2-usb-phy fallback

Re: [PATCH v2] sh_eth: remove unchecked interrupts

Hi Chris, On Thu, Dec 1, 2016 at 3:06 PM, Chris Brandt wrote: > --- a/drivers/net/ethernet/renesas/sh_eth.c > +++ b/drivers/net/ethernet/renesas/sh_eth.c > @@ -518,7 +518,7 @@ static struct sh_eth_cpu_data r7s72100_data = { > > .ecsr_value = ECSR_ICD, >

Re: [PATCH] PM / Domains: Do not print PM domain add error message if EPROBE_DEFER

On Wednesday, November 30, 2016 01:24:56 PM Geert Uytterhoeven wrote: > EPROBE_DEFER is not an error, hence printing an error message like > > renesas_irqc e61c.interrupt-controller: failed to add to PM domain > always-on: -517 > > may confuse the user. > > Suppress the error message

[PATCH 2/4] 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 --- arch/arm/boot/dts/r8a7791.dtsi | 3

[PATCH 4/4] 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 ---

[PATCH 1/4] 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 --- arch/arm/boot/dts/r8a7790.dtsi | 3

[PATCH 0/4] ARM, arm64: dts: Use usb-phy fallback bindings

Hi, this short series makes use of fallback bindings for Renesas R-Car PHY drivers in the DT of SoCs which already use those drivers. Simon Horman (4): ARM: dts: r8a7790: Use renesas,rcar-gen2-usb-phy fallback binding ARM: dts: r8a7791: Use renesas,rcar-gen2-usb-phy fallback binding ARM:

[PATCH v2] sh_eth: remove unchecked interrupts

When streaming a lot of data and the RZ can't keep up, some status bits will get set that are not being checked or cleared which cause the following messages and the Ethernet driver to stop working. This patch fixes that issue. irq 21: nobody cared (try booting with the "irqpoll" option)

Re: [PATCH] pinctrl: sh-pfc: r8a7793: Implement voltage switching for SDHI

On Thu, Dec 1, 2016 at 2:21 PM, Simon Horman wrote: > Voltage switching is the same as on the r8a7791. > > Cc: Wolfram Sang > Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven

Re: [PATCH] pinctrl: sh-pfc: r8a7793: Implement voltage switching for SDHI

On Thu, Dec 01, 2016 at 02:21:07PM +0100, Simon Horman wrote: > Voltage switching is the same as on the r8a7791. > > Cc: Wolfram Sang > Signed-off-by: Simon Horman Reviewed-by: Wolfram Sang

[PATCH] pinctrl: sh-pfc: r8a7793: Implement voltage switching for SDHI

Voltage switching is the same as on the r8a7791. Cc: Wolfram Sang Signed-off-by: Simon Horman --- Based on sh-pfc-for-v4.10-tag2 --- drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH] can: rcar_canfd: Correct order of interrupt specifiers

On 11/23/2016 02:44 PM, Geert Uytterhoeven wrote: > According to both DTS (example and actual files), and Linux driver code, > the first interrupt specifier should be the Channel interrupt, while the > second interrupt specifier should be the Global interrupt. > > Signed-off-by: Geert

RE: [PATCH] sh_eth: add missing checks for status bits

On 12/1/2016, Sergei Shtylyov wrote: > Hello! > > Please always CC me on the sh_eth/ravb driver patches as directed by > scripts/get_maintainer.pl. OK. I'm sorry. > On 11/30/2016 11:01 PM, Chris Brandt wrote: > > > When streaming a lot of data and the RZ can't keep up, some status > >

Re: mmc: tmio: why enable/disable SDIO irq on every transaction with IOMOD?

Hi Wolfram, On Thu, 01 Dec 2016 19:46:22 +0900, Wolfram Sang wrote: > > > > So my question is that "What is the reason behind to disable IRQ with > > > SDIO_MODE? Is there any situation which masking with SDIO_INFO1_MASK > > > is not enough? > > The code was introduced with 845ecd20239c28

Re: mmc: tmio: why enable/disable SDIO irq on every transaction with IOMOD?

Hi, thanks for the report and thanks to Ulf for forwarding. Adding renesas-soc list, too. > > So my question is that "What is the reason behind to disable IRQ with > > SDIO_MODE? Is there any situation which masking with SDIO_INFO1_MASK > > is not enough? This code predates the time since I

Re: [PATCH] arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins

Hi Niklas, On Thu, Dec 1, 2016 at 11:29 AM, Niklas Söderlund wrote: > On 2016-12-01 10:13:56 +0100, Geert Uytterhoeven wrote: >> On Mon, Nov 28, 2016 at 12:46 PM, Niklas Söderlund >> > diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts >> >

Re: [PATCH] Platform: vsp1: Clean up file handle in open() error path.

Hi Shailendra, Thank you for the patch. On Thursday 01 Dec 2016 10:20:18 Shailendra Verma wrote: > v4l2_fh_init is already done.So call the v4l2_fh_exit in error condition > before returing from the function. > > Signed-off-by: Shailendra Verma Reviewed-by: Laurent

Re: [PATCH] arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins

Hi Geert, Thanks for your feedback. On 2016-12-01 10:13:56 +0100, Geert Uytterhoeven wrote: > Hi Niklas, > > On Mon, Nov 28, 2016 at 12:46 PM, Niklas Söderlund > wrote: > > The EthernetAVB should not depend on the bootloader to setup correct > >

Re: [PATCH] sh_eth: add missing checks for status bits

Hello! Please always CC me on the sh_eth/ravb driver patches as directed by scripts/get_maintainer.pl. On 11/30/2016 11:01 PM, Chris Brandt wrote: When streaming a lot of data and the RZ can't keep up, some status bits will get set that are not being checked or cleared which cause the

Re: [PATCH] sh_eth: add missing checks for status bits

Hello! On 12/1/2016 11:52 AM, Simon Horman wrote: When streaming a lot of data and the RZ can't keep up, some status bits will get set that are not being checked or cleared which cause the following messages and the Ethernet driver to stop working. This patch fixes that issue. irq 21: nobody

Re: [PATCH] arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins

Hi Niklas, On Mon, Nov 28, 2016 at 12:46 PM, Niklas Söderlund wrote: > The EthernetAVB should not depend on the bootloader to setup correct > drive-strength values. Values for drive-strength where found by examine examining > the registers after the

Re: [GIT PULL] Renesas ARM Based SoC Match Updates for v4.10

On Thursday, December 1, 2016 9:47:58 AM CET Simon Horman wrote: > Thanks for pulling this and other outstanding pull requests from Geert and > myself. I don't think we have anything more outstanding at this time. Ok, thanks for the confirmation! Arnd

[PATCH] arm64: dts: h3ulcb: Provide sd0_uhs node

Provide separaate sd0 and sd0_uhs nodes rather than duplicate sd0 nodes. Cc: Vladimir Barinov Cc: Sergei Shtylyov Fixes: 93373c309a70 ("arm64: dts: h3ulcb: rename SDHI0 pins") Signed-off-by: Simon Horman

Re: [PATCH] pinctrl: sh-pfc: r8a7791: Add ADI pinconf support

Hi Jacopo, On Tue, Nov 29, 2016 at 10:11 AM, Jacopo Mondi wrote: > Add pin configuration support for Gyro-ADC, named ADI on r8a7791 SoC. > > The Gyro-ADC supports three different configurations: > a single ADC (adi and adi_b groups), 2 ADCs selectable through a single >

Re: [PATCH] sh_eth: add missing checks for status bits

On Wed, Nov 30, 2016 at 03:01:48PM -0500, Chris Brandt wrote: > When streaming a lot of data and the RZ can't keep up, some status bits > will get set that are not being checked or cleared which cause the > following messages and the Ethernet driver to stop working. This > patch fixes that issue.

Re: [GIT PULL] Renesas ARM Based SoC Match Updates for v4.10

On Wed, Nov 30, 2016 at 04:50:20PM +0100, Arnd Bergmann wrote: > On Wednesday, November 23, 2016 9:13:31 PM CET Simon Horman wrote: > > This pull request is based on the pull request "soc_device_match() > > interface for matching against soc_bus attributes" sent by Geert > > Uytterhoeven which