All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hiep Cao Minh <cm-hiep@jinso.co.jp>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: laurent.pinchart+renesas@ideasonboard.com,
	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, horms+renesas@verge.net.au,
	linux-renesas-soc@vger.kernel.org, wsa@sang-engineering.com,
	harunaga <nx-truong@jinso.co.jp>, 人ソ)ドンさん <cv-dong@jinso.co.jp>,
	"Na Hoan" <na-hoan@jit.vn>
Subject: Re: GEN2: Initialization of VIN failed at upstream v4.8-rc2
Date: Tue, 13 Sep 2016 14:12:54 +0900	[thread overview]
Message-ID: <57D78AD6.2090408@jinso.co.jp> (raw)
In-Reply-To: <20160912110929.GQ27014@bigcity.dyn.berto.se>

Hi Niklas,


On 09/12/2016 08:09 PM, Niklas Söderlund wrote:
> Hi Hiep,
>
> On 2016-09-12 18:33:49 +0900, Hiep Cao Minh wrote:
>> Hi Niklas
>>
>> As you know the information about initialization of VIN failed at upstream
>> v4.8-rc2
>>   from the report of "The failure summary report of GEN2 for Linux v4.8-rc2".
>> "…
>> [ 5.589485] [<c0549114>] (of_node_put) from [<c0510558>]
>> (rcar_vin_probe+0x1c4/0x2d0)
>> [ 5.612949] [<c0510394>] (rcar_vin_probe) from [<c040dd60>]
>> (platform_drv_probe+0x58/0xa4)
>> …
>> [ 5.942909] [<c040e6f0>] (__platform_driver_register) from [<c091fa58>]
>> (rcar_vin_driver_init+0x18/0x20)
>> [ 5.971318] [<c091fa40>] (rcar_vin_driver_init) from [<c0900e44>]
>> (do_one_initcall+0xb4/0x164) ...
>> ...”
>>
>> I have found the patch that causing of this issue:
>> "f00add9 [media] rcar-vin: add Renesas R-Car VIN driver"
>>
>> Please have a look at this issue when you have time.
> Thanks for finding this. I found out about this issue (which is only
> printed if some OF debug option is enabled) after the patch was picked
> up.
>
> The issue is already fixed and picked up in the media tree, see 83fba2c
> ([media] rcar-vin: rework how subdevice is found and bound).
Thanks for your fixed patch, We'll try it on our environment.

Jinso/Linux Team.
Hiep.

  reply	other threads:[~2016-09-13  5:12 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 [this message]
     [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
     [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=57D78AD6.2090408@jinso.co.jp \
    --to=cm-hiep@jinso.co.jp \
    --cc=cv-dong@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=linux-renesas-soc@vger.kernel.org \
    --cc=lm-duc@jinso.co.jp \
    --cc=magnus.damm@gmail.com \
    --cc=na-hoan@jit.vn \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=nv-dung@jinso.co.jp \
    --cc=nx-truong@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.