From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: I.MX6 HDMI support in v4.2
Date: Tue, 08 Sep 2015 12:56:18 +0200 [thread overview]
Message-ID: <1441709778.13536.8.camel@pengutronix.de> (raw)
In-Reply-To: <m337yp5gvv.fsf@t19.piap.pl>
Am Dienstag, den 08.09.2015, 12:45 +0200 schrieb Krzysztof Ha?asa:
> Trying to make some progress... I was missing the etnaviv DRM kernel
> driver. Now I have both IMX and etnaviv drivers, Linux v4.0-stable:
>
> git://git.pengutronix.de/git/lst/linux.git (etnaviv DRM driver)
> PLL5 DTS patch (enables HDMI with LVDS driver loaded):
>
> --- a/arch/arm/boot/dts/imx6q-gw54xx.dts
> +++ b/arch/arm/boot/dts/imx6q-gw54xx.dts
> @@ -21,3 +21,11 @@
> &sata {
> status = "okay";
> };
> +
> +&clks {
> + assigned-clocks = <&clks IMX6QDL_CLK_LDB_DI0_SEL>,
> + <&clks IMX6QDL_CLK_LDB_DI1_SEL>;
> + assigned-clock-parents = <&clks IMX6QDL_CLK_PLL3_USB_OTG>,
> + <&clks IMX6QDL_CLK_PLL3_USB_OTG>;
> +};
> +
>
> also had to apply:
>
> --- a/drivers/staging/etnaviv/Makefile
> +++ b/drivers/staging/etnaviv/Makefile
> @@ -11,7 +11,6 @@ etnaviv-y := \
> etnaviv_gem_submit.o \
> etnaviv_gpu.o \
> etnaviv_iommu.o \
> - etnaviv_iommu_v2.o \
> etnaviv_mmu.o \
> etnaviv_buffer.o
>
>
> X.org etc.:
> git://github.com/laanwj/etna_viv.git
> git://ftp.arm.linux.org.uk/~rmk/libdrm-armada.git/
> git://ftp.arm.linux.org.uk/~rmk/xf86-video-armada.git unstable-devel
> (I can't use master branch of xf86-video-armada.git because it doesn't
> support etnaviv - does it?)
>
> X log (relevant(?) stuff only):
>
> [ 18919.848] (II) armada(0): hardware: imx-drm
> [ 18919.923] (--) armada(0): Vivante GC320 GPU revision 5007 (etnaviv) 2d PE2.0
> [ 18919.925] (II) armada(0): [DRI2] Setup complete
> [ 18919.925] (II) armada(0): [DRI2] DRI driver: etnadrm
> [ 18919.925] (II) armada(0): direct rendering: DRI2 enabled
> [ 18919.925] (II) armada(0): RandR 1.2 enabled, ignore the following RandR disabled message.
> [ 18919.927] (==) armada(0): DPMS enabled
> [ 18919.927] (==) armada(0): hotplug detection enabled
> [ 18919.928] (II) armada(0): etnaviv: Xv: using YUY2 tiled format intermediate YUV target
> [ 18919.971] (EE) AIGLX error: dlopen of /lib/dri/etnadrm_dri.so failed (I don't have this yet)
> [ 18920.072] (II) armada(0): etnaviv: A8 target not supported
>
> If I try to use pengutronix/etnaviv-4.1-wip branch (etnaviv DRM - for
> v4.2), dmesg contains a lot of:
> [drm:etnaviv_ioctl_gem_submit [etnaviv]] *ERROR* cmdstream bo has flag ETNA_BO_CMDSTREAM not set
> and it doesn't work. I assume I shouldn't use it yet?
>
You need changes to the X.Org driver for that to work. I'm currently
working on a new version of the etnaviv-drm driver which will break the
kernel userspace interface another time - hopefully for the last time
now.
I'm almost done and will publish patches for both the kernel and the
X.Org driver today.
> Changing to pengutronix/etnaviv-for-upstream, it works - sort of.
>
> I now have two Xvideo adapters:
> Adaptor: 0
> Name: Marvell Armada Overlay Video
> Port: 88
> (which unfortunately doesn't work, the window is black, the XV
> attributes are set to minimums and I can't set them).
>
> Is it expected?
>
This is expected, it's the overlay adapter which doesn't really work
with imx-drm yet.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-09-08 10:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 10:55 I.MX6 HDMI support in v4.2 Krzysztof Hałasa
2015-09-07 11:25 ` Russell King - ARM Linux
2015-09-07 14:04 ` Krzysztof Hałasa
2015-09-08 9:16 ` Russell King - ARM Linux
2015-09-08 11:01 ` Krzysztof Hałasa
2015-09-08 12:57 ` Russell King - ARM Linux
2015-09-08 14:59 ` Krzysztof Hałasa
2015-09-10 10:25 ` Krzysztof Hałasa
2015-09-10 10:49 ` Russell King - ARM Linux
2015-09-10 11:29 ` Krzysztof Hałasa
2015-09-17 7:21 ` Philipp Zabel
2015-09-17 8:38 ` Krzysztof Hałasa
2015-09-17 9:23 ` Russell King - ARM Linux
2015-09-08 10:45 ` Krzysztof Hałasa
2015-09-08 10:56 ` Lucas Stach [this message]
2015-09-08 11:01 ` Russell King - ARM Linux
2015-09-08 11:07 ` Lucas Stach
2015-09-08 11:29 ` Russell King - ARM Linux
2015-09-08 12:43 ` Lucas Stach
2015-09-08 13:40 ` Russell King - ARM Linux
2015-09-08 14:17 ` Robert Nelson
2015-09-08 14:45 ` Krzysztof Hałasa
2015-09-08 14:48 ` Lucas Stach
2015-09-08 15:55 ` Russell King - ARM Linux
2015-09-08 17:07 ` Jon Nettleton
2015-09-08 11:06 ` Krzysztof Hałasa
2015-09-14 8:39 ` Krzysztof Hałasa
2015-09-15 8:24 ` Krzysztof Hałasa
2015-09-15 10:12 ` Russell King - ARM Linux
2015-09-15 11:01 ` Krzysztof Hałasa
2015-09-15 14:29 ` Russell King - ARM Linux
2015-09-15 16:53 ` Krzysztof Hałasa
2015-09-15 15:53 ` Lucas Stach
2015-09-15 16:36 ` Russell King - ARM Linux
2015-09-15 16:53 ` Lucas Stach
2015-09-15 17:04 ` Russell King - ARM Linux
2015-09-15 19:01 ` Lucas Stach
2015-09-28 14:48 ` xf86-video-armada + etnaviv (Was: Re: I.MX6 HDMI support in v4.2) Lucas Stach
2015-09-28 15:24 ` Russell King - ARM Linux
2015-09-28 15:40 ` Lucas Stach
2015-09-28 16:50 ` Russell King - ARM Linux
2015-09-29 8:28 ` Lucas Stach
2015-09-29 8:41 ` Russell King - ARM Linux
2015-09-29 9:01 ` Lucas Stach
2015-09-15 16:57 ` I.MX6 HDMI support in v4.2 Krzysztof Hałasa
2015-09-16 7:57 ` Krzysztof Hałasa
2015-09-16 15:52 ` Lucas Stach
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=1441709778.13536.8.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).