SUPERH platform development
 help / color / mirror / Atom feed
* Rcar-du Initialization errors on Koelsch
@ 2015-02-23  5:08 Cao Minh Hiep
  2015-02-23 23:47 ` Laurent Pinchart
  2015-02-24  0:43 ` Cao Minh Hiep
  0 siblings, 2 replies; 3+ messages in thread
From: Cao Minh Hiep @ 2015-02-23  5:08 UTC (permalink / raw)
  To: linux-sh

Hi Laurent-san
I am Hiep from Jinzai Solution.

We have tested the linux ver 3.19 on Koelsch, we found some error 
messages from Rcar-Du as show below:
The error messages:
"[drm] Initialized drm 1.1.0 20060810
  rcar-du feb00000.display: Failed to initialize drm fb helper.
  rcar-du feb00000.display: failed to initialize DRM/KMS
  rcar-du: probe of feb00000.display failed with error -22"

Then, we find out these patches as below are causing of this bug:
0ee56d4 ARM: shmobile: koelsch: Enable DU device in DT
910343e ARM: shmobile: koelsch-reference: Remove DU platform device

Please see them when you have time!

Best Regards,
Jinso/Cao Minh Hiep.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Rcar-du Initialization errors on Koelsch
  2015-02-23  5:08 Rcar-du Initialization errors on Koelsch Cao Minh Hiep
@ 2015-02-23 23:47 ` Laurent Pinchart
  2015-02-24  0:43 ` Cao Minh Hiep
  1 sibling, 0 replies; 3+ messages in thread
From: Laurent Pinchart @ 2015-02-23 23:47 UTC (permalink / raw)
  To: linux-sh

Hi Hiep-san,

On Monday 23 February 2015 14:08:16 Cao Minh Hiep wrote:
> Hi Laurent-san
> I am Hiep from Jinzai Solution.
> 
> We have tested the linux ver 3.19 on Koelsch, we found some error
> messages from Rcar-Du as show below:
> The error messages:
> "[drm] Initialized drm 1.1.0 20060810
>   rcar-du feb00000.display: Failed to initialize drm fb helper.
>   rcar-du feb00000.display: failed to initialize DRM/KMS
>   rcar-du: probe of feb00000.display failed with error -22"
> 
> Then, we find out these patches as below are causing of this bug:
> 0ee56d4 ARM: shmobile: koelsch: Enable DU device in DT
> 910343e ARM: shmobile: koelsch-reference: Remove DU platform device

This is due to the fact that no connector has been instantiated. The error 
message is pretty confusing, I'll submit a patch to make it clearer, but it 
won't fix the issue.

With the platform data based DU instantiation the Lager and Koelsch board file 
contained LVDS panel information, and the DU driver instantiated one LVDS 
connector. I wanted to replicate that when moving to DT, but the approach has 
been rejected during review due to the fact that the panel isn't part of the 
Lager and Koelsch boards, and thus shouldn't be described in r8a7790-lager.dts 
or r8a7791-koelsch.dts.

I've thus created a separate DT file (r8a77xx-aa104xd12-panel.dtsi) to 
describe the panel, which can be included directly in r8a7790-lager.dts or 
r8a7791-koelsch.dts as in the following patch.

Please note that the patch won't be upstreamed due to the reason explained 
above.

commit eca4ad5b98775c9a8cf5ee03598c3e5421f65030
Author: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Date:   Fri Oct 24 14:53:13 2014 +0300

    ARM: shmobile: koelsch: Add panel to DT
    
    Signed-off-by: Laurent Pinchart 
<laurent.pinchart+renesas@ideasonboard.com>

diff --git a/arch/arm/boot/dts/r8a7791-koelsch.dts 
b/arch/arm/boot/dts/r8a7791-koelsch.dts
index 624bb2c30513..5119ed12fe63 100644
--- a/arch/arm/boot/dts/r8a7791-koelsch.dts
+++ b/arch/arm/boot/dts/r8a7791-koelsch.dts
@@ -648,3 +648,5 @@
 &ssi1 {
 	shared-pin;
 };
+
+#include "r8a77xx-aa104xd12-panel.dtsi"

-- 
Regards,

Laurent Pinchart


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: Rcar-du Initialization errors on Koelsch
  2015-02-23  5:08 Rcar-du Initialization errors on Koelsch Cao Minh Hiep
  2015-02-23 23:47 ` Laurent Pinchart
@ 2015-02-24  0:43 ` Cao Minh Hiep
  1 sibling, 0 replies; 3+ messages in thread
From: Cao Minh Hiep @ 2015-02-24  0:43 UTC (permalink / raw)
  To: linux-sh

Hi Laurent-san

Thanks for your replying.

On 2015年02月24日 08:47, Laurent Pinchart wrote:
> Hi Hiep-san,
>
> On Monday 23 February 2015 14:08:16 Cao Minh Hiep wrote:
>> Hi Laurent-san
>> I am Hiep from Jinzai Solution.
>>
>> We have tested the linux ver 3.19 on Koelsch, we found some error
>> messages from Rcar-Du as show below:
>> The error messages:
>> "[drm] Initialized drm 1.1.0 20060810
>>    rcar-du feb00000.display: Failed to initialize drm fb helper.
>>    rcar-du feb00000.display: failed to initialize DRM/KMS
>>    rcar-du: probe of feb00000.display failed with error -22"
>>
>> Then, we find out these patches as below are causing of this bug:
>> 0ee56d4 ARM: shmobile: koelsch: Enable DU device in DT
>> 910343e ARM: shmobile: koelsch-reference: Remove DU platform device
> This is due to the fact that no connector has been instantiated. The error
> message is pretty confusing, I'll submit a patch to make it clearer, but it
> won't fix the issue.
>
> With the platform data based DU instantiation the Lager and Koelsch board file
> contained LVDS panel information, and the DU driver instantiated one LVDS
> connector. I wanted to replicate that when moving to DT, but the approach has
> been rejected during review due to the fact that the panel isn't part of the
> Lager and Koelsch boards, and thus shouldn't be described in r8a7790-lager.dts
> or r8a7791-koelsch.dts.
Thanks. I understood.
> I've thus created a separate DT file (r8a77xx-aa104xd12-panel.dtsi) to
> describe the panel, which can be included directly in r8a7790-lager.dts or
> r8a7791-koelsch.dts as in the following patch.
>
> Please note that the patch won't be upstreamed due to the reason explained
> above.
Ok, I see.

Best Regards,
Jinso/Hiep

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-02-24  0:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-23  5:08 Rcar-du Initialization errors on Koelsch Cao Minh Hiep
2015-02-23 23:47 ` Laurent Pinchart
2015-02-24  0:43 ` Cao Minh Hiep

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox