All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [Bug Report] Rcar-H2: VIN: Error messages at boot log
Date: Fri, 22 May 2015 00:13:04 +0000	[thread overview]
Message-ID: <555E7490.2090302@jinso.co.jp> (raw)
In-Reply-To: <CAMuHMdVKDou8kOcVvLqJO2C14zYP-hhASWS_4kSShqLdqVq7Jg@mail.gmail.com>

Hi Geert-san
Thank for your feedback!

On 2015年05月21日 16:17, Geert Uytterhoeven wrote:
> Hi Hiep-san,
>
> On Thu, May 21, 2015 at 3:56 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote:
>> We have tested Linux upstream version-4.1-rc2 on Lager and Koelsch.
>> We found a Error message of VIN(Video Input) at boot logs:
>> The error messages is showed as below:
>> "adv7180 6-0020: chip found @ 0x20 (e6520000.i2c)
>> soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
>> rcar_vin e6ef1000.video: group probe failed: -6"
>>
>> We tested it by default config, and Linaro userland v2014.09.
>> Is it a bug?
> I see the same error message in a shmobile_defconfig kernel built from
> renesas-drivers-2015-04-27-v4.1-rc1.
>
> I've just tried a shmobile_defconfig kernel built in a tree based on
> renesas-drivers-2015-05-19-v4.1-rc4, and the error message is gone.
>
> I don't know what fixed it.
I re-tested renesas-drivers-2015-05-19-v4.1-rc4 on my Lager board.
My result test is the same, the error message is gone.

I also checked on upstream v4.1-rc4, but the error massage still has.
I think, there is a patch that fixed it between two versions.

Best Regards,
Hiep.

      reply	other threads:[~2015-05-22  0:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  7:17 [Bug Report] Rcar-H2: VIN: Error messages at boot log Geert Uytterhoeven
2015-05-22  0:13 ` Cao Minh Hiep [this message]

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=555E7490.2090302@jinso.co.jp \
    --to=cm-hiep@jinso.co.jp \
    --cc=linux-sh@vger.kernel.org \
    /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.