[PATCH 4/5] arch: sh: ms7724se: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver is ms7724se board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 and CEU1 with no active video subdevices. Memory for the CEU video buffers is now reserved with membocks APIs and

[PATCH 1/5] media: i2c: Copy rj54n1cb0c soc_camera sensor driver

Copy the soc_camera based driver in v4l2 sensor driver directory. This commit just copies the original file without modifying it. No modification to KConfig and Makefile as soc_camera framework dependencies need to be removed first in next commit. Signed-off-by: Jacopo Mondi

[PATCH 5/5] arch: sh: ap325rxa: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in ap325rxa board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 with a single video sensor (ov7725). Memory for the CEU video buffers is now reserved with membocks APIs and need

[PATCH 2/5] media: i2c: rj54n1: Remove soc_camera dependencies

Remove soc_camera framework dependencies from rj54n1 sensor driver. - Handle clock - Handle GPIOs (named 'powerup' and 'enable') - Register the async subdevice - Remove g/s_mbus_config as they're deprecated. - Adjust build system - List the driver as maintained for 'Odd Fixes' as I don't have HW

[PATCH 3/5] arch: sh: kfr2r09: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in kfr2r09 board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and move clk and gpio handling away from board file, registering the clock source and the enable gpios for driver consumption.

[PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh

Hello, this series removes dependencies on the soc_camera based sh_mobile_ceu_camera driver from 3 board files in arch/sh and from one sensor driver used by one of those boards. Hans, this means there are no more user of the soc_camera framework that I know of in Linux, and I guess we can now

[PATCH v2] arm64: dts: renesas: Add sdhi2_ds pin group to SDHI2 pinctrl groups

From: Masaharu Hayakawa This patch adds definitions for configuration of the power-source, drive-strength, etc... for the SD2_DS pin for Salvator-X(S) and ULCB boards. Signed-off-by: Masaharu Hayakawa Signed-off-by: Takeshi Kihara [wsa: fixed for ULCB boards, too] Signed-off-by: Wolfram Sang

[PATCH v2] arm64: dts: salvator-x(s): Update I2C ch4 clock to 400kHz

From: Takeshi Kihara Any of the following devices connected to I2C ch4 of the Salvator-X(S) boards will operate at 400 kHz: PCA9654, 9FGV0841, ADV7482WBBCZ, MAX9611, 5P49V5923, 5P49V6901A This patch updates the clock frequency to 400 KHz. Signed-off-by: Takeshi Kihara [wsa: squashed

Re: [PATCH v3] vfio: platform: Fix using devices in PM Domains

Hi Geert, On 05/28/2018 05:26 PM, Geert Uytterhoeven wrote: > If a device is part of a PM Domain (e.g. power and/or clock domain), its > power state is managed using Runtime PM. Without Runtime PM, the device > may not be powered up or clocked, causing subtle failures, crashes, or > system

[PATCH v3 0/2] Add R8A77980/Condor I2C support

Hello! Here's the set of 2 patches against Simon Horman's 'renesas.git' repo's 'renesas-devel-20180528-v4.17-rc7' tag. We're adding the R8A77980 I2C nodes and then describing 2 PCA9654 I/O expanders connected to the I2C0 bus on the Condor board. [1/2] arm64: dts: renesas: r8a77980: add I2C

[PATCH] i2c: rcar: document R8A77980 bindings

R-Car V3H (R8A77980) SoC also has the R-Car gen3 compatible I2C controller, so document the SoC specific bindings. Signed-off-by: Sergei Shtylyov --- The patch is against Wolfram Sang's 'linux.git' repo's 'i2c/for-next' branch but I wouldn't mind if it was applied to the 'i2c/for-current'

[PATCH 1/2] arm64: dts: renesas: r8a77980: add I2C support

Define the generic R8A77980 parts of the I2C[0-5] device node. Based on the original (and large) patch by Vladimir Barinov. Signed-off-by: Vladimir Barinov Signed-off-by: Sergei Shtylyov --- arch/arm64/boot/dts/renesas/r8a77980.dtsi | 111 ++ 1 file changed, 111

[PATCH 2/2] arm64: dts: renesas: condor: add I2C0 support

Define the Condor board dependent part of the I2C0 device node. The I2C0 bus is populated by 2 ON Semiconductor PCA9654 I/O expanders and Analog Devices ADV7511W HDMI transmitter (but we're only describing the former chips now). Signed-off-by: Sergei Shtylyov ---

Re: [PATCH v3 0/2] Add R8A77980/Condor I2C support

Sorry, "v3" shouldn't be there in the subject...

Re: [PATCH v3] vfio: platform: Fix using devices in PM Domains

Hi Eric, On Mon, May 28, 2018 at 10:27 PM, Auger Eric wrote: > On 05/28/2018 05:26 PM, Geert Uytterhoeven wrote: >> If a device is part of a PM Domain (e.g. power and/or clock domain), its >> power state is managed using Runtime PM. Without Runtime PM, the device >> may not be powered up or

[PATCH v2] dt-bindings: media: rcar_vin: fix style for ports and endpoints

The style for referring to ports and endpoint are wrong. Refer to them using lowercase and a unit address, port@x and endpoint@x. Signed-off-by: Niklas Söderlund Reported-by: Geert Uytterhoeven Reviewed-by: Rob Herring --- * Changes since v1. - Fixed spelling reported by Sergei,

[PATCH v2] rcar-vin: sync which hardware buffer to start capture from

When starting the VIN capture procedure we are not guaranteed that the first buffer written to is VnMB1 to which we assigned the first buffer queued. This is problematic for two reasons. Buffers might not be dequeued in the same order they where queued for capture. Future features planed for the

[PATCH v2] media: rcar-vin: enable support for r8a77965

Add the SoC specific information for Renesas r8a77965. Signed-off-by: Niklas Söderlund Reviewed-by: Laurent Pinchart --- * Changes since v1 - Fixed typo in variable name, s/_rcar_info_r8a77965_routes/rcar_info_r8a77965_routes/. - Collected Laurents tag. ---

Re: [RFC PATCH v2 1/2] drm: Add generic colorkey properties

On 28.05.2018 16:15, Ville Syrjälä wrote: > On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote: >> Color keying is the action of replacing pixels matching a given color >> (or range of colors) with transparent pixels in an overlay when >> performing blitting. Depending on the hardware

Re: [RFC PATCH v2 1/2] drm: Add generic colorkey properties

On 29.05.2018 02:48, Dmitry Osipenko wrote: > inversion=true" if mask has form of 0x11000111, though this could be not For clarity: I meant s/0x11000111/0xFF000FFF/.

Re: [PATCH v2 10/11] arm64: dts: r8a77965-salvator-x: Enable DU external clocks and HDMI

Hi Geert > > +_con { > > + remote-endpoint = <_dw_hdmi0_out>; > > +}; > > I think the hdmi0 and hdmi0_con parts can be moved to salvator-common.dtsi. > Can we do that now (with stubs?), or does this have to wait until r8a77965 has > received HDMI sound support? HDMI sound doesn't use

RE: [PATCH v5] usb: gadget: udc: renesas_usb3: Add register of usb role switch

Hi Andy, Thank you for your review! > From: Andy Shevchenko, Sent: Monday, May 28, 2018 9:47 PM > > On Fri, May 25, 2018 at 10:12 AM, Yoshihiro Shimoda > wrote: > > > -static void usb3_set_mode(struct renesas_usb3 *usb3, bool host) > > Wouldn't be better to choose another name for a new

RE: [PATCH v5] usb: gadget: udc: renesas_usb3: Add register of usb role switch

Hi Heikki, > From: Heikki Krogerus, Sent: Monday, May 28, 2018 10:05 PM > > On Fri, May 25, 2018 at 04:12:56PM +0900, Yoshihiro Shimoda wrote: > > @@ -2573,6 +2635,12 @@ static void renesas_usb3_init_ram(struct > > renesas_usb3 *usb3, struct device *dev, > > EXTCON_NONE, > > }; > > > >

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

Hi Simon, On Monday, 28 May 2018 12:39:17 EEST Simon Horman wrote: > On Fri, May 25, 2018 at 01:23:53PM +0300, Laurent Pinchart wrote: > > On Friday, 25 May 2018 13:13:20 EEST Simon Horman wrote: > >> On Thu, May 24, 2018 at 11:00:52AM +0300, Laurent Pinchart wrote: > >>> On Wednesday, 21

Re: [PATCH 3/6] ravb: remove custom .set_link_ksettings from ethtool ops

Hello Sergei, On 05/26/2018 10:50 PM, Sergei Shtylyov wrote: > On 05/24/2018 02:11 PM, Vladimir Zapolskiy wrote: > >> The change replaces a custom implementation of .set_link_ksettings >> callback with a shared phy_ethtool_set_link_ksettings(), this fixes >> sleep in atomic context bug, which is

Re: [PATCH 13/15] arm: dts: r8a7743: Add missing OPP properties for CPUs

On Mon, May 28, 2018 at 04:28:31PM +0530, Viresh Kumar wrote: > On 28-05-18, 11:23, Simon Horman wrote: > > [Cc Biju Das] > > > > On Fri, May 25, 2018 at 04:01:59PM +0530, Viresh Kumar wrote: > > > The OPP properties, like "operating-points", should either be present > > > for all the CPUs of a

Re: [PATCH v4 2/4] mmc: core: more fine-grained hooks for HS400 tuning

On Tue, May 22, 2018 at 04:32:09PM +0200, Ulf Hansson wrote: > On 18 April 2018 at 11:56, Simon Horman wrote: > > This adds two new HS400 tuning operations: > > * prepare_hs400_tuning_downgrade > > * complete_hs400_tuning > > > > These supplement the existing HS400

Re: [PATCH v5] usb: gadget: udc: renesas_usb3: Add register of usb role switch

On Fri, May 25, 2018 at 04:12:56PM +0900, Yoshihiro Shimoda wrote: > @@ -2573,6 +2635,12 @@ static void renesas_usb3_init_ram(struct renesas_usb3 > *usb3, struct device *dev, > EXTCON_NONE, > }; > > +static struct usb_role_switch_desc renesas_usb3_role_switch_desc = { You can constify

[PATCH] arm64: dts: renesas: r8a77965: Add all HSCIF nodes

From: Takeshi Kihara Based on a similar patch of the R8A7796 device tree by Ulrich Hecht . Signed-off-by: Takeshi Kihara Signed-off-by: Geert Uytterhoeven ---

Re: [PATCH 13/15] arm: dts: r8a7743: Add missing OPP properties for CPUs

On 28-05-18, 11:23, Simon Horman wrote: > [Cc Biju Das] > > On Fri, May 25, 2018 at 04:01:59PM +0530, Viresh Kumar wrote: > > The OPP properties, like "operating-points", should either be present > > for all the CPUs of a cluster or none. If these are present only for a > > subset of CPUs of a

Re: [PATCH] arm64: dts: r8a77965: Add Watchdog Timer controller node using RCLK Watchdog Timer

Hi Kaneko-san, (after adding more coffee) The summary prefix should be "arm64: dts: renesas: r8a77965:" On Mon, May 28, 2018 at 11:32 AM, Geert Uytterhoeven wrote: > On Wed, May 23, 2018 at 2:36 PM, Yoshihiro Kaneko > wrote: >> From: Takeshi

Re: [PATCH v5] usb: gadget: udc: renesas_usb3: Add register of usb role switch

On Fri, May 25, 2018 at 10:12 AM, Yoshihiro Shimoda wrote: > -static void usb3_set_mode(struct renesas_usb3 *usb3, bool host) Wouldn't be better to choose another name for a new function? > + struct renesas_usb3 *usb3 = container_of(work, struct

[PATCH] pinctrl: sh-pfc: r8a77965: Add HSCIF pins, groups, and functions

From: Takeshi Kihara This patch adds HSCIF{0,1,2,3,4} pins, groups and functions to the R8A77965 SoC. Signed-off-by: Takeshi Kihara Signed-off-by: Geert Uytterhoeven --- To be queued in sh-pfc-for-v4.19.

Re: [RFC PATCH v2 1/2] drm: Add generic colorkey properties

On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote: > Color keying is the action of replacing pixels matching a given color > (or range of colors) with transparent pixels in an overlay when > performing blitting. Depending on the hardware capabilities, the > matching pixel can either

[PATCH] arm64: dts: renesas: r8a77965: Use r8a77965-cpg-mssr binding definitions

Replace the hardcoded clock indices by R8A77965_CLK_* symbols. Signed-off-by: Geert Uytterhoeven --- Commit 7ce36da900c0a2ff ("clk: renesas: cpg-mssr: Add support for R-Car M3-N") providing the definitions is in v4.17-rc1. arch/arm64/boot/dts/renesas/r8a77965.dtsi | 12

[PATCH v3] vfio: platform: Fix using devices in PM Domains

If a device is part of a PM Domain (e.g. power and/or clock domain), its power state is managed using Runtime PM. Without Runtime PM, the device may not be powered up or clocked, causing subtle failures, crashes, or system lock-ups when the device is accessed by the guest. Fix this by adding

[PATCH/RFC] arm64: dts: renesas: salvator-common: Add HSCIF1 device support

From: Hiromitsu Yamasaki This patch adds the pin control for HSCIF1, and supports connection with the Debug Serial-1 (CN26) on Salvator boards. SCIF1 and HSCI1 are sharing the pin connected to the Debug Serial-1 (CN26) on Salvator boards, and it is necessary

Re: [PATCH v4 5/9] media: rcar-vin: Parse parallel input on Gen3

Hi Jacopo, On 2018-05-25 13:50:08 +0200, Jacopo Mondi wrote: > Hi Niklas, >I might have another question before sending v5. > > On Fri, May 25, 2018 at 12:29:44AM +0200, Niklas Söderlund wrote: > > Hi Jacopo, > > > > Thanks for your work. > > > > I really like what you did with this patch in

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

On Mon, May 28, 2018 at 12:45:32PM +0300, Laurent Pinchart wrote: > Hi Simon, > > On Monday, 28 May 2018 12:39:17 EEST Simon Horman wrote: > > On Fri, May 25, 2018 at 01:23:53PM +0300, Laurent Pinchart wrote: > > > On Friday, 25 May 2018 13:13:20 EEST Simon Horman wrote: > > >> On Thu, May 24,

Re: [PATCH v2] vfio: platform: Fix using devices in PM Domains

Hi Geert, On 05/18/2018 12:55 PM, Geert Uytterhoeven wrote: > If a device is part of a PM Domain (e.g. power and/or clock domain), its > power state is managed using Runtime PM. Without Runtime PM, the device > may not be powered up or clocked, causing subtle failures, crashes, or > system

Re: [PATCH v2] vfio: platform: Fix using devices in PM Domains

Hi Eric, On Mon, May 28, 2018 at 4:54 PM, Auger Eric wrote: > On 05/18/2018 12:55 PM, Geert Uytterhoeven wrote: >> If a device is part of a PM Domain (e.g. power and/or clock domain), its >> power state is managed using Runtime PM. Without Runtime PM, the device >> may

[PATCH] media: vsp1: Document vsp1_dl_body refcnt

In commit 2d9445db0ee9 ("media: vsp1: Use reference counting for bodies"), a new field was introduced to the vsp1_dl_body structure to account for usage tracking of the body. Document the newly added field in the kerneldoc. Signed-off-by: Kieran Bingham ---

Re: [GIT PULL] Renesas ARM64 Based SoC DT Updates for v4.18

Hi Olof, On Sat, May 26, 2018 at 02:14:20PM -0700, Olof Johansson wrote: > Hi Simon, > > On Fri, May 18, 2018 at 01:16:00PM +0200, Simon Horman wrote: > > Hi Olof, Hi Kevin, Hi Arnd, > > > > Please consider these Renesas ARM64 based SoC DT updates for v4.18. > > > > > > The following changes

Re: [PATCH] gpio: dwapb: Fix rework support for 1 interrupt per port A GPIO

On Fri, May 25, 2018 at 5:11 PM, Phil Edworthy wrote: > Commit da069d5d2b814d9887989dcdb29fb0202eac8b38 ("gpio: dwapb: Rework > support for 1 interrupt per port A GPIO"), was an incremental patch that > was supposed to provide the delta between v5 and v6 patch set for

Re: [PATCH 1/9] ARM: shmobile: defconfig: Enable MTD command line partition parsing

On Tue, May 22, 2018 at 02:02:49PM +0200, Marek Vasut wrote: > In preparation for removing MTD partitioning from the DTs and moving > it over to kernel command line partition parsing, enable the support > for kernel command line MTD partition parsing. > > The argument for not having MTD

Re: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT

On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote: > On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote: > > Hi Marek, > > > > On Wed, May 23, 2018 at 12:01 AM, Marek Vasut wrote: > >> On 05/22/2018 04:43 PM, Geert Uytterhoeven wrote: > >>> On Tue, May 22, 2018 at

Re: [PATCH v4 6/6] PCI: rcar: Shut the PHY down in failpath

On Thu, May 24, 2018 at 04:36:24PM +0200, Marek Vasut wrote: > If anything fails past phy_init_fn() and the system is a Gen3 with > a PHY, the PHY will be left on and inited. This is caused by the > phy_init_fn, which is in fact a pointer to rcar_pcie_phy_init_gen3() > function, which starts the

Re: [PATCH v4 2/6] PCI: rcar: Add missing irq_dispose_mapping() into failpath

On Thu, May 24, 2018 at 04:36:20PM +0200, Marek Vasut wrote: > The rcar_pcie_get_resources() is another misnomer with a side effect. > The function does not only get resources, but also maps MSI IRQs via > irq_of_parse_and_map(). In case anything fails afterward, the IRQ > mapping must be disposed

Re: [PATCH v4 1/6] PCI: rcar: Pull bus clock enable/disable from rcar_pcie_get_resources()

On Thu, May 24, 2018 at 04:36:19PM +0200, Marek Vasut wrote: > The rcar_pcie_get_resources() is another misnomer with a side effect. > The function does not only get resources, but also enables/disables bus > clock. This is forgotten in the probe() function though and if anything > in probe()

Re: [PATCH v4 3/6] PCI: rcar: Teardown MSI setup if rcar_pcie_enable() fails

On Thu, May 24, 2018 at 04:36:21PM +0200, Marek Vasut wrote: > If the rcar_pcie_enable() fails and MSIs are enabled, the setup done in > rcar_pcie_enable_msi() is never undone. Add a function to tear down the > MSI setup by disabling the MSI handling in the PCIe block, deallocating > the pages

Re: [PATCH v4 4/6] PCI: rcar: Poll more often in rcar_pcie_wait_for_dl()

On Thu, May 24, 2018 at 04:36:22PM +0200, Marek Vasut wrote: > The data link active signal usually takes ~20 uSec to be asserted, > poll the bit more often to avoid useless delays in this function. > Use udelay() instead of usleep() for such a small delay as suggested > by the timer documentation

Re: [PATCH v4 5/6] PCI: rcar: Remove IRQ mappings in rcar_pcie_enable_msi failpath

On Thu, May 24, 2018 at 04:36:23PM +0200, Marek Vasut wrote: > The rcar_pcie_enable_msi() creates IRQ mappings using irq_create_mapping() > before requesting the IRQs using devm_request_irq(). If devm_request_irq() > fails for some reason, rcar_pcie_enable_msi() does not remove the mapping. > >

Re: [PATCH v4 0/6] PCI: rcar: Failpath fixes

On Fri, May 25, 2018 at 05:43:13PM +0100, Lorenzo Pieralisi wrote: > On Thu, May 24, 2018 at 04:36:18PM +0200, Marek Vasut wrote: > > Multiple minor failpath fixes for the R-Car PCIe driver. > > > > V4: Sync up the version numbers > > Rebase on top of Lorenzo's tree > > Add new patch

Re: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT

Hi Simon, On Mon, May 28, 2018 at 10:41 AM, Simon Horman wrote: > On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote: >> On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote: >> > On Wed, May 23, 2018 at 12:01 AM, Marek Vasut >> > wrote: >> >> On

Re: [PATCH 00/03] arm64: dts: renesas: Add IPMMU device nodes

On Mon, May 21, 2018 at 11:44:44PM +0900, Magnus Damm wrote: > arm64: dts: renesas: Add IPMMU device nodes > > [PATCH 01/03] arm64: dts: renesas: r8a77965: Add IPMMU devices nodes > [PATCH 02/03] arm64: dts: renesas: r8a77980: Add IPMMU devices nodes > [PATCH 03/03] arm64: dts: renesas: r8a77990:

Re: [PATCH v2 10/11] arm64: dts: r8a77965-salvator-x: Enable DU external clocks and HDMI

Hi Kieran, Morimoto-san, On Fri, Apr 27, 2018 at 6:57 PM, Kieran Bingham wrote: > The DU1 external dot clock is provided by the fixed frequency clock > generator X21, while the DU0 and DU3 clocks are provided by the > programmable Versaclock5 clock

Re: [PATCH] arm64: dts: r8a77965: Add Watchdog Timer controller node using RCLK Watchdog Timer

On Wed, May 23, 2018 at 09:36:35PM +0900, Yoshihiro Kaneko wrote: > From: Takeshi Kihara > > Add a device node for the Watchdog Timer (WDT) controller on the Renesas > R-Car M3N (R8A77965) SoC. > > Based on a similar patch of the R8A7796 device tree > by Geert

Re: [PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

On Fri, May 25, 2018 at 11:27:46AM +0200, Geert Uytterhoeven wrote: > Hi Michel, > > On Thu, May 24, 2018 at 11:28 AM, Michel Pollet > wrote: > > This adds the Renesas R9A06G032 bare bone support. > > > > This currently only handles generic parts (gic, architected

Re: [PATCH 13/15] arm: dts: r8a7743: Add missing OPP properties for CPUs

[Cc Biju Das] On Fri, May 25, 2018 at 04:01:59PM +0530, Viresh Kumar wrote: > The OPP properties, like "operating-points", should either be present > for all the CPUs of a cluster or none. If these are present only for a > subset of CPUs of a cluster then things will start falling apart as soon >

Re: [PATCH 0/2] arm: dts: salvator-x(s): increase I2C ch4 bus speed

On Fri, May 25, 2018 at 01:05:40PM +0200, Wolfram Sang wrote: > Patches taken from the BSP. I did some testing by accessing the chips > manually. > I also checked the datasheets of the attached I2C clients which confirm this > step up. Hi Wolfram, Given Olof Johansson's recent comments in ("Re:

Re: [PATCH 2/2] arm64: dts: ulcb: Add sdhi2_ds pin group to SDHI2 pinctrl groups

On Fri, May 25, 2018 at 05:05:18PM +0200, Wolfram Sang wrote: > This patch adds definitions for configuration of the power-source, > drive-strength, etc... for the SD2_DS pin. Based on a similar patch for > Salvator boards by Masaharu Hayakawa and Takeshi Kihara. > > Signed-off-by: Wolfram Sang

Re: [PATCH] arm64: dts: r8a77965: Add Watchdog Timer controller node using RCLK Watchdog Timer

On Wed, May 23, 2018 at 2:36 PM, Yoshihiro Kaneko wrote: > From: Takeshi Kihara > > Add a device node for the Watchdog Timer (WDT) controller on the Renesas > R-Car M3N (R8A77965) SoC. > > Based on a similar patch of the R8A7796 device tree >

Re: [PATCH] PCI: rcar: Clean up PHY init on failure

On Fri, May 25, 2018 at 09:27:42PM +0200, Geert Uytterhoeven wrote: > CC Sergei > > On Fri, May 25, 2018 at 8:33 PM, Marek Vasut wrote: > > If the Gen3 PHY fails to power up, the code does not undo the > > initialization caused by phy_init(). Add the missing failure > >

Re: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT

On Mon, May 28, 2018 at 10:54:57AM +0200, Geert Uytterhoeven wrote: > Hi Simon, > > On Mon, May 28, 2018 at 10:41 AM, Simon Horman wrote: > > On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote: > >> On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote: > >> > On Wed, May

Re: [PATCH v4 00/16] R-Car DU: Convert LVDS code to bridge driver

On Fri, May 25, 2018 at 01:23:53PM +0300, Laurent Pinchart wrote: > Hi Simon, > > On Friday, 25 May 2018 13:13:20 EEST Simon Horman wrote: > > On Thu, May 24, 2018 at 11:00:52AM +0300, Laurent Pinchart wrote: > > > On Wednesday, 21 February 2018 18:39:25 EEST Simon Horman wrote: > > >> On Wed,