linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	mchehab@kernel.org, robh+dt@kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	linux-media@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org, agross@kernel.org,
	david.brown@linaro.org, lkft-triage@lists.linaro.org,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: next-20190806: arm64: adv7511 3-0039: failed to find dsi host
Date: Wed, 7 Aug 2019 10:46:33 +0200	[thread overview]
Message-ID: <a9f7c007-8639-0202-c35d-219d371a1842@xs4all.nl> (raw)
In-Reply-To: <CA+G9fYus+cW4775Y2_Xqpc+G6YP_KfjGeCMzoSQq6o2yVY8Q3w@mail.gmail.com>

Adding dri-devel since this appears to be drm specific and not media
related.

Regards,

	Hans

On 8/7/19 10:17 AM, Naresh Kamboju wrote:
> arm64 devices dragonboard 410c (QC410E) and hi6220-hikey running Linux
> next-20190806 loading modules causing floods of kernel messages.
> 
> We have enabled few extra kernel configs for testing.
> CONFIG_DRM_I2C_ADV7511=m
> CONFIG_DRM_I2C_ADV7511_CEC=y
> ...
> 
> Please find below boot log and config file link.
> 
> [    0.000000] Linux version 5.3.0-rc3-next-20190806 (oe-user@oe-host)
> (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Tue Aug 6 05:49:36 UTC 2019
> [    0.000000] Machine model: Qualcomm Technologies, Inc. APQ 8016 SBC
> ....
> [   10.051193] adv7511 3-0039: 3-0039 supply dvdd not found, using
> dummy regulator
> [   10.051633] adv7511 3-0039: 3-0039 supply pvdd not found, using
> dummy regulator
> [   10.076257] adreno 1c00000.gpu: Adding to iommu group 0
> [   10.090929] adv7511 3-0039: 3-0039 supply a2vdd not found, using
> dummy regulator
> [   10.101703] msm_mdp 1a01000.mdp: Adding to iommu group 1
> [   10.102563] msm_mdp 1a01000.mdp: No interconnect support may cause
> display underflows!
> [   10.139492] adv7511 3-0039: failed to find dsi host
> ...
> [   33.065744] adv7511 3-0039: failed to find dsi host
> [   33.076721] msm 1a00000.mdss: 1a00000.mdss supply vdd not found,
> using dummy regulator
> [   33.078344] msm_mdp 1a01000.mdp: [drm:mdp5_bind [msm]] MDP5 version v1.6
> [   33.083862] msm 1a00000.mdss: bound 1a01000.mdp (ops mdp5_ops [msm])
> [   33.090892] msm_dsi 1a98000.dsi: 1a98000.dsi supply gdsc not found,
> using dummy regulator
> [   33.097756] msm_dsi 1a98000.dsi: 1a98000.dsi supply gdsc not found,
> using dummy regulator
> [   33.106606] msm_dsi_manager_register: failed to register mipi dsi
> host for DSI 0
> [   33.114579] msm 1a00000.mdss: failed to bind 1a98000.dsi (ops
> dsi_ops [msm]): -517
> [   33.121263] msm 1a00000.mdss: master bind failed: -517
> [   33.135547] adv7511 3-0039: 3-0039 supply dvdd not found, using
> dummy regulator
> [   33.139360] adv7511 3-0039: 3-0039 supply pvdd not found, using
> dummy regulator
> [   33.143646] adv7511 3-0039: 3-0039 supply a2vdd not found, using
> dummy regulator
> 
> Full test log
> https://lkft.validation.linaro.org/scheduler/job/860208#L956
> 
> metadata:
>   git branch: master
>   git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>   git commit: 958eb4327c1761c609bde8e9f7c04e9d1c6fbb96
>   git describe: next-20190806
>   make_kernelversion: 5.3.0-rc3
>   kernel-config:
> http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-next/579/config
>   kernel-defconfig:
> http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-next/579/defconfig
>   build-location:
> http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-next/579
> 
> Best regards
> Naresh Kamboju
> 


      reply	other threads:[~2019-08-07  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  8:17 next-20190806: arm64: adv7511 3-0039: failed to find dsi host Naresh Kamboju
2019-08-07  8:46 ` Hans Verkuil [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=a9f7c007-8639-0202-c35d-219d371a1842@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=agross@kernel.org \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).