Re: [PATCH v2] sh_eth: add support to change MTU

2017-06-09 Thread Sergei Shtylyov
On 06/09/2017 11:32 PM, Niklas Söderlund wrote: 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

[PATCH v2] sh_eth: add support to change MTU

2017-06-09 Thread Niklas Söderlund
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: [PATCH] sh_eth: add support to change MTU

2017-06-09 Thread Niklas Söderlund
Hi Sergei, Thanks for your feedback. On 2017-06-09 19:31:09 +0300, Sergei Shtylyov wrote: > Hello! > > On 06/09/2017 06:30 PM, Niklas Söderlund wrote: > > > The hardware supports the MTU to be changed and the driver it self is > > somewhat prepared to support this. This patch hooks up the

Re: [PATCH] sh_eth: add support to change MTU

2017-06-09 Thread Sergei Shtylyov
Hello! On 06/09/2017 06:30 PM, Niklas Söderlund wrote: 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

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

2017-06-09 Thread Geert Uytterhoeven
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 (pci_device_reg): Node /pci@ee09/usb@0,1 PCI unit address format error,

[PATCH] sh_eth: add support to change MTU

2017-06-09 Thread Niklas Söderlund
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 --- Based on v4.12-rc1 and tested on

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

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 4/7] media: Add new SDR formats PC16, PC18 & PC20

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 7/7] media: platform: rcar_drif: Add DRIF support

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 3/7] media: i2c: max2175: Add MAX2175 support

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 5/7] doc_rst: media: New SDR formats PC16, PC18 & PC20

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 2/7] dt-bindings: media: Add MAX2175 binding description

2017-06-09 Thread Ramesh Shanmugasundaram
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 ++

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

2017-06-09 Thread Ramesh Shanmugasundaram
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 v7 1/7] media: v4l2-ctrls: Reserve controls for MAX217X

2017-06-09 Thread Ramesh Shanmugasundaram
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] rcar-vin: add support for V4L2_FIELD_SEQ_{TB,BT}

2017-06-09 Thread Niklas Söderlund
The hardware do not support capturing the field types V4L2_FIELD_SEQ_TB and V4L2_FIELD_SEQ_BT. To capture in these formats the driver needs to change what field (top or bottom) is to be captured next and for every other capture adjust the offset of the capture buffer. This patch adds support for

[PATCH] clk: renesas: cpg-mssr: Use of_device_get_match_data() helper

2017-06-09 Thread Geert Uytterhoeven
If CONFIG_OF=n: drivers/clk/renesas/renesas-cpg-mssr.c: In function ‘cpg_mssr_probe’: drivers/clk/renesas/renesas-cpg-mssr.c:702: warning: dereferencing ‘void *’ pointer drivers/clk/renesas/renesas-cpg-mssr.c:702: error: request for member ‘data’ in something not a structure or

[PATCH] pinctrl: sh-pfc: r8a7795: Add EtherAVB pins, groups and function

2017-06-09 Thread Geert Uytterhoeven
Add pins, groups, and a function for EtherAVB on R-Car H3 ES2.0. Extracted from a big patch in the BSP by Takeshi Kihara. Signed-off-by: Geert Uytterhoeven --- To be queued in sh-pfc-for-v4.13. drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 111

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

2017-06-09 Thread Geert Uytterhoeven
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 support for the Renesas Salvator-XS development board equipped with an R-Car H3

[PATCH 2/4] arm64: dts: renesas: Extract common Salvator-X/XS board support

2017-06-09 Thread Geert Uytterhoeven
The Renesas Salvator-X and Salvator-XS (Salvator-X 2nd version) boards are very similar. To avoid duplication, prepare for the advent of the latter by extracting the common board parts into its own .dtsi file. Signed-off-by: Geert Uytterhoeven --- .../{salvator-x.dtsi

[PATCH 1/4] ARM: shmobile: Document Renesas H3-based Salvator-XS board DT bindings

2017-06-09 Thread Geert Uytterhoeven
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. Document board part number and compatible values for the version with R-Car H3. Signed-off-by: Geert Uytterhoeven

[PATCH 3/4] arm64: dts: renesas: Add common Salvator-XS board support

2017-06-09 Thread Geert Uytterhoeven
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. Add initial support for the common parts of the Salvator-XS board into its own .dtsi file, to be included by the DTSes for the H3/M3-W

[PATCH 4/4] arm64: dts: renesas: Add support for Salvator-XS with R-Car H3 ES2.0

2017-06-09 Thread Geert Uytterhoeven
Add initial support for the Renesas Salvator-XS (Salvator-X 2nd version) development board equipped with an R-Car H3 ES2.0 SiP. Signed-off-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/Makefile | 1 +

Re: [PATCH v4] v4l: subdev: tolerate null in media_entity_to_v4l2_subdev

2017-06-09 Thread Kieran Bingham
Hi Sakari, Mauro, On 08/06/17 21:10, Mauro Carvalho Chehab wrote: > Em Thu, 8 Jun 2017 22:32:10 +0300 > Sakari Ailus escreveu: > >> Hi Mauro, >> >> On Thu, Jun 08, 2017 at 03:00:22PM -0300, Mauro Carvalho Chehab wrote: >>> Em Wed, 7 Jun 2017 10:52:07 +0100 >>> Kieran

Re: [PATCH/RFC 5/5] mmc: renesas-sdhi: remove gen3 support from sysc dmac driver

2017-06-09 Thread Geert Uytterhoeven
Hi Simon, On Thu, Jun 8, 2017 at 3:09 PM, Simon Horman wrote: > Gen3 SoCs are now supported by the internal dmac variant of the SDHI driver. > Remove them from the sys dmac variant where only PIO mode is supported. > > Signed-off-by: Simon Horman

Re: [PATCH/RFC 4/5] mmc: renesas_sdhi: add support for R-Car Gen3 SDHI DMAC

2017-06-09 Thread Geert Uytterhoeven
Hi Simon, On Thu, Jun 8, 2017 at 3:13 PM, Simon Horman wrote: > R-Car Gen3 has a dedicated DMA controller for SDHI module. Since > the DMAC is in a part of SDHI module and is not suitable as dmaengine, the DMAC is part of the SDHI module? > this patch adds a

Re: [PATCH/RFC 2/5] mmc: tmio: add complete to DMA ops

2017-06-09 Thread Geert Uytterhoeven
Hi Simon, On Thu, Jun 8, 2017 at 3:09 PM, Simon Horman wrote: > Add complete to DMA ops to allow DMAC implementation dependent > handling of DMA completion. > > Signed-off-by: Simon Horman > --- > drivers/mmc/host/tmio_mmc.h | 1 + >

Re: [PATCH/RFC 3/5] mmc: sh_mobile_sdhi: add some SoC specific data for R-Car Gen3

2017-06-09 Thread Geert Uytterhoeven
Hi Simon, On Thu, Jun 8, 2017 at 3:09 PM, Simon Horman wrote: > To avoid complicate code in own dma code for gen3, this patch > adds set max_segs to 1. Then, the tmio driver will get requests > as sg_len = 1 only. The above doesn't seem to match with the actual code

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

2017-06-09 Thread Dong Aisheng
Hi Linus & j, On Mon, May 29, 2017 at 6:42 PM, jmondi wrote: > Hi Linus, > > On Mon, May 29, 2017 at 10:45:44AM +0200, Linus Walleij wrote: >> On Tue, May 23, 2017 at 8:37 PM, jmondi wrote: >> >> >> I did not follow too much. >> >> But it seems