[GIT PULL FOR renesas-drivers] media: ADV748x driver

Hi Geert, Please consider including this driver (based on linux-media/master) for renesas-drivers. -- Regards Kieran The following changes since commit 47f910f0e0deb880c2114811f7ea1ec115a19ee4: [media] v4l: subdev: tolerate null in media_entity_to_v4l2_subdev (2017-06-08 16:55:25 -0300)

[PATCH v4 1/2] media: i2c: adv748x: add adv748x driver

From: Kieran Bingham Provide support for the ADV7481 and ADV7482. The driver is modelled with 4 subdevices to allow simultaneous streaming from the AFE (Analog front end) and HDMI inputs though two CSI TX entities. The HDMI entity is linked to the TXA

[PATCH v4 2/2] arm64: dts: renesas: salvator-x: Add ADV7482 support

From: Kieran Bingham Provide ADV7482, and the needed connectors Signed-off-by: Kieran Bingham v4: - dt: Rebase to dts/renesas/salvator-x.dtsi - dt: Use AIN0-7 rather than AIN1-8

[PATCH v4 0/2] ADV748x HDMI/Analog video receiver

From: Kieran Bingham This is a driver for the Analog Devices ADV748x device, and follows on from a previous posting by Niklas Söderlund [0] of an earlier incarnation of this driver. Aside from a few bug fixes, and considerable refactoring this driver: -

Re: [PATCH v2] net: phy: Make phy_ethtool_ksettings_get return void

Hi Yuval, [auto build test ERROR on net-next/master] [also build test ERROR on next-20170609] [cannot apply to v4.12-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] net: phy: Make phy_ethtool_ksettings_get return void

From: David Miller Date: Mon, 12 Jun 2017 10:25:25 -0400 (EDT) > From: Yuval Shaia > Date: Mon, 12 Jun 2017 17:15:08 +0300 > >> Make return value void since function never return meaningfull value >> >> Signed-off-by: Yuval Shaia

Re: [PATCH v2] net: phy: Make phy_ethtool_ksettings_get return void

From: Yuval Shaia Date: Mon, 12 Jun 2017 17:15:08 +0300 > Make return value void since function never return meaningfull value > > Signed-off-by: Yuval Shaia > Acked-by: Sergei Shtylyov > --- > v0 ->v1: >

Re: [GIT PULL FOR renesas-drivers] mmc: renesas_sdhi: add support for R-Car Gen3 SDHI DMAC

> > This pull request is based on mmc/next. > > Unfortunately Ulf rebases mmc/next regularly, causing lots of conflicts. Maybe we could ask him to stop doing that? I was taught "never rebase anything going into linux-next" back then for exactly those reasons. signature.asc Description: PGP

[PATCH v2] net: phy: Make phy_ethtool_ksettings_get return void

Make return value void since function never return meaningfull value Signed-off-by: Yuval Shaia Acked-by: Sergei Shtylyov --- v0 ->v1: * These files were missing in v0 * drivers/net/ethernet/renesas/ravb_main.c

Re: [PATCH v8 3/8] media: i2c: max2175: Add MAX2175 support

Hi Hans, On Mon, Jun 12, 2017 at 3:50 PM, Hans Verkuil wrote: > On 06/12/2017 03:26 PM, Ramesh Shanmugasundaram wrote: >> This patch adds driver support for the MAX2175 chip. This is Maxim >> Integrated's RF to Bits tuner front end chip designed for software-defined >> radio

Re: [PATCH v3] sh_eth: add support for changing MTU

From: Niklas Söderlund Date: Mon, 12 Jun 2017 10:39:03 +0200 > The hardware supports the MTU to be changed and the driver it self is > somewhat prepared to support this. This patch hooks up the callbacks to > be able to change the MTU from user-space. > >

Re: [PATCH v1] net/phy: Make phy_ethtool_ksettings_get return void

From: Yuval Shaia Date: Mon, 12 Jun 2017 10:42:33 +0300 > Make return value void since function never return meaningfull value > > Signed-off-by: Yuval Shaia > Acked-by: Sergei Shtylyov > --- > Re-sending

Re: [PATCH v8 3/8] media: i2c: max2175: Add MAX2175 support

On 06/12/2017 03:26 PM, Ramesh Shanmugasundaram wrote: This patch adds driver support for the MAX2175 chip. This is Maxim Integrated's RF to Bits tuner front end chip designed for software-defined radio solutions. This driver exposes the tuner as a sub-device instance with standard and custom

[PATCH v8 1/8] media: v4l2-ctrls: Reserve controls for MAX217X

Reserve controls for MAX217X RF to Bits tuner family. These hybrid radio receiver chips are highly programmable and hence reserving 32 controls. Signed-off-by: Ramesh Shanmugasundaram Acked-by: Laurent Pinchart ---

[PATCH v8 4/8] media: Add new SDR formats PC16, PC18 & PC20

This patch adds support for the three new SDR formats. These formats were prefixed with "planar" indicating I & Q data are not interleaved as in other formats. Here, I & Q data constitutes the top half and bottom half of the received buffer respectively. V4L2_SDR_FMT_PCU16BE - 14-bit complex (I &

[PATCH v8 7/8] media: platform: rcar_drif: Add DRIF support

This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs. The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF device represents a channel and each channel can have one or two sub-channels respectively depending on the target board. DRIF supports only Rx

[PATCH v8 8/8] MAINTAINERS: Add entry for R-Car DRIF & MAX2175 drivers

Add maintainter entry for the R-Car DRIF and MAX2175 drivers. Signed-off-by: Ramesh Shanmugasundaram --- MAINTAINERS | 19 +++ 1 file changed, 19 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 053c3bdd1fe5..cfa78fe5142a 100644

[PATCH v8 3/8] media: i2c: max2175: Add MAX2175 support

This patch adds driver support for the MAX2175 chip. This is Maxim Integrated's RF to Bits tuner front end chip designed for software-defined radio solutions. This driver exposes the tuner as a sub-device instance with standard and custom controls to configure the device. Signed-off-by: Ramesh

[PATCH v8 5/8] doc_rst: media: New SDR formats PC16, PC18 & PC20

This patch adds documentation for the three new SDR formats V4L2_SDR_FMT_PCU16BE V4L2_SDR_FMT_PCU18BE V4L2_SDR_FMT_PCU20BE Signed-off-by: Ramesh Shanmugasundaram --- .../media/uapi/v4l/pixfmt-sdr-pcu16be.rst | 55 ++

[PATCH v8 0/8] Add V4L2 SDR (DRIF & MAX2175) driver

Hi Mauro, Hans, This patch set contains two drivers - Renesas R-Car Digital Radio Interface (DRIF) driver - Maxim's MAX2175 RF to Bits tuner driver These patches were based on top of media_tree. commit: 47f910f0e0deb880c2114811f7ea1ec115a19ee4 These two drivers combined together expose a V4L2

[PATCH v8 6/8] dt-bindings: media: Add Renesas R-Car DRIF binding

Add binding documentation for Renesas R-Car Digital Radio Interface (DRIF) controller. Signed-off-by: Ramesh Shanmugasundaram Acked-by: Rob Herring --- .../devicetree/bindings/media/renesas,drif.txt | 176 + 1

[PATCH v8 2/8] dt-bindings: media: Add MAX2175 binding description

Add device tree binding documentation for MAX2175 RF to bits tuner device. Signed-off-by: Ramesh Shanmugasundaram Acked-by: Rob Herring --- .../devicetree/bindings/media/i2c/max2175.txt | 59 ++

Re: [PATCH 1/2] soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON

On 12 June 2017 at 11:23, Geert Uytterhoeven wrote: > Improve handling of always-on PM domains by using the > GENPD_FLAG_ALWAYS_ON flag introduced in commit ffaa42e8a40b7f10 ("PM / > Domains: Enable users of genpd to specify always on PM domains"). > > Signed-off-by:

Re: [PATCH 2/2] ARM: shmobile: pm-rmobile: Use GENPD_FLAG_ALWAYS_ON

On 12 June 2017 at 11:23, Geert Uytterhoeven wrote: > Improve handling of always-on PM domains by using the > GENPD_FLAG_ALWAYS_ON flag introduced in commit ffaa42e8a40b7f10 ("PM / > Domains: Enable users of genpd to specify always on PM domains"). > > Note that the PM

Re: [PATCH] ravb: add wake-on-lan support via magic packet

Hi Niklas, On Mon, Jun 12, 2017 at 1:32 PM, Niklas Söderlund wrote: > On 2017-05-18 10:52:25 +0200, Geert Uytterhoeven wrote: >> On Tue, May 16, 2017 at 2:16 PM, Niklas Söderlund >> wrote: >> > On 2017-05-16 13:36:21 +0200, Geert

Re: [PATCH] ravb: add wake-on-lan support via magic packet

Hi Geert, On 2017-05-18 10:52:25 +0200, Geert Uytterhoeven wrote: > Hi Niklas, > > On Tue, May 16, 2017 at 2:16 PM, Niklas Söderlund > wrote: > > On 2017-05-16 13:36:21 +0200, Geert Uytterhoeven wrote: > >> On Tue, May 16, 2017 at 1:01 PM, Simon Horman

Re: ravb WoL interrupt flood

Hi Geert, On 2017-05-30 12:29:24 +0200, Niklas Söderlund wrote: > Hi Geert, > > Thanks for the report. I did run a 200+ loop suspend/resume without > issues so this error is probably hard to reproduce or something changed > since v4.11-rc1 which if IIRC was the base I used to do the tests. >

Re: [RFC PATCH v2 0/2] mmc: core: process ECC errors raised in stop cmds

On Mon, Jun 12, 2017 at 10:30:27AM +0200, Ulf Hansson wrote: > On 8 April 2017 at 22:20, Wolfram Sang > wrote: > > Here is the second RFC for handling ECC errors flagged in the stop command > > after a multiblock transfer. It is still RFC because I could only

Re: [PATCH/RFC] clk: renesas: cpg-mssr: Restore module clock registers during resume

Hi Geert, Thanks for your patch. On 2017-06-07 13:58:38 +0200, Geert Uytterhoeven wrote: > During PSCI system suspend, R-Car Gen3 SoCs are powered down, and their > clock register state is lost. Note that as the boot loader skips most > initialization after resume, clock register state differs

[PATCH v2] media: fdp1: Support ES2 platforms

From: Kieran Bingham The new Renesas R-Car H3 ES2.0 platforms have a new hw version register. Update the driver accordingly, defaulting to the new hw revision, and differentiating the older revision as ES1 Signed-off-by: Kieran Bingham

Re: [PATCH] media: fdp1: Support ES2 platforms

Hi Kieran, Laurent, On Sat, Jun 10, 2017 at 9:54 AM, Laurent Pinchart wrote: > On Friday 09 Jun 2017 18:15:48 Kieran Bingham wrote: >> From: Kieran Bingham >> >> The new Renesas R-Car H3 ES2.0 platforms have an updated

[PATCH] MAINTAINERS: Add entry for R-Car DRIF & MAX2175 drivers

Add maintainter entry for the R-Car DRIF and MAX2175 drivers. Signed-off-by: Ramesh Shanmugasundaram --- Hi Hans, Added the missing MAINTAINTERS entry on top of this (https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg15081.html)

Re: [GIT PULL FOR renesas-drivers] mmc: renesas_sdhi: add support for R-Car Gen3 SDHI DMAC

Hi Simon, On Mon, Jun 12, 2017 at 11:47 AM, Simon Horman wrote: > please consider pulling changes to add support for R-Car Gen3 SDHI DMAC. > > This gives a significant performance boost; > the headline figure is 9.5MB/s -> 39.7MB/s. > > This pull request is based on

[GIT PULL FOR renesas-drivers] mmc: renesas_sdhi: add support for R-Car Gen3 SDHI DMAC

Hi Geert, please consider pulling changes to add support for R-Car Gen3 SDHI DMAC. This gives a significant performance boost; the headline figure is 9.5MB/s -> 39.7MB/s. This pull request is based on mmc/next. The following changes since commit 6e75316c15df8333506377743c75fcd626193849:

Re: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Linus, On Sun, Jun 11, 2017 at 11:45:49PM +0200, Linus Walleij wrote: > On Fri, Jun 9, 2017 at 9:50 AM, jmondi wrote: > > On Fri, Jun 09, 2017 at 03:26:57PM +0800, Dong Aisheng wrote: > > >> > I see three options here: > >> > > >> > 1) Add "output-buffer-enable" and

[PATCH 2/2] arm64: dts: r8a7796: Add reset control properties for audio

Note that the audio module has resets for the Serial Sound Interfaces only. Signed-off-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a7796.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7796.dtsi

[PATCH 1/2] arm64: dts: r8a7795: Add reset control properties for audio

Note that the audio module has resets for the Serial Sound Interfaces only. Signed-off-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi

[PATCH 0/2] arm64: dts: renesas: Add reset control properties for audio

Hi Simon, Magnus, Morimoto-san, This patch series describes all resets wired to the audio modules on R-Car Gen3 SoCs, following the DT binding update in commit 5f440c48c5d5a11f ("ASoC: rsnd: Document optional reset properties") in sound-asoc/for-next. Thanks! Geert Uytterhoeven (2):

[GIT PULL] Second Round of Renesas ARM Based SoC Fixes for v4.12

Hi Olof, Hi Kevin, Hi Arnd, Please consider these second round of Renesas ARM based SoC fixes for v4.12. It splits LCD mux and gpio into separate nodes as different values for the output-high property are required. This pull request is based on the previous round of such requests, tagged as

[PATCH] ARM: dts: armadillo800eva: Split LCD mux and gpio

From: Geert Uytterhoeven Configuration of the lcd0 pinmux group and GPIO hog for the external GPIO mux are done using a single device node, causing the "output-high" property to be applied to both. This will fail for the pinmux group, but doesn't cause any harm, as the

[PATCH 1/2] soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON

Improve handling of always-on PM domains by using the GENPD_FLAG_ALWAYS_ON flag introduced in commit ffaa42e8a40b7f10 ("PM / Domains: Enable users of genpd to specify always on PM domains"). Signed-off-by: Geert Uytterhoeven --- drivers/soc/renesas/rcar-sysc.c | 28

[PATCH 2/2] ARM: shmobile: pm-rmobile: Use GENPD_FLAG_ALWAYS_ON

Improve handling of always-on PM domains by using the GENPD_FLAG_ALWAYS_ON flag introduced in commit ffaa42e8a40b7f10 ("PM / Domains: Enable users of genpd to specify always on PM domains"). Note that the PM domain containing the serial console is still handled locally. Signed-off-by: Geert

Re: [PATCH 0/4] arm64: renesas: Add support for Salvator-XS

On Fri, Jun 09, 2017 at 01:43:45PM +0200, Geert Uytterhoeven wrote: > Hi Simon, Magnus, > > The Renesas Salvator-XS (Salvator-X 2nd version) development board can > be equipped with either an R-Car H3 ES2.0 or M3-W ES1.x SiP, which are > pin-compatible. > > This patch series adds initial

Re: [PATCH v2] ARM: dts: r8a779x: Fix PCI bus dtc warnings

On Fri, Jun 09, 2017 at 05:50:40PM +0200, Geert Uytterhoeven wrote: > From: Rob Herring > > The bogus 'device_type = "pci"' confuses dtc, causing lots of totally > unrelated warnings. After fixing that, real warnings like > > arch/arm/boot/dts/r8a7790-lager.dtb: Warning

Re: [PATCH] arm64: dts: salvator-x: Add missing index to PWM pinctrl subnode name

On Thu, Jun 08, 2017 at 03:45:00PM +0200, Geert Uytterhoeven wrote: > R-Car Gen3 SoCs contain multiple PWM modules. Hence to avoid conflicts, > pinctrl subnodes for PWM should include indices referring to their > instances. > > Fixes: b33be33670217533 ("arm64: dts: salvator-x: Add panel

[PATCH v3] sh_eth: add support for changing MTU

The hardware supports the MTU to be changed and the driver it self is somewhat prepared to support this. This patch hooks up the callbacks to be able to change the MTU from user-space. Signed-off-by: Niklas Söderlund Acked-by: Sergei Shtylyov

Re: [RFC PATCH v2 0/2] mmc: core: process ECC errors raised in stop cmds

On 8 April 2017 at 22:20, Wolfram Sang wrote: > Here is the second RFC for handling ECC errors flagged in the stop command > after a multiblock transfer. It is still RFC because I could only test it by > inducing ECC errors in software (see patch for TMIO below).

Re: [PATCH v7 0/7] Add V4L2 SDR (DRIF & MAX2175) driver

Hi Ramesh, Can you post a patch on top of this series adding entries for these two drivers to the MAINTAINERS file? That's missing in this series. Thanks! Hans On 06/09/2017 05:07 PM, Ramesh Shanmugasundaram wrote: Hi Mauro, Hans, This patch set contains two drivers - Renesas