From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>, ulf.hansson@linaro.org
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: meson-sm1-sei610: add HDMI display support
Date: Thu, 22 Aug 2019 10:23:31 +0200 [thread overview]
Message-ID: <09a5372b-3ff1-b6fc-9a06-d8f9c235e763@baylibre.com> (raw)
In-Reply-To: <7ho90i5c41.fsf@baylibre.com>
On 22/08/2019 01:31, Kevin Hilman wrote:
> Neil Armstrong <narmstrong@baylibre.com> writes:
>
>> Update compatible of the pwc-vpu node and add the HDMI support nodes
>> for the Amlogic SM1 Based SEI610 Board.
>
> I think this changelog is out of date. It's not doing anything with the
> VPU pwrc node.
Exact, thanks for pointing it
>
> Kevin
>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>> .../boot/dts/amlogic/meson-sm1-sei610.dts | 23 +++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts b/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> index 12dab0ba2f26..66bd3bfbaf91 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> +++ b/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> @@ -51,6 +51,17 @@
>> };
>> };
>>
>> + hdmi-connector {
>> + compatible = "hdmi-connector";
>> + type = "a";
>> +
>> + port {
>> + hdmi_connector_in: endpoint {
>> + remote-endpoint = <&hdmi_tx_tmds_out>;
>> + };
>> + };
>> + };
>> +
>> leds {
>> compatible = "gpio-leds";
>>
>> @@ -177,6 +188,18 @@
>> phy-mode = "rmii";
>> };
>>
>> +&hdmi_tx {
>> + status = "okay";
>> + pinctrl-0 = <&hdmitx_hpd_pins>, <&hdmitx_ddc_pins>;
>> + pinctrl-names = "default";
>> +};
>> +
>> +&hdmi_tx_tmds_port {
>> + hdmi_tx_tmds_out: endpoint {
>> + remote-endpoint = <&hdmi_connector_in>;
>> + };
>> +};
>> +
>> &i2c3 {
>> status = "okay";
>> pinctrl-0 = <&i2c3_sda_a_pins>, <&i2c3_sck_a_pins>;
>> --
>> 2.22.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-22 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 11:41 [PATCH 0/5] arm64: meson: add support for SM1 Power Domains Neil Armstrong
2019-08-21 11:41 ` [PATCH 1/5] dt-bindings: power: add Amlogic Everything-Else power domains bindings Neil Armstrong
2019-08-21 13:46 ` Rob Herring
2019-08-21 11:41 ` [PATCH 2/5] soc: amlogic: Add support for Everything-Else power domains controller Neil Armstrong
2019-08-21 23:16 ` Kevin Hilman
2019-08-22 8:35 ` Neil Armstrong
2019-08-22 20:32 ` Kevin Hilman
2019-08-23 8:22 ` Neil Armstrong
2019-08-23 15:06 ` Kevin Hilman
2019-08-21 11:41 ` [PATCH 3/5] arm64: meson-g12: add Everything-Else power domain controller Neil Armstrong
2019-08-21 11:41 ` [PATCH 4/5] arm64: dts: meson-sm1-sei610: add HDMI display support Neil Armstrong
2019-08-21 23:31 ` Kevin Hilman
2019-08-22 8:23 ` Neil Armstrong [this message]
2019-08-21 11:41 ` [PATCH 5/5] arm64: dts: meson-sm1-sei610: add USB support Neil Armstrong
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=09a5372b-3ff1-b6fc-9a06-d8f9c235e763@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ulf.hansson@linaro.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).