linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Icenowy Zheng <icenowy@aosc.io>
To: linux-arm-kernel@lists.infradead.org,
	Maxime Ripard <maxime.ripard@bootlin.com>
Cc: devicetree@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [linux-sunxi] Re: [PATCH 1/2] ARM: sun8i: h3: enable HDMI output on Banana Pi M2 Zero
Date: Thu, 12 Jul 2018 15:09:55 +0800	[thread overview]
Message-ID: <A7CA2831-7117-415C-BC59-3FB4AE425598@aosc.io> (raw)
In-Reply-To: <20180712064601.m3bdd46wzac5fpgh@flea>



于 2018年7月12日 GMT+08:00 下午2:46:01, Maxime Ripard <maxime.ripard@bootlin.com> 写到:
>On Wed, Jul 11, 2018 at 11:15:50PM +0800, Icenowy Zheng wrote:
>> 
>> 
>> 于 2018年7月11日 GMT+08:00 下午11:05:32, Maxime Ripard
><maxime.ripard@bootlin.com> 写到:
>> >Hi,
>> >
>> >On Wed, Jul 11, 2018 at 09:22:32PM +0800, Icenowy Zheng wrote:
>> >> Banana Pi M2 Zero board has a miniHDMI port connected to the HDMI
>> >> controller of Allwinner H3 SoC.
>> >> 
>> >> Enable the HDMI output in Banana Pi M2 Zero device tree.
>> >> 
>> >> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
>> >> ---
>> >>  .../dts/sun8i-h2-plus-bananapi-m2-zero.dts    | 25
>> >+++++++++++++++++++
>> >>  1 file changed, 25 insertions(+)
>> >> 
>> >> diff --git a/arch/arm/boot/dts/sun8i-h2-plus-bananapi-m2-zero.dts
>> >b/arch/arm/boot/dts/sun8i-h2-plus-bananapi-m2-zero.dts
>> >> index 7d01f9322658..eb61dcf32797 100644
>> >> --- a/arch/arm/boot/dts/sun8i-h2-plus-bananapi-m2-zero.dts
>> >> +++ b/arch/arm/boot/dts/sun8i-h2-plus-bananapi-m2-zero.dts
>> >> @@ -26,6 +26,17 @@
>> >>  		stdout-path = "serial0:115200n8";
>> >>  	};
>> >>  
>> >> +	hdmi-connector {
>> >> +		compatible = "hdmi-connector";
>> >> +		type = "c";
>> >
>> >This is not one of the connector type declared in DRM, how is it
>> >exposed to the userspace?
>> 
>> So just use "A" here (because of single link)?
>
>If the connector type is C, it should be C, and DRM / driver adjusted
>to handle it.

Okay I won't change this property, if there's any further revisions.

For DRM driver, I think it can be an independent patchset.

>
>Maxime

  reply	other threads:[~2018-07-12  7:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 13:22 [PATCH 0/2] Misc function enhance to Banana Pi M2 Zero board Icenowy Zheng
2018-07-11 13:22 ` [PATCH 1/2] ARM: sun8i: h3: enable HDMI output on Banana Pi M2 Zero Icenowy Zheng
2018-07-11 15:05   ` Maxime Ripard
2018-07-11 15:14     ` [linux-sunxi] " Jernej Škrabec
2018-07-11 15:19       ` Icenowy Zheng
2018-07-11 15:15     ` Icenowy Zheng
2018-07-12  6:46       ` Maxime Ripard
2018-07-12  7:09         ` Icenowy Zheng [this message]
2018-07-12 14:53           ` Maxime Ripard
2018-07-13  2:28             ` Icenowy Zheng
2018-07-13  7:45               ` Maxime Ripard
2018-07-18 22:13   ` [linux-sunxi] " Julian Calaby

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=A7CA2831-7117-415C-BC59-3FB4AE425598@aosc.io \
    --to=icenowy@aosc.io \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=wens@csie.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).