Rcar Gen2: DU: Bootlogs Error and show image error

Rcar Gen2: DU: Bootlogs Error and show image error

[Cao Minh Hiep]

Hi Laurent-san

Thanks for your kindness support!
I don't mean to bother you!
But as you know, we have reported to you before, have some problems 
related to DU driver.
We couldn't show a image on the display. We found the messages as showed 
below:
-----
Boot logs on Rcar-H2:
rcar-du feb00000.display: failed to initialize encoder 
/i2c@e6520000/hdmi@39 (-38), skipping
rcar-du feb00000.display: fb0:  frame buffer device
-----
Boot logs on Rcar-M2:
rcar-du feb00000.display: failed to initialize encoder 
/i2c@e6530000/hdmi@39 (-g
rcar-du feb00000.display: error: no encoder could be initialized
rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
rcar-du: probe of feb00000.display failed with error -22
-----

This is tested on linux stable v4.3.
Please have a look when you have time.

Best Regards,
Jinso/Cao Minh Hiep.

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Laurent Pinchart]

Hello, and sorry for the late reply.

On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote:
> Hi Laurent-san
> 
> Thanks for your kindness support!
> I don't mean to bother you!

You're not bothering me at all :-)

> But as you know, we have reported to you before, have some problems
> related to DU driver.
> We couldn't show a image on the display. We found the messages as showed
> below:
> -----
> Boot logs on Rcar-H2:
> rcar-du feb00000.display: failed to initialize encoder
> /i2c@e6520000/hdmi@39 (-38), skipping
> rcar-du feb00000.display: fb0:  frame buffer device
> -----
> Boot logs on Rcar-M2:
> rcar-du feb00000.display: failed to initialize encoder
> /i2c@e6530000/hdmi@39 (-g
> rcar-du feb00000.display: error: no encoder could be initialized
> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
> rcar-du: probe of feb00000.display failed with error -22
> -----
> 
> This is tested on linux stable v4.3.
> Please have a look when you have time.

Have you enabled CONFIG_DRM_RCAR_HDMI ?

-- 
Regards,

Laurent Pinchart

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Cao Minh Hiep]

Hi Laurent-san

Thanks for your reply!

On 2015年11月25日 10:08, Laurent Pinchart wrote:
> Hello, and sorry for the late reply.
No, problems!
> On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote:
>> Hi Laurent-san
>>
>> Thanks for your kindness support!
>> I don't mean to bother you!
> You're not bothering me at all :-)
>
>> But as you know, we have reported to you before, have some problems
>> related to DU driver.
>> We couldn't show a image on the display. We found the messages as showed
>> below:
>> -----
>> Boot logs on Rcar-H2:
>> rcar-du feb00000.display: failed to initialize encoder
>> /i2c@e6520000/hdmi@39 (-38), skipping
>> rcar-du feb00000.display: fb0:  frame buffer device
>> -----
>> Boot logs on Rcar-M2:
>> rcar-du feb00000.display: failed to initialize encoder
>> /i2c@e6530000/hdmi@39 (-g
>> rcar-du feb00000.display: error: no encoder could be initialized
>> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
>> rcar-du: probe of feb00000.display failed with error -22
>> -----
>>
>> This is tested on linux stable v4.3.
>> Please have a look when you have time.
> Have you enabled CONFIG_DRM_RCAR_HDMI ?
>
Yes, These initialize logs are taken with default config that 
CONFIG_DRM_RCAR_HDMI disabled at v4.3.
But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show 
any images on HDMI or RGB Screen.

I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default 
config at v4.4-rc2.
But have a error message as below and DU is still not improved(still can 
not show images on screen).


On Rcar-H2(Lager):

[drm] Initialized drm 1.1.0 20060810
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
rcar-du feb00000.display: fb0:  frame buffer device
[drm] Initialized rcar-du 1.0.0 20130110 on minor 0

On Rcar-M2(Koelsch):

[drm] Initialized drm 1.1.0 20060810
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
rcar-du feb00000.display: fb0:  frame buffer device
[drm] Initialized rcar-du 1.0.0 20130110 on minor 0

Thank you!
Jinso/Hiep

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Laurent Pinchart]

Hello,

On Thursday 26 November 2015 11:48:22 Cao Minh Hiep wrote:
> On 2015年11月25日 10:08, Laurent Pinchart wrote:
> > On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote:
> >> Hi Laurent-san
> >> 
> >> Thanks for your kindness support!
> >> I don't mean to bother you!
> > 
> > You're not bothering me at all :-)
> > 
> >> But as you know, we have reported to you before, have some problems
> >> related to DU driver.
> >> We couldn't show a image on the display. We found the messages as showed
> >> below:
> >> -----
> >> Boot logs on Rcar-H2:
> >> rcar-du feb00000.display: failed to initialize encoder
> >> /i2c@e6520000/hdmi@39 (-38), skipping
> >> rcar-du feb00000.display: fb0:  frame buffer device
> >> -----
> >> Boot logs on Rcar-M2:
> >> rcar-du feb00000.display: failed to initialize encoder
> >> /i2c@e6530000/hdmi@39 (-g
> >> rcar-du feb00000.display: error: no encoder could be initialized
> >> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
> >> rcar-du: probe of feb00000.display failed with error -22
> >> -----
> >> 
> >> This is tested on linux stable v4.3.
> >> Please have a look when you have time.
> > 
> > Have you enabled CONFIG_DRM_RCAR_HDMI ?
> 
> Yes, These initialize logs are taken with default config that
> CONFIG_DRM_RCAR_HDMI disabled at v4.3.
> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show
> any images on HDMI or RGB Screen.
> 
> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default
> config at v4.4-rc2.
> But have a error message as below and DU is still not improved(still can
> not show images on screen).
> 
> 
> On Rcar-H2(Lager):
> 
> [drm] Initialized drm 1.1.0 20060810
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] No driver support for vblank timestamp query.
> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
> rcar-du feb00000.display: fb0:  frame buffer device
> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
> 
> On Rcar-M2(Koelsch):
> 
> [drm] Initialized drm 1.1.0 20060810
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] No driver support for vblank timestamp query.
> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
> rcar-du feb00000.display: fb0:  frame buffer device
> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0

-517 (-EPROBE_DEFER) means that probe deferral is requested because a required 
dependency is not present. Have you compiled and loaded the adv7511 driver 
(CONFIG_DRM_I2C_ADV7511) ?

-- 
Regards,

Laurent Pinchart

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Cao Minh Hiep]

Hello Laurent-san,


>>>> But as you know, we have reported to you before, have some problems
>>>> related to DU driver.
>>>> We couldn't show a image on the display. We found the messages as showed
>>>> below:
>>>> -----
>>>> Boot logs on Rcar-H2:
>>>> rcar-du feb00000.display: failed to initialize encoder
>>>> /i2c@e6520000/hdmi@39 (-38), skipping
>>>> rcar-du feb00000.display: fb0:  frame buffer device
>>>> -----
>>>> Boot logs on Rcar-M2:
>>>> rcar-du feb00000.display: failed to initialize encoder
>>>> /i2c@e6530000/hdmi@39 (-g
>>>> rcar-du feb00000.display: error: no encoder could be initialized
>>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
>>>> rcar-du: probe of feb00000.display failed with error -22
>>>> -----
>>>>
>>>> This is tested on linux stable v4.3.
>>>> Please have a look when you have time.
>>> Have you enabled CONFIG_DRM_RCAR_HDMI ?
>> Yes, These initialize logs are taken with default config that
>> CONFIG_DRM_RCAR_HDMI disabled at v4.3.
>> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show
>> any images on HDMI or RGB Screen.
>>
>> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default
>> config at v4.4-rc2.
>> But have a error message as below and DU is still not improved(still can
>> not show images on screen).
>>
>>
>> On Rcar-H2(Lager):
>>
>> [drm] Initialized drm 1.1.0 20060810
>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [drm] No driver support for vblank timestamp query.
>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
>> rcar-du feb00000.display: fb0:  frame buffer device
>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
>>
>> On Rcar-M2(Koelsch):
>>
>> [drm] Initialized drm 1.1.0 20060810
>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [drm] No driver support for vblank timestamp query.
>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
>> rcar-du feb00000.display: fb0:  frame buffer device
>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
> -517 (-EPROBE_DEFER) means that probe deferral is requested because a required
> dependency is not present. Have you compiled and loaded the adv7511 driver
> (CONFIG_DRM_I2C_ADV7511) ?
>
Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at 
v4.4-rc2.
I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI 
then test.
But It has nothing change.
Is there other configuration or reason could we think?

we usually use Morimoto-san's the bmap tool to show a image as below:
./bmap /dev/fb0 ./hdmi.bmp
It is good for showing a image in bsp version ltsi-v3.10.31-rcar/gen2-1.9.5.


Thank you!
Jinso/Hiep

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Cao Minh Hiep]

Hi Laurent-san

Sorry to bother you again!

On 2015年11月27日 15:13, Cao Minh Hiep wrote:
> Hello Laurent-san,
>
>
>>>>> But as you know, we have reported to you before, have some problems
>>>>> related to DU driver.
>>>>> We couldn't show a image on the display. We found the messages as 
>>>>> showed
>>>>> below:
>>>>> -----
>>>>> Boot logs on Rcar-H2:
>>>>> rcar-du feb00000.display: failed to initialize encoder
>>>>> /i2c@e6520000/hdmi@39 (-38), skipping
>>>>> rcar-du feb00000.display: fb0:  frame buffer device
>>>>> -----
>>>>> Boot logs on Rcar-M2:
>>>>> rcar-du feb00000.display: failed to initialize encoder
>>>>> /i2c@e6530000/hdmi@39 (-g
>>>>> rcar-du feb00000.display: error: no encoder could be initialized
>>>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-22)
>>>>> rcar-du: probe of feb00000.display failed with error -22
>>>>> -----
>>>>>
>>>>> This is tested on linux stable v4.3.
>>>>> Please have a look when you have time.
>>>> Have you enabled CONFIG_DRM_RCAR_HDMI ?
>>> Yes, These initialize logs are taken with default config that
>>> CONFIG_DRM_RCAR_HDMI disabled at v4.3.
>>> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show
>>> any images on HDMI or RGB Screen.
>>>
>>> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default
>>> config at v4.4-rc2.
>>> But have a error message as below and DU is still not improved(still 
>>> can
>>> not show images on screen).
>>>
>>>
>>> On Rcar-H2(Lager):
>>>
>>> [drm] Initialized drm 1.1.0 20060810
>>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>>> [drm] No driver support for vblank timestamp query.
>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
>>> rcar-du feb00000.display: fb0:  frame buffer device
>>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
>>>
>>> On Rcar-M2(Koelsch):
>>>
>>> [drm] Initialized drm 1.1.0 20060810
>>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>>> [drm] No driver support for vblank timestamp query.
>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
>>> rcar-du feb00000.display: fb0:  frame buffer device
>>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
>> -517 (-EPROBE_DEFER) means that probe deferral is requested because a 
>> required
>> dependency is not present. Have you compiled and loaded the adv7511 
>> driver
>> (CONFIG_DRM_I2C_ADV7511) ?
>>
> Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at 
> v4.4-rc2.
> I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI 
> then test.
> But It has nothing change.
> Is there other configuration or reason could we think?
>

Does this problem happen on your board?
If not, Could you please send me your config file?.


Thank you!
Jinso/Hiep

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Laurent Pinchart]

Hello Cao Minh-san,

(this is a bit of a stupid question, and I apologize for that, but what is the 
proper way to address you, Cao-san, Cao Minh-san, Hiep-san, or something else 
?)

On Thursday 10 December 2015 10:43:18 Cao Minh Hiep wrote:
> 
> >>> Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at
> >>> v4.4-rc2.
> >>> I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI
> >>> then test.
> >>> But It has nothing change.
> >>> Is there other configuration or reason could we think?
> >> 
> >> Does this problem happen on your board?
> >> If not, Could you please send me your config file?.
> > 
> > Sorry for the delay, I wanted to retry on my Koelsch board before
> > replying.
> > 
> > The probe deferral error (-517) you're seeing is normal, it comes from the
> > DU being probed before its dependencies. Probe is deferred and retried,
> > and finally succeeds as shown by
> > 
> > [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
> > 
> > With a stock v4.4-rc2 kernel I get the same result, and I can then use the
> > HDMI output without any issue with the modetest application.
> > 
> > I've attached the kernel configuration I used for testing, just in case.
> 
> Thanks, I have changed our HDMI display device(Old one -> other newer one),
> and then I could show a image on the display successfully. This test is
> on Koelsch board.
> But I found that, before showing the image on HDMI display,
> I have to enable CONFIG_FRAMEBUFFER_CONSOLE =y or
> run a command something like "fbset -xres 640 -yres 480 -laced 0", in
> order to clear the first screen.
> 
> On Lager, with the same test method, I could show a image on RGB display
> very well,
> but when I showed image on HDMI display, The image showed on display
> looks bad as attached picture.
> The attached picture: HDMI-Display-image-showed-from-Lager.jpg
> 
> Please have a look and show me what i have to do!

I'll try to reproduce that. Could you please send me the image file and the 
exact test procedure ?

-- 
Regards,

Laurent Pinchart

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Laurent Pinchart]

Hello Hiep-san,

On Tuesday 28 Jun 2016 10:19:20 Hiep Cao Minh wrote:
> Hi Laurent-san
> 
> Sorry to bother you again!
> I would like to confirm the fixed patch for this issue on Lager.
> I have retested it on Lager(Rcar-H2), The issue still happens at the
> Linux upstream version v4.7-rc2
> Have you released the fixed patch?
> Please tell me the version and test method if you have already released it.
> I resent the damage image when displaying it on the HDMI screen.

I'm currently traveling and have only taken my H3 board with me, so I don't 
have access to Lager. I'll be back home on the 5th of July and then test this. 
Sorry for the delay.

> On 12/17/2015 03:37 PM, Cao Minh Hiep wrote:
> > Hello Laurent-san
> > 
> > On 2015年12月14日 04:45, Laurent Pinchart wrote:
> >> Hello Cao Minh-san,
> >> 
> >> (this is a bit of a stupid question, and I apologize for that, but
> >> what is the
> >> proper way to address you, Cao-san, Cao Minh-san, Hiep-san, or
> >> something else
> >> ?)
> > 
> > No problems! :) , Hiep is my name! Every one calls me Hiep,
> > 
> >> On Thursday 10 December 2015 10:43:18 Cao Minh Hiep wrote:
> >>>>>> Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default
> >>>>>> config at
> >>>>>> v4.4-rc2.
> >>>>>> I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI
> >>>>>> then test.
> >>>>>> But It has nothing change.
> >>>>>> Is there other configuration or reason could we think?
> >>>>> 
> >>>>> Does this problem happen on your board?
> >>>>> If not, Could you please send me your config file?.
> >>>> 
> >>>> Sorry for the delay, I wanted to retry on my Koelsch board before
> >>>> replying.
> >>>> 
> >>>> The probe deferral error (-517) you're seeing is normal, it comes
> >>>> from the
> >>>> DU being probed before its dependencies. Probe is deferred and
> >>>> retried,
> >>>> and finally succeeds as shown by
> >>>> 
> >>>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0
> >>>> 
> >>>> With a stock v4.4-rc2 kernel I get the same result, and I can then
> >>>> use the
> >>>> HDMI output without any issue with the modetest application.
> >>>> 
> >>>> I've attached the kernel configuration I used for testing, just in
> >>>> case.
> >>> 
> >>> Thanks, I have changed our HDMI display device(Old one -> other
> >>> newer one),
> >>> and then I could show a image on the display successfully. This test is
> >>> on Koelsch board.
> >>> But I found that, before showing the image on HDMI display,
> >>> I have to enable CONFIG_FRAMEBUFFER_CONSOLE =y or
> >>> run a command something like "fbset -xres 640 -yres 480 -laced 0", in
> >>> order to clear the first screen.
> >>> 
> >>> On Lager, with the same test method, I could show a image on RGB
> >>> display
> >>> very well,
> >>> but when I showed image on HDMI display, The image showed on display
> >>> looks bad as attached picture.
> >>> The attached picture: HDMI-Display-image-showed-from-Lager.jpg
> >>> 
> >>> Please have a look and show me what i have to do!
> >> 
> >> I'll try to reproduce that. Could you please send me the image file
> >> and the
> >> exact test procedure ?
> > 
> > I tested on v4.4-rc2 on Lager board.
> > 
> > CONFIG_DRM_RCAR_HDMI=y
> > CONFIG_DRM_I2C_ADV7511=y
> > VIDEO_ADV7511=y
> > CONFIG_FRAMEBUFFER_CONSOLE =y
> > 
> > I used the Morimoto-san's bmap tool to show image file.
> > ./bmap /dev/fb0 ./picture.bmp
> > 
> > I attach bmap file and the image file "picture.bmp".
> > 
> > Regards,
> > Jinso/Hiep.

-- 
Regards,

Laurent Pinchart

[PATCH] pinctrl: sh-pfc: r8a7795: Rename SEL_SCIF to SEL_SATA

[Geert Uytterhoeven]

Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet.

This has no user-visible impact.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7795.c b/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
index 29d001b8a727e154..bb5f37cbb9502d5f 100644
--- a/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
+++ b/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
@@ -495,7 +495,7 @@ FM(IP16_31_28)	IP16_31_28
 #define MOD_SEL1_13		FM(SEL_SCIF3_0)		FM(SEL_SCIF3_1)
 #define MOD_SEL1_12		FM(SEL_SCIF2_0)		FM(SEL_SCIF2_1)
 #define MOD_SEL1_11		FM(SEL_SCIF1_0)		FM(SEL_SCIF1_1)
-#define MOD_SEL1_10		FM(SEL_SCIF_0)		FM(SEL_SCIF_1)
+#define MOD_SEL1_10		FM(SEL_SATA_0)		FM(SEL_SATA_1)
 #define MOD_SEL1_9		FM(SEL_REMOCON_0)	FM(SEL_REMOCON_1)
 #define MOD_SEL1_6		FM(SEL_RCAN0_0)		FM(SEL_RCAN0_1)
 #define MOD_SEL1_5		FM(SEL_PWM6_0)		FM(SEL_PWM6_1)
@@ -1033,7 +1033,7 @@ static const u16 pinmux_data[] = {
 	PINMUX_IPSR_DATA(IP9_19_16,	SD2_DAT3),
 
 	PINMUX_IPSR_DATA(IP9_23_20,	SD2_DS),
-	PINMUX_IPSR_MSEL(IP9_23_20,	SATA_DEVSLP_B,		SEL_SCIF_1),
+	PINMUX_IPSR_MSEL(IP9_23_20,	SATA_DEVSLP_B,		SEL_SATA_1),
 
 	PINMUX_IPSR_DATA(IP9_27_24,	SD3_DAT4),
 	PINMUX_IPSR_MSEL(IP9_27_24,	SD2_CD_A,		SEL_SDHI2_0),
@@ -1293,7 +1293,7 @@ static const u16 pinmux_data[] = {
 
 	PINMUX_IPSR_DATA(IP15_11_8,	SSI_SDATA6),
 	PINMUX_IPSR_MSEL(IP15_11_8,	SIM0_CLK_D,		SEL_SIMCARD_3),
-	PINMUX_IPSR_MSEL(IP15_11_8,	SATA_DEVSLP_A,		SEL_SCIF_0),
+	PINMUX_IPSR_MSEL(IP15_11_8,	SATA_DEVSLP_A,		SEL_SATA_0),
 
 	PINMUX_IPSR_DATA(IP15_15_12,	SSI_SCK78),
 	PINMUX_IPSR_MSEL(IP15_15_12,	HRX2_B,			SEL_HSCIF2_1),
-- 
1.9.1

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Laurent Pinchart]

Hello Hiep-san,

(Dropping the linux-sh mailing list and adding linux-renesas-soc)

On Tuesday 28 Jun 2016 10:19:20 Hiep Cao Minh wrote:
> Hi Laurent-san
> 
> Sorry to bother you again!
> I would like to confirm the fixed patch for this issue on Lager.
> I have retested it on Lager(Rcar-H2), The issue still happens at the
> Linux upstream version v4.7-rc2
> Have you released the fixed patch?
> Please tell me the version and test method if you have already released it.
> I resent the damage image when displaying it on the HDMI screen.

I've finally been able to test the problem you have reported on the Lager 
board.

There is a new issue introduced in the current merging window that completely 
breaks HDMI output on Lager. I have posted a fix to the dri-devel and linux-
renesas-soc mailing lists under the subject "[PATCH] drm: rcar-du: Link HDMI 
encoder with bridge". I will make sure that it lands in v4.8 (hopefully in 
v4.8-rc1, but it might have to wait for v4.8-rc2).

With the fix applied to Linus' latest master branch (the commid ID I used is 
f7b32e4c021fd788f13f6785e17efbc3eb05b351) HDMI output works properly on Lager 
for me. Running your test application displays the image correctly on my 
screen.

Could you check whether you can reproduce the problem with the latest kernel ?

-- 
Regards,

Laurent Pinchart

Re: Rcar Gen2: DU: Bootlogs Error and show image error

[Hiep Cao Minh]

Hello Laurent-san,

Thanks for your reply!

>> Hi Laurent-san
>>
>> Sorry to bother you again!
>> I would like to confirm the fixed patch for this issue on Lager.
>> I have retested it on Lager(Rcar-H2), The issue still happens at the
>> Linux upstream version v4.7-rc2
>> Have you released the fixed patch?
>> Please tell me the version and test method if you have already released it.
>> I resent the damage image when displaying it on the HDMI screen.
> I've finally been able to test the problem you have reported on the Lager
> board.
>
> There is a new issue introduced in the current merging window that completely
> breaks HDMI output on Lager. I have posted a fix to the dri-devel and linux-
> renesas-soc mailing lists under the subject "[PATCH] drm: rcar-du: Link HDMI
> encoder with bridge". I will make sure that it lands in v4.8 (hopefully in
> v4.8-rc1, but it might have to wait for v4.8-rc2).
>
> With the fix applied to Linus' latest master branch (the commid ID I used is
> f7b32e4c021fd788f13f6785e17efbc3eb05b351) HDMI output works properly on Lager
> for me. Running your test application displays the image correctly on my
> screen.
>
> Could you check whether you can reproduce the problem with the latest kernel ?
Thanks for your patch!,
Currently, I could not confirm your patch on latest kernel v4.7 because 
of source code is unsupported
So I might to wait for  a newer version of Linux mainline.
I also have tried to put it on renesas-drivers latest version, but It is 
the same Linux mainline version.

Could you please tell me the other kernel version that the patch 
comfirmation is possible?.

Thank you!.
Jinso/Hiep.