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
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
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
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
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,
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
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
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 &
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
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
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 ++
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 ++
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
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
---
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
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
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
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
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
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
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
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 +
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
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
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
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 +
>
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
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
28 matches
Mail list logo