[renesas-drivers:topic/salvator-x-hdmi-prototype-2016-08-30-v4.8-rc4 915/2661] drivers/media/i2c/adv7482.c:1368:1: error: '__mod_of__adv7482_of_ids_device_table' aliased to undefined symbol 'adv7482_o

tree: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git topic/salvator-x-hdmi-prototype-2016-08-30-v4.8-rc4 head: 734ea84d5f5e0cb742993e87fb99f934b5719d38 commit: c585bda5a818d6c75430e57587c7e529395ddfbf [915/2661] [media] i2c: adv7482: add adv7482 driver config:

[PATCH] ARM: dts: wheat: add SDHI0 support

Define the Wheat board dependent part of the SDHI0 (connected to the micro-SD slot) device node along with the necessary voltage regulator. Signed-off-by: Sergei Shtylyov <sergei.shtyl...@cogentembedded.com> --- This patch is against the 'renesas-devel-20160830-v4.8-rc4' of Simon Ho

[GIT PULL FOR renesas-drivers] UHS-I SDR-104 support for sh_mobile_sdhi

Hi Geert, please consider pulling updated UHS-I SDR-104 support for sh_mobile_sdhi. This updates a branch you already have in renesas-drivers, topic/sdr104-v4, which should be dropped. The Gen 3 portion of this patchset is not much use from a performance point of view without DMA support

[PATCH v5 05/11] mmc: sh_mobile_sdhi: Add tuning support

Add tuning support for use with SDR104 mode This includes adding support for the sampling clock controller (SCC). Based on work by Ai Kyuse. Cc: Ai Kyuse Signed-off-by: Simon Horman --- v5 [Simon Horman] * As suggested by Ulf Hansson - Use

[PATCH v5 10/11] arm64: dts: r8a7795: salvator-x: Enable UHS-I SDR-104

Add the sd-uhs-sdr104 property to SDHI0 and SDHI1. Signed-off-by: Simon Horman --- v5 * New patch --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts

[PATCH v5 06/11] ARM: dts: lager: Enable UHS-I SDR-104

Add the sd-uhs-sdr104 property to SDHI0. Signed-off-by: Simon Horman --- arch/arm/boot/dts/r8a7790-lager.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/r8a7790-lager.dts b/arch/arm/boot/dts/r8a7790-lager.dts index

[PATCH v5 09/11] arm64: dts: r8a7795: salvator: enable UHS for SDHI 0 & 3

From: Wolfram Sang Reviewed-by: Geert Uytterhoeven Signed-off-by: Wolfram Sang Signed-off-by: Simon Horman --- v5 * Added to series, previously posted by Wolfram

[PATCH v5 08/11] arm64: r8a7795: Set maximum frequencies for SDHI clocks

Signed-off-by: Simon Horman --- v5 * New patch --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi index 70949f4d50a2..f83b87e9366e

[PATCH v5 11/11] arm64: defconfig: Enable SDHI and GPIO_REGULATOR

This allows use of the SDHI SD/SDIO controller present on R-Car Gen3 SoCs and already enabled in the DT of the r8a7795/salvator-x (H3). Signed-off-by: Simon Horman --- v5 * New patch --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v5 00/11] UHS-I SDR-104 support for sh_mobile_sdhi

Hi, this series is based on work by Ai Kyuse to add UHS-I SDR-104 support for sh_mobile_sdhi. It builds on work by Shinobu Uehara, Rob Taylor, William Towle and Ian Molton, Ben Hutchings, Wolfram Sang and others to add UHS-I SDR-50 support to the same driver. This series enables: * UHS-I SDR-104

[PATCH v5 01/11] mmc: tmio: enhance illegal sequence handling

From: Ai Kyuse An illegal sequence command error may occur if there is a stopbit or cmd_index error as well as a CRC error. The correct course of action is to re-enable IRQs An illegal sequence data error may occur if there is a CRC or stopbit error, or underrun. In

[PATCH v5 04/11] mmc: tmio: Add tuning support

From: Ai Kyuse Add tuning support for use with SDR104 mode Signed-off-by: Ai Kyuse Signed-off-by: Simon Horman --- v5 [Simon Horman] * As suggested by Ulf Hansson: - Move hw reset support into a separate patch -

[PATCH v5 03/11] mmc: tmio: Add hw reset support

From: Ai Kyuse Add hw reset support. Signed-off-by: Ai Kyuse Signed-off-by: Simon Horman --- This is required by tuning support which will be introduced by follow-up patches. v5 [Simon Horman] * As suggested by Ulf

[PATCH v5 02/11] mmc: tmio: document mandatory and optional callbacks

Signed-off-by: Simon Horman --- v5 * New patch --- drivers/mmc/host/tmio_mmc.h | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/mmc/host/tmio_mmc.h b/drivers/mmc/host/tmio_mmc.h index 1f1cb2628f67..4b36cb5c2d9c 100644 ---

[PATCH v5 07/11] arm64: dts: r8a7795: remove unnecessary cap-mmc-highspeed property

Remove cap-mmc-highspeed property from SDHI2 and SDHI3. This property is unnecessary as the driver automatically sets the highspeed capability. Furthermore its use is inconsistent with SDHI0 and SDHI1 which are also highspeed capable but do not have this property present. Found by inspection.

Re: [PATCH v2] Documentation: devicetree: changesets do locking on their own meanwhile

On Wed, Aug 24, 2016 at 03:38:56PM +0200, Wolfram Sang wrote: > Since commit 183223770ae862 ("drivers/of: Export OF changeset functions"), > the mentioned functions do all necessary locking. > > Signed-off-by: Wolfram Sang > Fixes: 183223770ae862 ("drivers/of:

Re: [PATCH v4 2/4] mmc: tmio: Add tuning support

On Mon, Aug 29, 2016 at 04:05:55PM +0200, Ulf Hansson wrote: > On 29 August 2016 at 14:05, Simon Horman wrote: > > On Fri, Aug 26, 2016 at 10:01:35AM +0200, Ulf Hansson wrote: > >> On 25 August 2016 at 14:04, Simon Horman wrote: > >> > On Tue, Aug 23, 2016

[PATCH v2] ARM: shmobile: fix regulator quirk for Gen2

The current implementation only works if the da9xxx devices are added before their drivers are registered. Only then it can apply the fixes to both devices. Otherwise, the driver for the first device gets probed before the fix for the second device can be applied. This is what fails when using the

Re: [git pull] clk: renesas: Updates for v4.9 (take two)

On 08/30, Geert Uytterhoeven wrote: > Hi Mike, Stephen, > > The following changes since commit b51d5275016c6edbf4656eaee30d836fef127016: > > clk: renesas: r8a7796: Add watchdog module clock (2016-08-09 09:53:47 +0200) > > are available in the git repository at: > >

Re: [RESEND PATCH v3 1/3] ARM: dts: DRA7: Add "linux,pci-domain" property for pci dt nodes

* Kishon Vijay Abraham I [160830 04:06]: > Hi Tony, > > On Friday 26 August 2016 09:00 PM, Tony Lindgren wrote: > > * Kishon Vijay Abraham I [160810 05:34]: > >> Since DRA7 has multiple PCIe Rootcomplex, add "linux,pci-domain" > >> property to assign a PCI domain

Re: [PATCH] usb: renesas_usbhs: add a compatible string for r8a7796

On Wed, Aug 24, 2016 at 04:39:53PM +0900, Yoshihiro Shimoda wrote: > This patch adds support for r8a7796 (R-Car M3-W). > > Signed-off-by: Yoshihiro Shimoda > --- > Documentation/devicetree/bindings/usb/renesas_usbhs.txt | 1 + >

Re: [PATCH v2] watchdog: softdog: implement pretimeout support

Hi Wolfram, On 08/30/2016 06:03 PM, Wolfram Sang wrote: From: Wolfram Sang Give devices which do not have hardware support for pretimeout at least a software version of it. Signed-off-by: Wolfram Sang --- Change since v1:

Re: [PATCH v3 01/13] ARM: dts: lager: rename and reindex i2cexio

Hi Simon, > serial0 = > serial1 = > - i2c8 = "i2cexio"; > + i2c10 = "i2cexio0"; Those should be pointers, i.e. "", here and in the rest of your series. Sorry for the broken template! Did you have a chance to test my fix for the demuxer?

[PATCH v2] watchdog: softdog: implement pretimeout support

From: Wolfram Sang Give devices which do not have hardware support for pretimeout at least a software version of it. Signed-off-by: Wolfram Sang --- Change since v1: added 'else' block in softdog_ping(), to actually disable

Re: [PATCH] ARM: shmobile: fix regulator quirk for Gen2

Hi Wolfram, On Tue, Aug 30, 2016 at 4:54 PM, Wolfram Sang wrote: > The current implementation only works if the da9xxx devices are added > before their drivers are registered. Only then it can apply the fixes to > both devices. Otherwise, the driver for the

[git pull] clk: renesas: Updates for v4.9 (take two)

Hi Mike, Stephen, The following changes since commit b51d5275016c6edbf4656eaee30d836fef127016: clk: renesas: r8a7796: Add watchdog module clock (2016-08-09 09:53:47 +0200) are available in the git repository at:

[PATCH] ARM: shmobile: fix regulator quirk for Gen2

The current implementation only works if the da9xxx devices are added before their drivers are registered. Only then it can apply the fixes to both devices. Otherwise, the driver for the first device gets probed before the fix for the second device can be applied. This is what fails when using the

RE: [PATCH] net: ethernet: renesas: sh_eth: do not access POST registers if not exist

Hello Sergei, On Aug 29, 2016, Sergei Shtylyov wrote: >SH7757 is not the only platform with TSU, there's e.g. R8A7740 ARM > SoC which only has 1 GETHER channel... I don't have the R8A7740 manual (R-Mobile A1) so I can't see. But even if it does not have the POST registers, it might not hurt

RE: [PATCH v2] clk: renesas: rz: Select EXTAL vs USB clock

Hi Geert, Thank you for the good review! On Aug 30, 2016, Geert Uytterhoeven wrote: > If you would use "cpg_mode = (ioread16(ppr0) >> 2) & 1;", the value of > cpg_mode would > be in sync with Table 6.2. Then you can avoid relying on actual clock names > in DT, and > keep > >parent_name =

renesas-drivers-2016-08-30-v4.8-rc4

I have pushed renesas-drivers-2016-08-30-v4.8-rc4 to https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git This tree is meant to ease development of platform support and drivers for Renesas ARM SoCs. It is created by merging (a) the for-next branches of various subsystem trees

R-Car E2 Can interface receive issue

I'm trying to use native (real hardware) interfaces like can0 in R-CAR E2 based board (RTP0RC7794SEB00011S - ALT board). I am able to configure the CAN interfaces (can0 and can1). While testing, CAN driver seems to be able to send the CAN packets but not able to receive CAN packets from bus.

Re: [RESEND PATCH v3 1/3] ARM: dts: DRA7: Add "linux,pci-domain" property for pci dt nodes

Hi Tony, On Friday 26 August 2016 09:00 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I [160810 05:34]: >> Since DRA7 has multiple PCIe Rootcomplex, add "linux,pci-domain" >> property to assign a PCI domain number to each of the host >> bridges. > > Is this patch safe to

Re: [PATCH v2 2/4] arm64: dts: renesas: r8a7795: Add VSP instances

Hi Geert, (CC'ing Morimoto-san) On Monday 29 Aug 2016 18:12:07 Geert Uytterhoeven wrote: > On Tue, Aug 9, 2016 at 2:29 PM, Laurent Pinchart wrote: > > The r8a7795 has 9 VSP instances. > > 7? > > > Signed-off-by: Laurent Pinchart > > > > --- > > > >

Re: [PATCH v2] clk: renesas: rz: Select EXTAL vs USB clock

Hi Chris, On Tue, Aug 30, 2016 at 5:13 AM, Chris Brandt wrote: > Check the MD_CLK pin to determine the current clock mode in order to set > the pll clock parent correctly. > > Signed-off-by: Chris Brandt Thanks for your patch! > --- > v2: >

Re: [PATCH v2] ARM: dts: rskrza1: initial device tree

On Mon, Aug 29, 2016 at 02:13:22PM -0400, Chris Brandt wrote: > Add the initial device tree for the RZ/A1 based development board (RSK). > > Signed-off-by: Chris Brandt > Reviewed-by: Geert Uytterhoeven > --- > v2: > * Removed empty line at end

Re: [PATCH v2] clk: renesas: rz: Select EXTAL vs USB clock

On Tue, Aug 30, 2016 at 09:04:44AM +0200, Simon Horman wrote: > On Mon, Aug 29, 2016 at 11:13:58PM -0400, Chris Brandt wrote: > > Check the MD_CLK pin to determine the current clock mode in order to set > > the pll clock parent correctly. > > > > Signed-off-by: Chris Brandt

Re: [PATCH v2] clk: renesas: rz: Select EXTAL vs USB clock

On Mon, Aug 29, 2016 at 11:13:58PM -0400, Chris Brandt wrote: > Check the MD_CLK pin to determine the current clock mode in order to set > the pll clock parent correctly. > > Signed-off-by: Chris Brandt > --- > v2: > * Switched to reading MD_CLK pin to determine mode

Re: [PATCH 1/4] ARM: dts: shmobile: remove label property from led

Hi Simon, On Tue, Aug 30, 2016 at 8:52 AM, Simon Horman wrote: > On Mon, Aug 29, 2016 at 09:53:23AM +0200, Geert Uytterhoeven wrote: >> The patch index in the subject should have been 0/4. You're breaking my >> script to extract patch series from email threads ;-) I think

Re: [PATCH 1/4] ARM: dts: shmobile: remove label property from led

On Mon, Aug 29, 2016 at 09:53:23AM +0200, Geert Uytterhoeven wrote: > Hi Simon, > > The patch index in the subject should have been 0/4. You're breaking my > script to extract patch series from email threads ;-) True. Probably we should not apply this series as its just a clean up and not worth