From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am57xx-beagle-x15: fix HDMI LS_OE GPIO
Date: Thu, 1 Sep 2016 09:09:33 -0500 [thread overview]
Message-ID: <b8647621-197c-97d5-8291-26c079e5eae8@ti.com> (raw)
In-Reply-To: <1472737901-26494-1-git-send-email-tomi.valkeinen@ti.com>
On 09/01/2016 08:51 AM, Tomi Valkeinen wrote:
> LS_OE GPIO was changed from gpio6_28 to gpio2_30 for the Rev B1 board,
> and the current .dts file has the old GPIO.
>
> Rev B1 is the earliest board supported, so we can just change the .dts.
>
> This fixes "omapdss error: HDMI I2C Master Error" which causes failure
> to read EDID from the monitor.
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> ---
> arch/arm/boot/dts/am57xx-beagle-x15.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> index c4d04c5293b9..07603d9e2da7 100644
> --- a/arch/arm/boot/dts/am57xx-beagle-x15.dts
> +++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> @@ -120,7 +120,7 @@
> pinctrl-0 = <&tpd12s015_pins>;
>
> gpios = <&gpio7 10 GPIO_ACTIVE_HIGH>, /* gpio7_10, CT CP HPD */
> - <&gpio6 28 GPIO_ACTIVE_HIGH>, /* gpio6_28, LS OE */
> + <&gpio2 30 GPIO_ACTIVE_HIGH>, /* gpio2_30, LS OE */
> <&gpio7 12 GPIO_ACTIVE_HIGH>; /* gpio7_12/sp1_cs2, HPD */
>
> ports {
>
I believe we have A2s being shipped as well. we dont want to break A2s
either -> I propose we refactor the dts to introduce revb1 X15.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2016-09-01 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 13:51 [PATCH] ARM: dts: am57xx-beagle-x15: fix HDMI LS_OE GPIO Tomi Valkeinen
2016-09-01 14:09 ` Nishanth Menon [this message]
2016-09-01 14:12 ` Robert Nelson
2016-09-01 14:14 ` Nishanth Menon
2016-09-01 14:57 ` Tomi Valkeinen
2016-09-01 14:57 ` Tony Lindgren
2016-09-01 15:00 ` Nishanth Menon
2017-11-14 0:27 ` Bill Traynor
2017-11-14 7:33 ` Tomi Valkeinen
2017-11-14 14:14 ` Bill Traynor
2017-11-14 16:07 ` Robert Nelson
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=b8647621-197c-97d5-8291-26c079e5eae8@ti.com \
--to=nm@ti.com \
--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