All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>,
	Fabio Estevam <festevam@gmail.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	patchwork-lst@pengutronix.de,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Ilia Mirkin <imirkin@alum.mit.edu>,
	linux-clk@vger.kernel.org, Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH] clk: imx51: propagate rate across ipu_di*_sel
Date: Mon, 21 Aug 2017 18:58:19 +0300	[thread overview]
Message-ID: <4d5dbc0a-56b0-52a3-482d-2b3348c9c53b@cogentembedded.com> (raw)
In-Reply-To: <20170821155412.GA24652@amethyst.visucore.com>

> I'm trying to, but getting a non-clock-related problem on the i.mx51 babbage board
> with current kernel preventing the display from coming up at all:
> 
>     [    0.824712] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>     [    0.831411] [drm] No driver support for vblank timestamp query.
>     [    0.837632] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
>     [    0.845214] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
>     [    0.852720] imx-drm display-subsystem: failed to bind display@di0 (ops imx_pd_ops): -19
>     [    0.860994] imx-drm display-subsystem: master bind failed: -19

I believe this should be fixed by

commit 799ee2970485dc206c3bf347d6e6827c04d5e4f9
Author: Philipp Zabel <p.zabel@pengutronix.de>
Date:   Mon Jun 12 17:54:29 2017 +0200

  drm/imx: parallel-display: Accept drm_of_find_panel_or_bridge failure


Nikita

WARNING: multiple messages have this Message-ID (diff)
From: nikita.yoush@cogentembedded.com (Nikita Yushchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: imx51: propagate rate across ipu_di*_sel
Date: Mon, 21 Aug 2017 18:58:19 +0300	[thread overview]
Message-ID: <4d5dbc0a-56b0-52a3-482d-2b3348c9c53b@cogentembedded.com> (raw)
In-Reply-To: <20170821155412.GA24652@amethyst.visucore.com>

> I'm trying to, but getting a non-clock-related problem on the i.mx51 babbage board
> with current kernel preventing the display from coming up at all:
> 
>     [    0.824712] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>     [    0.831411] [drm] No driver support for vblank timestamp query.
>     [    0.837632] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
>     [    0.845214] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
>     [    0.852720] imx-drm display-subsystem: failed to bind display at di0 (ops imx_pd_ops): -19
>     [    0.860994] imx-drm display-subsystem: master bind failed: -19

I believe this should be fixed by

commit 799ee2970485dc206c3bf347d6e6827c04d5e4f9
Author: Philipp Zabel <p.zabel@pengutronix.de>
Date:   Mon Jun 12 17:54:29 2017 +0200

  drm/imx: parallel-display: Accept drm_of_find_panel_or_bridge failure


Nikita

  reply	other threads:[~2017-08-21 15:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 16:30 [PATCH] clk: imx51: propagate rate across ipu_di*_sel Lucas Stach
2017-08-18 16:30 ` Lucas Stach
2017-08-21 14:17 ` Fabio Estevam
2017-08-21 14:17   ` Fabio Estevam
2017-08-21 15:54   ` Wladimir J. van der Laan
2017-08-21 15:54     ` Wladimir J. van der Laan
2017-08-21 15:58     ` Nikita Yushchenko [this message]
2017-08-21 15:58       ` Nikita Yushchenko
2017-08-21 16:38       ` Wladimir J. van der Laan
2017-08-21 16:38         ` Wladimir J. van der Laan
2017-08-21 16:39         ` Fabio Estevam
2017-08-21 16:39           ` Fabio Estevam
2017-08-21 16:44           ` Wladimir J. van der Laan
2017-08-21 16:44             ` Wladimir J. van der Laan
2017-08-31 18:31 ` Stephen Boyd
2017-08-31 18:31   ` Stephen Boyd

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=4d5dbc0a-56b0-52a3-482d-2b3348c9c53b@cogentembedded.com \
    --to=nikita.yoush@cogentembedded.com \
    --cc=cphealy@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=imirkin@alum.mit.edu \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=laanwj@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=patchwork-lst@pengutronix.de \
    --cc=sboyd@codeaurora.org \
    --cc=shawnguo@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.