From: laanwj@gmail•com (Wladimir J. van der Laan)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] clk: imx51: propagate rate across ipu_di*_sel
Date: Mon, 21 Aug 2017 17:54:12 +0200 [thread overview]
Message-ID: <20170821155412.GA24652@amethyst.visucore.com> (raw)
In-Reply-To: <CAOMZO5BoZNQrmDMXE0CDxLS-v7xVu4z87Ezdma1X1QCV56rPtQ@mail.gmail.com>
Hello Fabio,
On Mon, Aug 21, 2017 at 11:17:01AM -0300, Fabio Estevam wrote:
> On Fri, Aug 18, 2017 at 1:30 PM, Lucas Stach <l.stach@pengutronix•de> wrote:
> Wladimir,
>
> Could you please test it and see if it fixes the DVI output issue you
> reported earlier?
> https://lists.freedesktop.org/archives/dri-devel/2017-April/138155.html
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
Will try to debug this later.
Regards,
Wladimir
next prev parent reply other threads:[~2017-08-21 15:54 UTC|newest]
Thread overview: 8+ 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-21 14:17 ` Fabio Estevam
2017-08-21 15:54 ` Wladimir J. van der Laan [this message]
2017-08-21 15:58 ` Nikita Yushchenko
2017-08-21 16:38 ` Wladimir J. van der Laan
2017-08-21 16:39 ` Fabio Estevam
2017-08-21 16:44 ` Wladimir J. van der Laan
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=20170821155412.GA24652@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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