All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	kernel@pengutronix.de,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	dri-devel@lists.freedesktop.org,
	Grant Likely <grant.likely@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 00/11] imx-drm dt bindings
Date: Mon, 7 Apr 2014 10:09:27 +0100	[thread overview]
Message-ID: <20140407090927.GW7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140407042334.GA28025@dragon>

On Mon, Apr 07, 2014 at 12:23:37PM +0800, Shawn Guo wrote:
> And I see another HDMI regression with my testing on mainline kernel.  I
> can have my HDMI work at 1920x1080 with v3.14 kernel, but it can only
> probes 1024x768 with the mainline today.

Works for me here.

> [    20.606] (II) LoadModule: "modesetting"
> [    20.607] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [    20.609] (II) Module modesetting: vendor="X.Org Foundation"
> [    20.609] 	compiled for 1.12.1.902, module version = 0.3.0
> [    20.610] 	Module class: X.Org Video Driver
> [    20.610] 	ABI class: X.Org Video Driver, version 12.0
> [    20.610] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [    20.610] (++) using VT number 7
> 
> [    20.624] (WW) Falling back to old probe method for modesetting
> [    20.624] (II) modesetting(0): using default device
> [    20.627] (II) modesetting(0): Creating default Display subsection in Screen section
> 	"Default Screen Section" for depth/fbbpp 24/32
> [    20.627] (==) modesetting(0): Depth 24, (==) framebuffer bpp 32
> [    20.628] (==) modesetting(0): RGB weight 888
> [    20.628] (==) modesetting(0): Default visual is TrueColor
> [    20.628] (II) modesetting(0): ShadowFB: preferred NO, enabled NO
> [    20.628] (II) modesetting(0): Output HDMI-0 has no monitor section
> [    20.629] (II) modesetting(0): EDID for output HDMI-0
> [    20.629] (II) modesetting(0): Printing probed modes for output HDMI-0

So no EDID.  Did you update the "ddc" property to "ddc-i2c-bus" ?

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 00/11] imx-drm dt bindings
Date: Mon, 7 Apr 2014 10:09:27 +0100	[thread overview]
Message-ID: <20140407090927.GW7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140407042334.GA28025@dragon>

On Mon, Apr 07, 2014 at 12:23:37PM +0800, Shawn Guo wrote:
> And I see another HDMI regression with my testing on mainline kernel.  I
> can have my HDMI work at 1920x1080 with v3.14 kernel, but it can only
> probes 1024x768 with the mainline today.

Works for me here.

> [    20.606] (II) LoadModule: "modesetting"
> [    20.607] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [    20.609] (II) Module modesetting: vendor="X.Org Foundation"
> [    20.609] 	compiled for 1.12.1.902, module version = 0.3.0
> [    20.610] 	Module class: X.Org Video Driver
> [    20.610] 	ABI class: X.Org Video Driver, version 12.0
> [    20.610] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [    20.610] (++) using VT number 7
> 
> [    20.624] (WW) Falling back to old probe method for modesetting
> [    20.624] (II) modesetting(0): using default device
> [    20.627] (II) modesetting(0): Creating default Display subsection in Screen section
> 	"Default Screen Section" for depth/fbbpp 24/32
> [    20.627] (==) modesetting(0): Depth 24, (==) framebuffer bpp 32
> [    20.628] (==) modesetting(0): RGB weight 888
> [    20.628] (==) modesetting(0): Default visual is TrueColor
> [    20.628] (II) modesetting(0): ShadowFB: preferred NO, enabled NO
> [    20.628] (II) modesetting(0): Output HDMI-0 has no monitor section
> [    20.629] (II) modesetting(0): EDID for output HDMI-0
> [    20.629] (II) modesetting(0): Printing probed modes for output HDMI-0

So no EDID.  Did you update the "ddc" property to "ddc-i2c-bus" ?

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-04-07  9:09 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  9:20 [PATCH v5 00/11] imx-drm dt bindings Philipp Zabel
2014-03-05  9:20 ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 01/11] staging: imx-drm-core: Use OF graph to find components and connections between encoder and crtcs Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05 10:05   ` Russell King - ARM Linux
2014-03-05 10:05     ` Russell King - ARM Linux
2014-03-05 14:25     ` Philipp Zabel
2014-03-05 14:25       ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 02/11] staging: imx-drm-core: use of_graph_parse_endpoint Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 03/11] staging: imx-drm: Document updated imx-drm device tree bindings Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 04/11] staging: imx-drm: Document imx-hdmi " Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 05/11] imx-drm: imx-hdmi: Fix DDC I2C bus property Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 07/11] ARM: dts: imx53-mba53: Fix TVE " Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:20 ` [PATCH v5 08/11] ARM: dts: imx51: Add IPU ports and endpoints, move imx-drm node to dtsi Philipp Zabel
2014-03-05  9:20   ` Philipp Zabel
2014-03-05  9:21 ` [PATCH v5 10/11] ARM: dts: imx6qdl: Add IPU DI " Philipp Zabel
2014-03-05  9:21   ` Philipp Zabel
2014-03-05  9:21 ` [PATCH v5 11/11] staging: imx-drm: Update TODO Philipp Zabel
2014-03-05  9:21   ` Philipp Zabel
2014-03-07 17:56 ` [PATCH v5 00/11] imx-drm dt bindings Russell King - ARM Linux
2014-03-07 17:56   ` Russell King - ARM Linux
2014-03-07 18:28   ` Greg Kroah-Hartman
2014-03-07 18:28     ` Greg Kroah-Hartman
2014-03-07 18:57     ` Philipp Zabel
2014-03-07 18:57       ` Philipp Zabel
2014-03-07 19:17       ` Russell King - ARM Linux
2014-03-07 19:17         ` Russell King - ARM Linux
     [not found] ` <1394011262-16849-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-05  9:20   ` [PATCH v5 06/11] imx-drm: imx-tve: Fix DDC I2C bus property Philipp Zabel
2014-03-05  9:20     ` Philipp Zabel
2014-03-06 13:03     ` Russell King - ARM Linux
2014-03-06 13:03       ` Russell King - ARM Linux
2014-03-06 13:32       ` Philipp Zabel
2014-03-06 13:32         ` Philipp Zabel
2014-03-05  9:21   ` [PATCH v5 09/11] ARM: dts: imx53: Add IPU DI ports and endpoints, move imx-drm node to dtsi Philipp Zabel
2014-03-05  9:21     ` Philipp Zabel
2014-03-11  3:46   ` [PATCH v5 00/11] imx-drm dt bindings Shawn Guo
2014-03-11  3:46     ` Shawn Guo
2014-03-11 11:42     ` Philipp Zabel
2014-03-11 11:42       ` Philipp Zabel
2014-03-11 13:27       ` Shawn Guo
2014-03-11 13:27         ` Shawn Guo
2014-03-11 13:34         ` Lucas Stach
2014-03-11 13:34           ` Lucas Stach
     [not found]           ` <1394544878.4339.7.camel-WzVe3FnzCwFR6QfukMTsflXZhhPuCNm+@public.gmane.org>
2014-03-11 14:14             ` Shawn Guo
2014-03-11 14:14               ` Shawn Guo
     [not found]     ` <20140311034607.GA26502-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2014-04-07  4:23       ` Shawn Guo
2014-04-07  4:23         ` Shawn Guo
2014-04-07  9:09         ` Russell King - ARM Linux [this message]
2014-04-07  9:09           ` Russell King - ARM Linux
2014-04-07 13:40           ` Shawn Guo
2014-04-07 13:40             ` Shawn Guo
2014-04-07 10:05         ` Philipp Zabel
2014-04-07 10:05           ` Philipp Zabel
2014-04-07 12:34           ` Philipp Zabel
2014-04-07 12:34             ` Philipp Zabel
2014-04-07 13:43           ` Shawn Guo
2014-04-07 13:43             ` Shawn Guo

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=20140407090927.GW7528@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=shawn.guo@freescale.com \
    /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.