On Wed, Jul 12, 2017 at 02:20:43AM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Tuesday 11 Jul 2017 11:16:17 Simon Horman wrote:
> > On Mon, Jul 10, 2017 at 04:31:38PM +0300, Laurent Pinchart wrote:
> > > On Monday 26 Jun 2017 19:29:28 Laurent Pinchart wrote:
> > >> Hello,
> > >>
> > >>
On Tue, Jul 11, 2017 at 03:51:40PM +0300, Sergei Shtylyov wrote:
> On 07/11/2017 03:21 PM, Simon Horman wrote:
>
> >>>Add a new compatible string for the RZ/G1M (R8A7743) SoC.
> >>>
> >>>Signed-off-by: Biju Das
> >>>---
> >>>v1->v2
> >>>* Changed the subject
> >>>*
On Tue, Jul 11, 2017 at 07:59:31PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
> wrote:
> > Add fallback compatibility string for R-Car Gen 1, 2 and 3.
> >
> > In the case of Renesas R-Car hardware we know that there
Hi Simon,
On Tuesday 11 Jul 2017 11:16:17 Simon Horman wrote:
> On Mon, Jul 10, 2017 at 04:31:38PM +0300, Laurent Pinchart wrote:
> > On Monday 26 Jun 2017 19:29:28 Laurent Pinchart wrote:
> >> Hello,
> >>
> >> This patch series enable DU support in DT for the R-Car H3 ES2.0
> >> Salvator-X
The DU can compose the output of a VSP with other planes on Gen2
hardware, and of two VSPs on Gen3 hardware. Neither of these features
are supported by the driver, and the current implementation always
assigns planes to CRTCs the same way.
Simplify the implementation by configuring plane
From: Kieran Bingham
The driver recently switched from handling page flip completion in the
DU vertical blanking handler to the VSP frame end handler to fix a race
condition. This unfortunately resulted in incorrect timestamps in the
vertical blanking
When implementing support for interlaced modes, the driver switched from
reporting vblank events on the vertical blanking (VBK) interrupt to the
frame end interrupt (FRM). This incorrectly divided the reported refresh
rate by two. Fix it by moving back to the VBK interrupt.
Fixes: 906eff7fcada
Hello,
The recent changes to the rcar-du driver to fix a page flip handling race
condition changed the order of which vblanks and page flips are handled,
resulting in incorrect timestamps being reported in the vblan events.
Correct this by handling vblank events in the same completion handler as
When implementing support for interlaced modes, the driver switched from
reporting vblank events on the vertical blanking (VBK) interrupt to the
frame end interrupt (FRM). This incorrectly divided the reported refresh
rate by two. Fix it by moving back to the VBK interrupt.
Fixes: 906eff7fcada
Hi Geert,
On Tuesday, July 11, 2017, Geert Uytterhoeven wrote:
> > zeroing out the bottom 2 bits of count for out math.
>
> s/out/our/
Thank you!
> > - buf8 = (u8 *)(buf + (count >> 2));
> > + buf8 = (u8 *)buf + (count & ~3);
> > count %= 4;
>
>
Hi Simon,
On Tue, Jul 11, 2017 at 2:38 PM, Simon Horman
wrote:
> Add fallback compatibility string for R-Car Gen 1, 2 and 3.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, f.e. Gen 1 and 2. But beyond that its not clear what
Hi Chris,
On Tue, Jul 11, 2017 at 6:29 PM, Chris Brandt wrote:
> The existing code gives an incorrect value.
> The buffer pointer 'buf' was of type unsigned short *, and 'count' was a
> number in bytes, so the pointer should have been cast before doing any
> pointer
On Tue, Jul 11, 2017 at 1:44 PM, Simon Horman
wrote:
> Add fallback compatibility string for R-Car Gen 2 and 3.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, e.g. Gen 1 and 2. But beyond that its not clear what the relationship
The existing code gives an incorrect value.
The buffer pointer 'buf' was of type unsigned short *, and 'count' was a
number in bytes, so the pointer should have been cast before doing any
pointer arithmetic.
Since we know the code before it is doing as many 4-byte transfers as
possible, we just
On 07/11/2017 02:44 PM, Simon Horman wrote:
Add fallback compatibility string for R-Car Gen 2 and 3.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 1 and 2. But beyond that its not clear what the relationship
between IP blocks might be. For example,
On Tue, Jul 11, 2017 at 04:43:28PM +0200, Ulf Hansson wrote:
> On 3 July 2017 at 21:28, Wolfram Sang
> wrote:
> > I always anticipated this code to be not correct, but now I had a test
> > case to prove it. According to all documentation I have, setting the
> >
Hi Hans and Niklas,
On Mon, Jun 19, 2017 at 01:44:22PM +0200, Hans Verkuil wrote:
> On 06/12/2017 04:48 PM, Niklas Söderlund wrote:
> > Hi Hans,
> >
> > Thanks for your comments.
> >
> > On 2017-05-29 13:16:23 +0200, Hans Verkuil wrote:
> > > On 05/24/2017 02:13 AM, Niklas Söderlund wrote:
> >
On 21 June 2017 at 16:00, Simon Horman wrote:
> Hi,
>
> this series adds support for the internal DMAC used by r8a779[56] SoCs.
> This is achieved by adding a new variant of the SDHI driver for this
> DMA controller with compat strings for the r8a779[56] SoCs.
> Compat
On 28 June 2017 at 17:23, Wolfram Sang wrote:
> Our hardware engineers confirmed that it is unnecessary to wait when
> turning the clock on/off. The documentation was a tad vague, so we
> used to play safe.
>
> Signed-off-by: Wolfram Sang
On 28 June 2017 at 17:21, Wolfram Sang wrote:
> Most registers need to wait until the command is completed, not
> necessarily until the bus is free. At least, R-Car 2+ SoCs can signal
> that via the CBSY bit, so let's use it there instead of SCLKDIVEN to
> save a
On 3 July 2017 at 21:28, Wolfram Sang wrote:
> I always anticipated this code to be not correct, but now I had a test
> case to prove it. According to all documentation I have, setting the
> TMIO_STOP_STP bit ever only worked during block transfers. This bit is
>
On 30 June 2017 at 12:56, Wolfram Sang wrote:
> From: Wolfram Sang
>
> The main patch is patch 4 which uses the maximum sd_buf size, i.e. 32 bit on
> Gen2 and 64 bit on Gen3. Instead of a new flag, we use the bus_shift
> information we
string usage in vin nodes for the
r8a779[23] SoCs.
Based on renesas-devel-20170711-v4.12
Simon Horman (3):
ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for vin nodes
ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for vin nodes
ARM: dts: r8a7794: Use R-Car Gen 2 fallback binding
Use R-Car Gen 2 fallback binding for vind nodes in DT for r8a7794 SoC.
This has no run-time effect for the current driver as the initialisation
sequence is the same for the SoC-specific binding for r8a7794 and the
fallback binding for R-Car Gen 2
Signed-off-by: Simon Horman
Use R-Car Gen 2 fallback binding for vind nodes in DT for r8a7790 SoC.
This has no run-time effect for the current driver as the initialisation
sequence is the same for the SoC-specific binding for r8a7790 and the
fallback binding for R-Car Gen 2
Signed-off-by: Simon Horman
Use R-Car Gen 2 fallback binding for vind nodes in DT for r8a7791 SoC.
This has no run-time effect for the current driver as the initialisation
sequence is the same for the SoC-specific binding for r8a7791 and the
fallback binding for R-Car Gen 2
Signed-off-by: Simon Horman
On 07/11/2017 03:20 PM, Chris Paterson wrote:
Add a new compatible string for the RZ/G1M (R8A7743) SoC.
Signed-off-by: Biju Das
---
v1->v2
* Changed the subject
* re-formatted the required properties
.../devicetree/bindings/net/renesas,ravb.txt | 29
On 07/11/2017 03:21 PM, Simon Horman wrote:
Add a new compatible string for the RZ/G1M (R8A7743) SoC.
Signed-off-by: Biju Das
---
v1->v2
* Changed the subject
* re-formatted the required properties
.../devicetree/bindings/net/renesas,ravb.txt | 29
Add fallback compatibility string for R-Car Gen 1, 2 and 3.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship
between IP blocks might be. For example, I believe that r8a7790 is older
than r8a7791
On Tue, Jul 11, 2017 at 03:12:14PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 07/10/2017 06:32 PM, Biju Das wrote:
>
> >Add a new compatible string for the RZ/G1M (R8A7743) SoC.
> >
> >Signed-off-by: Biju Das
> >---
> >v1->v2
> >* Changed the subject
> >*
Hello Sergei,
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: 11 July 2017 13:12
>
> Hello!
>
> On 07/10/2017 06:32 PM, Biju Das wrote:
>
> > Add a new compatible string for the RZ/G1M (R8A7743) SoC.
> >
> > Signed-off-by: Biju Das
> > ---
Hello!
On 07/10/2017 06:32 PM, Biju Das wrote:
Add a new compatible string for the RZ/G1M (R8A7743) SoC.
Signed-off-by: Biju Das
---
v1->v2
* Changed the subject
* re-formatted the required properties
.../devicetree/bindings/net/renesas,ravb.txt | 29
Remove support for the SH7372 (SH-Mobile AP4) from the renesas-tpu driver.
Commit edf4100906044225 ("ARM: shmobile: sh7372 dtsi: Remove Legacy file")
removes this SoC from the kernel in v4.1.
Acked-by: Geert Uytterhoeven
Signed-off-by: Simon Horman
On Thu, Nov 24, 2016 at 11:58:43AM +0100, Simon Horman wrote:
> Hi Magnus,
>
> On Mon, Mar 14, 2016 at 11:23:42PM +0900, Magnus Damm wrote:
> > clocksource: sh_cmt: DT binding rework V4
> >
> > [PATCH v4 01/06] devicetree: bindings: Remove sh7372 CMT binding
> > [PATCH v4 02/06] devicetree:
Add fallback compatibility string for R-Car Gen 2 and 3.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 1 and 2. But beyond that its not clear what the relationship
between IP blocks might be. For example, I believe that r8a7790 is older
than r8a7791
Hi Rob,
On Tue, Jul 11, 2017 at 12:37 PM, Rob Landley wrote:
> On 07/11/2017 03:59 AM, Geert Uytterhoeven wrote:
>> On Tue, Jul 11, 2017 at 10:42 AM, Arnd Bergmann wrote:
>>> On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
>>> wrote:
On 07/11/2017 03:59 AM, Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Tue, Jul 11, 2017 at 10:42 AM, Arnd Bergmann wrote:
>> On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
>> wrote:
>>> On Tue, Jul 11, 2017 at 5:38 AM, Magnus Damm
On Mon, Jul 10, 2017 at 04:31:38PM +0300, Laurent Pinchart wrote:
> On Monday 26 Jun 2017 19:29:28 Laurent Pinchart wrote:
> > Hello,
> >
> > This patch series enable DU support in DT for the R-Car H3 ES2.0 Salvator-X
> > board. Patch 1/2 extends the DT bindings as needed, and patch 2/2 then
> >
On Mon, Jul 10, 2017 at 03:28:13PM +0200, Geert Uytterhoeven wrote:
> Hi Arnd, Kevin, Magnus, Olof, Simon,
>
> This patch series updates shmobile_defconfig and multi_v7_defconfig to
> (re-)enable some features:
> - Re-enable R-Car PCIe (shmobile_defconfig),
> - Re-enable R-Car XHCI
On Mon, Jul 10, 2017 at 05:51:09PM +0200, Geert Uytterhoeven wrote:
> On Mon, Jul 10, 2017 at 5:32 PM, Biju Das wrote:
> > Add a new compatible string for the RZ/G1M (R8A7743) SoC.
> >
> > Signed-off-by: Biju Das
>
> Reviewed-by: Geert
On Fri, Jul 07, 2017 at 05:36:16AM +0300, Vladimir Barinov wrote:
> Hello,
>
> This patch series enables HDMI support for the H3 and M3-W based ULCB boards
>
> This has the following dependency:
> - [PATCH v2 series] R-Car Salvator-X M3-W: Enable DU support
> - [PATCH] arm64: dts: renesas: ulcb:
On Mon, Jul 10, 2017 at 11:25:31AM +0200, Simon Horman wrote:
> On Mon, Jun 26, 2017 at 10:56:42AM -0500, Rob Herring wrote:
> > On Wed, Jun 21, 2017 at 12:31:27PM +0300, Laurent Pinchart wrote:
> > > The M3-W HDMI TX controller seems to be compatible for the H3. No
> > > extension to the DT
On Mon, Jul 10, 2017 at 12:49:45PM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Monday 10 Jul 2017 11:07:50 Simon Horman wrote:
> > On Wed, Jun 21, 2017 at 03:17:30PM +0300, Laurent Pinchart wrote:
> > > Add the HDMI encoder to the R8A7796 DT in disabled state.
> > >
> > > Signed-off-by:
Hi Arnd,
On Tue, Jul 11, 2017 at 10:42 AM, Arnd Bergmann wrote:
> On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
> wrote:
>> On Tue, Jul 11, 2017 at 5:38 AM, Magnus Damm wrote:
>>> On Mon, Jul 10, 2017 at 10:28 PM, Geert
Hi Arnd,
On Tue, Jul 11, 2017 at 10:39 AM, Arnd Bergmann wrote:
> On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
> wrote:
>
>> Whether we want to hide the option (and default to y if ARCH_RENESAS, i.e.
>> ARM) is another question. Note that that
On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
wrote:
> Hi Magnus,
>
> On Tue, Jul 11, 2017 at 5:38 AM, Magnus Damm wrote:
>> On Mon, Jul 10, 2017 at 10:28 PM, Geert Uytterhoeven
>> Since enabling DMA Engine still keeps PIO support around I
On Tue, Jul 11, 2017 at 8:59 AM, Geert Uytterhoeven
wrote:
> Whether we want to hide the option (and default to y if ARCH_RENESAS, i.e.
> ARM) is another question. Note that that wouldn't reduce code
> maintainability,
> as the #ifdefs would be kept, and it would prevent
On Tue, Jul 11, 2017 at 4:47 AM, Vladimir Barinov
wrote:
> From: Vladimir Barinov
>
> The ULCB board has one HDMI output connector.
>
> This connector is available on both the H3 and M3-W ULCB boards.
> Add this to
Hi Magnus,
On Tue, Jul 11, 2017 at 5:38 AM, Magnus Damm wrote:
> On Mon, Jul 10, 2017 at 10:28 PM, Geert Uytterhoeven
> wrote:
>> DMA for (H)SCIF(A|B) serial ports on Renesas R-Car Gen2 and RZ/G1 SoCs
>> is considered stable, hence enable it by
49 matches
Mail list logo