Re: [PATCH 2/4] ARM: dts: omap4-panda: Fix DVI EDID reads
From: Roger Quadros
Date: Tue Jun 18 2013 - 09:30:14 EST
On 06/18/2013 02:11 PM, Roger Quadros wrote:
> On Panda the +5V supply for DVI EDID is supplied by the
> same regulator that poweres the USB Hub. Currently, the
> DSS/DVI subsystem doesn't know how to manage this regulator
> and so DVI EDID reads will fail if USB Hub is not enabled.
> As a temporary fix we keep this regulator permanently enabled
> on boot. This fixes the DVI EDID read problem.
> CC: Tomi Valkeinen <tomi.valkeinen@xxxxxx>
> Signed-off-by: Roger Quadros <rogerq@xxxxxx>
> arch/arm/boot/dts/omap4-panda-common.dtsi | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
> diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi b/arch/arm/boot/dts/omap4-panda-common.dtsi
> index 7a21e8e..40df79e 100644
> --- a/arch/arm/boot/dts/omap4-panda-common.dtsi
> +++ b/arch/arm/boot/dts/omap4-panda-common.dtsi
> @@ -80,6 +80,11 @@
> gpio = <&gpio1 1 0>; /* gpio_1 */
> startup-delay-us = <70000>;
> + /*
> + * FIXME: Remove boot-on when DSS can handle this regulator
> + * for DVI EDID.
> + */
> + regulator-boot-on;
As pointed out by Tomi, the correct usage here is "regulator-always-on".
The reason I use "regulator-boot-on" is because the regulator framework doesn't
turn on the regulator. (maybe a bug in the regulator framework?)
"regulator-boot-on" is not sufficient as it doesn't prevent drivers from turning it
off. e.g. loading and unloading the USB host driver will turn of the regulator.
So it must be used along with "regulator-always-on"
I'll fix this in v2.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/