All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuan Truong Nguyen <nx-truong@jinso.co.jp>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: duclm <lm-duc@jinso.co.jp>,
	ryusuke.sakato.bx@renesas.com, kuninori.morimoto.gx@renesas.com,
	magnus.damm@gmail.com, geert+renesas@glider.be,
	h-inayoshi@jinso.co.jp, yoshihiro.shimoda.uh@renesas.com,
	nv-dung@jinso.co.jp, cm-hiep@jinso.co.jp,
	laurent.pinchart+renesas@ideasonboard.com,
	horms+renesas@verge.net.au, linux-renesas-soc@vger.kernel.org,
	wsa@sang-engineering.com
Subject: Re: The failure summary report of GEN2 for linux stable v4.8
Date: Fri, 11 Nov 2016 11:44:37 +0900	[thread overview]
Message-ID: <b0a73d94-6f5f-de40-7790-c91af576f96e@jinso.co.jp> (raw)
In-Reply-To: <2073526.U7B9OGNC0q@avalon>

Hi Laurent

please check this when you have time.

If you need any information,  let us know.

thanks and best regard

JINSO/Truong


On 2016年11月11日 10:31, Laurent Pinchart wrote:
> Hello Truong,
>
> On Friday 21 Oct 2016 14:20:24 Laurent Pinchart wrote:
>> On Friday 21 Oct 2016 19:53:47 Xuan Truong Nguyen wrote:
>>> Hello Laurent.
>>>
>>>> The document mentions that you have used shmobile_defconfig. However,
>>>> that configuration in v4.8 doesn't enable CONFIG_CMA, which causes at
>>>> least the DU driver to fail probing the device. I thus assume you have
>>>> modified the configuration to enable CMA. The fact that
>>>> shmobile_defconfig doesn't include the uvcvideo driver used by test 14
>>>> seems to confirm local modifications to the configuration.
>>>> Issue 8 ("Lager: bad image quality when shown on HDMI display") can't be
>>>> reproduced on my system when displaying a test pattern with the modetest
>>>> application. Could you please share more information on how to reproduce
>>>> the problem ?
>>> We retested this issue No 8 again with the CONFIG_CMA enabled but the
>>> result is the same. you could see it by the error.jpg image in
>>> attachments. the display device used is Panasonic TH-L19C3 (refer the
>>> device.jpg). we also send you my configs file, too (lager_du.config).
>> Thank you for the information, I'll try to reproduce the problem here with
>> your kernel configuration.
> I've been able to reproduce the problem here, and at this point I'm not sure
> what goes wrong. I've tested older kernels up to the point where HDMI support
> for Lager was introduced, and the bug was present in all of them. I'll try to
> fix it, but I have other higher priority tasks at the moment.
>
>>> just one more thing, with CONFIG_CMA enabled, the driver fails on
>>> probing if we boot the board without the HDMI cable inserted in advance.
>>> we have to insert the cable before booting the board. and not all the
>>> display work with current HDMI driver (as our LG display will not work)
>>> we are using the mainline upstream version 4.8
>> Interesting, I'll check that too.
> I haven't had time to check this yet.
>
>>> if you need any information to debug, please lets us know.
>> Could you please tell me what you're using to test the display ?

  reply	other threads:[~2016-11-11  2:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57A46D20.7040106@jinso.co.jp>
     [not found] ` <57C9764F.2070802@jinso.co.jp>
     [not found]   ` <f2bb791e-8973-10a9-a2ac-1a944b38d4ad@jinso.co.jp>
2016-09-12  8:57     ` GEN2: Initialization of VSP1 failed at upstream v4.8-rc2 Hiep Cao Minh
2016-09-12  9:06       ` Geert Uytterhoeven
2016-09-12  9:25         ` Hiep Cao Minh
2016-09-12 10:31         ` Laurent Pinchart
     [not found]         ` <57ECF4EA.4010704@jinso.co.jp>
2016-09-29 13:40           ` GEN2:Lager: Only 1 core works when turning off the SW8-PIN4 Geert Uytterhoeven
2016-09-30  9:55             ` Hiep Cao Minh
2016-09-30  9:58               ` Geert Uytterhoeven
2016-09-30 10:05                 ` Hiep Cao Minh
2016-11-07  9:44                   ` Geert Uytterhoeven
2016-11-07 10:37                     ` Hiep Cao Minh
2016-11-07 12:19                       ` Geert Uytterhoeven
2016-09-12  9:33       ` GEN2: Initialization of VIN failed at upstream v4.8-rc2 Hiep Cao Minh
2016-09-12 11:09         ` Niklas Söderlund
2016-09-13  5:12           ` Hiep Cao Minh
     [not found]     ` <9d9a647b-d75f-e89a-2d4d-55e409ccabae@jinso.co.jp>
2016-10-18 13:17       ` The failure summary report of GEN2 for linux stable v4.8 Wolfram Sang
     [not found]         ` <b7e9b4c2-1d5d-2e76-c0f4-fcc50150dc30@jinso.co.jp>
2016-10-24  7:00           ` Geert Uytterhoeven
     [not found]             ` <125b4831-cbdf-f8e1-da97-8ea9cf458c22@jinso.co.jp>
2016-10-24  9:21               ` Geert Uytterhoeven
2016-10-25  2:07                 ` Xuan Truong Nguyen
2016-10-28  8:14                 ` Yoshihiro Shimoda
2016-10-28 10:29                   ` Xuan Truong Nguyen
2016-11-07  0:30                   ` Xuan Truong Nguyen
2016-10-18 14:13       ` Laurent Pinchart
2016-10-18 15:55         ` Laurent Pinchart
2016-10-19  2:39         ` Xuan Truong Nguyen
     [not found]         ` <a101cec4-c9ee-48fa-4f16-5e4cb2b8fab7@jinso.co.jp>
2016-10-21 11:20           ` Laurent Pinchart
2016-10-24  5:51             ` Xuan Truong Nguyen
2016-11-11  1:31             ` Laurent Pinchart
2016-11-11  2:44               ` Xuan Truong Nguyen [this message]
     [not found]       ` <58060015.3020702@jinso.co.jp>
2016-10-19  0:40         ` The failure summary report of GEN3(RCAR H3) " Kuninori Morimoto
2016-10-19  2:45           ` Xuan Truong Nguyen
     [not found]         ` <b4efb8cc-bf55-cf34-a537-4ffa5041291a@jinso.co.jp>
2016-10-31 13:16           ` The failure summary report of GEN3(RCAR H3) for linux upstream v4.9-rc2 Geert Uytterhoeven
2016-11-02  1:29             ` duclm
2016-11-02  7:46               ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0a73d94-6f5f-de40-7790-c91af576f96e@jinso.co.jp \
    --to=nx-truong@jinso.co.jp \
    --cc=cm-hiep@jinso.co.jp \
    --cc=geert+renesas@glider.be \
    --cc=h-inayoshi@jinso.co.jp \
    --cc=horms+renesas@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lm-duc@jinso.co.jp \
    --cc=magnus.damm@gmail.com \
    --cc=nv-dung@jinso.co.jp \
    --cc=ryusuke.sakato.bx@renesas.com \
    --cc=wsa@sang-engineering.com \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.