From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] staging: imx-drm-core: skip components whose parent device is disabled
Date: Fri, 18 Apr 2014 21:42:49 +0100 [thread overview]
Message-ID: <20140418204249.GG24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1397440946-2303-1-git-send-email-shawn.guo@freescale.com>
On Mon, Apr 14, 2014 at 10:02:26AM +0800, Shawn Guo wrote:
> In a board setup which disables LDB device node completely by changing
> status to 'disabled', and only enables HDMI device, we're running into
> the problem that imx-drm master never succeeds in binding, and hence
> HDMI does not come up either.
>
> &ldb {
> status = "disabled";
>
> lvds-channel at 1 {
> ...
> status = "okay";
> };
> };
>
> The imx-drm-core should really skip the LVDS channels no matter what
> lvds-channel's status is, if LDB device is disabled. Let's consider
> such setup a misconfiguration, give a warning in there and not add the
> component.
>
> Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
> ---
> Changes since v1:
> * Put a warning on such misconfiguration
Thanks Shawn, I've added it to my queue for Greg.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-18 20:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 2:02 [PATCH v2] staging: imx-drm-core: skip components whose parent device is disabled Shawn Guo
2014-04-14 8:01 ` Philipp Zabel
2014-04-18 20:42 ` Russell King - ARM Linux [this message]
2014-04-19 5:53 ` Shawn Guo
2014-04-19 8:42 ` Russell King - ARM Linux
2014-04-19 11:00 ` Shawn Guo
2014-04-21 14:22 ` Olof Johansson
2014-04-21 23:31 ` Shawn Guo
2014-04-22 20:49 ` Arnd Bergmann
2014-04-22 21:55 ` Russell King - ARM Linux
2014-04-23 7:44 ` Shawn Guo
2014-04-23 9:00 ` Russell King - ARM Linux
2014-04-24 21:36 ` Arnd Bergmann
2014-04-26 10:20 ` Russell King - ARM Linux
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=20140418204249.GG24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).