From: Tony Lindgren <tony@atomide.com>
To: Florian Vaussard <florian.vaussard@epfl.ch>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: duovero-parlor: Add HDMI output
Date: Tue, 20 May 2014 07:39:32 -0700 [thread overview]
Message-ID: <20140520143932.GA27830@atomide.com> (raw)
In-Reply-To: <1400595946-1294-1-git-send-email-florian.vaussard@epfl.ch>
* Florian Vaussard <florian.vaussard@epfl.ch> [140520 07:26]:
> @@ -77,6 +94,15 @@
> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_a24.gpio_48: amdix enabled */
> >;
> };
> +
> + dss_hdmi_pins: pinmux_dss_hdmi_pins {
> + pinctrl-single,pins = <
> + 0x58 (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_hpd.hdmi_hpd */
> + 0x5a (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_cec.hdmi_cec */
> + 0x5c (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_ddc_scl.hdmi_ddc_scl */
> + 0x5e (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_ddc_sda.hdmi_ddc_sda */
> + >;
> + };
> };
>
> &i2c2 {
This seems to apply with fuzz against omap-for-v3.16/dt-v2, but
should be updated against omap-for-v3.16/dt-v2 to use OMAP4_IOPAD
as omap4-duovero-parlor.dts is now using it. That makes checking
the muxing easier against the TRM. See commit 5efa994b0d49 for
the script Joachim used.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: duovero-parlor: Add HDMI output
Date: Tue, 20 May 2014 07:39:32 -0700 [thread overview]
Message-ID: <20140520143932.GA27830@atomide.com> (raw)
In-Reply-To: <1400595946-1294-1-git-send-email-florian.vaussard@epfl.ch>
* Florian Vaussard <florian.vaussard@epfl.ch> [140520 07:26]:
> @@ -77,6 +94,15 @@
> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_a24.gpio_48: amdix enabled */
> >;
> };
> +
> + dss_hdmi_pins: pinmux_dss_hdmi_pins {
> + pinctrl-single,pins = <
> + 0x58 (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_hpd.hdmi_hpd */
> + 0x5a (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_cec.hdmi_cec */
> + 0x5c (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_ddc_scl.hdmi_ddc_scl */
> + 0x5e (PIN_INPUT_PULLUP | MUX_MODE0) /* hdmi_ddc_sda.hdmi_ddc_sda */
> + >;
> + };
> };
>
> &i2c2 {
This seems to apply with fuzz against omap-for-v3.16/dt-v2, but
should be updated against omap-for-v3.16/dt-v2 to use OMAP4_IOPAD
as omap4-duovero-parlor.dts is now using it. That makes checking
the muxing easier against the TRM. See commit 5efa994b0d49 for
the script Joachim used.
Regards,
Tony
next prev parent reply other threads:[~2014-05-20 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 14:25 [PATCH] ARM: dts: duovero-parlor: Add HDMI output Florian Vaussard
2014-05-20 14:25 ` Florian Vaussard
2014-05-20 14:39 ` Tony Lindgren [this message]
2014-05-20 14:39 ` Tony Lindgren
2014-05-21 6:41 ` Florian Vaussard
2014-05-21 6:41 ` Florian Vaussard
2014-05-20 18:09 ` Joachim Eastwood
2014-05-20 18:09 ` Joachim Eastwood
2014-05-21 6:43 ` Florian Vaussard
2014-05-21 6:43 ` Florian Vaussard
2014-05-21 8:14 ` Florian Vaussard
2014-05-21 8:14 ` Florian Vaussard
2014-05-21 8:26 ` Tomi Valkeinen
2014-05-21 8:26 ` Tomi Valkeinen
2014-05-21 9:04 ` Florian Vaussard
2014-05-21 9:04 ` Florian Vaussard
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=20140520143932.GA27830@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@epfl.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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.