From: Daniel Vetter <daniel@ffwll.ch>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Maxime Ripard <maxime@cerno.tech>,
linux-omap <linux-omap@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [drm:simple_bridge_attach [simple_bridge]] *ERROR* Fix bridge driver to make connector optional!
Date: Tue, 21 Apr 2020 14:18:57 +0200 [thread overview]
Message-ID: <20200421121857.GV3456981@phenom.ffwll.local> (raw)
In-Reply-To: <CB5A5B81-F06C-4CBE-95DE-96C8723D2AC5@goldelico.com>
On Fri, Apr 17, 2020 at 02:18:11PM +0200, H. Nikolaus Schaller wrote:
> Hi Maxime,
> I have started to test v5.7-rc1 and can't fully boot the GTA04
> device any more.
>
> What I see in the log is:
>
> [ 28.567840] [drm:simple_bridge_attach [simple_bridge]] *ERROR* Fix bridge driver to make connector optional!
General PSA (and for Laurent et al, i.e. entire team of people working on all
the varios bridge conversions):
Please don't make something an error before all in-tree users are
converted. Even an informational warning is often too much, even only very
few drivers are left using an old pattern.
-Daniel
> [ 28.567871] omapdrm omapdrm.0: unable to attach bridge /ocp@68000000/dss@48050000/encoder@48050c00
> [ 28.786529] omapdrm omapdrm.0: omap_modeset_init failed: ret=-22
> [ 28.841552] omapdrm: probe of omapdrm.0 failed with error -22
>
> This device uses the ti,opa362 chip which did have a dedicated
> omapdss driver before (which is removed now) and which seems to
> be supported by the simple_bridge now.
>
> The opa362 is sitting in the video out path from
>
> omapdrm -> venc -> opa362 -> video-out-connector.
>
> What does this error mean? How can it be fixed?
>
> BR and thanks,
> Nikolaus
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2020-04-21 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CB5A5B81-F06C-4CBE-95DE-96C8723D2AC5@goldelico.com>
2020-04-17 12:44 ` [drm:simple_bridge_attach [simple_bridge]] *ERROR* Fix bridge driver to make connector optional! Maxime Ripard
2020-04-17 12:58 ` Laurent Pinchart
2020-04-17 13:53 ` H. Nikolaus Schaller
2020-04-21 12:18 ` Daniel Vetter [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=20200421121857.GV3456981@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=maxime@cerno.tech \
/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