From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Hiep Cao Minh" <cm-hiep@jinso.co.jp>,
"Xuan Truong Nguyen" <nx-truong@jinso.co.jp>,
duclm <lm-duc@jinso.co.jp>,
"Ryusuke Sakato" <ryusuke.sakato.bx@renesas.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
稲吉 <h-inayoshi@jinso.co.jp>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
Dung:人ソ <nv-dung@jinso.co.jp>,
"Simon Horman" <horms+renesas@verge.net.au>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Wolfram Sang" <wsa@sang-engineering.com>
Subject: Re: GEN2: Initialization of VSP1 failed at upstream v4.8-rc2
Date: Mon, 12 Sep 2016 13:31:07 +0300 [thread overview]
Message-ID: <14183308.lEBcY4YWhy@avalon> (raw)
In-Reply-To: <CAMuHMdWouXw1Cen8wyoHFHEYQpOvwOg3gLGpA2VtDUerk1iqbg@mail.gmail.com>
Hello,
On Monday 12 Sep 2016 11:06:02 Geert Uytterhoeven wrote:
> On Mon, Sep 12, 2016 at 10:57 AM, Hiep Cao Minh <cm-hiep@jinso.co.jp> wrote:
> > As you know the information about Initialization of VSP1 failed at
> > upstream v4.8-rc2 from the report of "The failure summary report of GEN2
> > for Linux v4.8-rc2".
> >
> > "[ 5.237049] vsp1: probe of fe920000.vsp1 failed with error -38
> > [ 5.254664] vsp1: probe of fe928000.vsp1 failed with error -38
> > [ 5.272277] vsp1: probe of fe930000.vsp1 failed with error -38
> > [ 5.289891] vsp1: probe of fe938000.vsp1 failed with error -38"
> >
> > I have found the patch that causing of this issue:
> > "94fcdf8 [media] v4l: vsp1: Add FCP support"
> >
> > In this patch,
> >
> > "@@ -528,7 +533,7 @@ static int vsp1_pm_runtime_resume(struct device *dev)
> > return ret;
> > }
> >
> > - return 0;
> > + return rcar_fcp_enable(vsp1->fcp);
> > }"
> >
> > vsp1_pm_runtime_resume() function should be returned "0" if it success.
> > I tried to debug this place, and I realize that the rcar_fcp_enable()
> > function returned "-38" during Initialization.
> > That's why the error message occurs.
> > We know that the rcar_fcp_enable() function also returns 0 on success or a
> > negative error code if an error occurs.
> > So, I am thinking of something just before it happens.
>
> Please see commits d0cd1e773fee06ed "[media] rcar-fcp: Make sure
> rcar_fcp_enable() returns 0 on success" in renesas-drivers and
> ba75faf43dc60744 in media-next.
>
> But we indeed need this fix in v4.8, not v4.9.
Mauro, you've queued
commit ba75faf43dc60744608ffa1412fdeceff2126cbc
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date: Tue Aug 9 12:36:41 2016 -0300
[media] rcar-fcp: Make sure rcar_fcp_enable() returns 0 on success
to the media tree master branch, but it fixes a v4.8 regression. Could you
please apply it to the fixes branch and push it upstream for v4.8 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-09-12 10:30 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 [this message]
[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
[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=14183308.lEBcY4YWhy@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=cm-hiep@jinso.co.jp \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=h-inayoshi@jinso.co.jp \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lm-duc@jinso.co.jp \
--cc=magnus.damm@gmail.com \
--cc=mchehab@osg.samsung.com \
--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.