Hi Laurent,
Thanks for your comments.
Apart from the issue with the input API Hans pointed which indicates I
need to keep that around until it's fixed in the framework I agree with
all your comments but one.
On 2017-12-08 12:14:05 +0200, Laurent Pinchart wrote:
> > @@ -628,7 +628,8 @@
Add support for the R-Car V3M (R8A77970) SoC to the R-Car DU driver.
Signed-off-by: Sergei Shtylyov
---
Changes in version 2:
- removed the 'model' and 'dpll_ch' field initializers;
- fixed up the DU port numbers;
- split the DU bindings and the LVDS driver
Document the R-Car V3M (R8A77970) SoC in the R-Car DU bindings.
Signed-off-by: Sergei Shtylyov
---
Changes in version 2:
- documented R8A77970 DU ports;
- patch split from the main R8A77970 DU support patch.
Hello!
Here's the set of 2 patches against the 'drm-next' branch of David Airlie's
'linux.git' repo. The purpose of these patches is to add the R-Car V3M
(R8A77970) support to the DU driver; the LVDS driver patches will be posted
separately...
[1/2] DT: display: renesas,du: document R8A77970
From: Magnus Damm
Add GPIO device nodes for the r8a77970 SoC. Each GPIO device is
currently assumed to have 32 pins.
Signed-off-by: Magnus Damm
---
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 96 +
1 file
arm64: dts: renesas: Eagle V3M PFC/GPIO update and SPI NOR flash bitbang hack
[PATCH/RFC 01/03] arm64: dts: renesas: r8a77970: Add PFC node for Eagle V3M
[PATCH/RFC 02/03] arm64: dts: renesas: r8a77970: Add GPIO nodes
[PATCH/RFC 03/03] arm64: dts: renesas: eagle: NOR flash SPI bitbang prototype
From: Magnus Damm
Drive the NOR flash chips via SPI bitbang instead of via the two
channels of QSPI hardware. This is useful to test the on-chip GPIO
devices.
Not-Yet-Signed-off-by: Magnus Damm
---
From: Magnus Damm
Add DT nodes for the PFC on the r8a77970 SoC and hook up the SCIF
console to make use of the PFC to configure the pins.
Signed-off-by: Magnus Damm
---
Depends on r8a77970 PFC support - included in latest
From: Magnus Damm
Here's V2 of a simple prototype hack to get the R-Car M3-N SoC working with
the r8a77965 Salvator-X. This version has been updated to fit on top of
"renesas-drivers-2018-01-09-v4.15-rc7".
The following patches are picked from renesas-bsp @
Commit d455b45f8393 ("v4l: vsp1: Add support for new VSP2-BS, VSP2-DL,
and VSP2-D instances") added support for the VSP2-D found in the R-Car
V3M (R8A77970) but the video output that VSP2-D sends to DU has a greenish
garbage-like line repeated every 8 screen rows. It turns out that R-Car
V3M has
rack for v4.17.
These changes are visible in the renesas-next-20180118-v4.15-rc1 and
renesas-devel-20180118-v4.15-rc8 tags.
Sorry for any confusion this may have caused.
On Thu, 18 Jan 2018, Masahiro Yamada wrote:
> The use of this flag has been replaced with MMC_CAP2_NO_WRITE_PROTECT.
> No platform defines this flag any more. Remove.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v3:
> - newly added
>
> Changes in
On Thu, Jan 18, 2018 at 03:20:00AM +0100, Niklas Söderlund wrote:
> Hi Simon,
>
> Thanks for your patch.
>
> On 2018-01-17 17:17:17 +0100, Simon Horman wrote:
> > Sort the subnodes of the soc node to improve maintainability.
> > The sort key is the address on the bus with instances of the same
>
On 17 January 2018 at 17:28, Masahiro Yamada
wrote:
>
> In the previous batch (https://lkml.org/lkml/2017/11/24/428)
> I sent 22 patches for TMIO MMC.
>
> 14 patches were applied, the rest is under discussion.
>
> This series consists of 16 patches.
>
> Patch 1-4:
14 matches
Mail list logo