devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sathya Prakash M R <sathyap@ti.com>
Cc: tony@atomide.com, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, pawel.moll@arm.com, paul@pwsan.com
Subject: Re: [PATCH 2/2] ARM: DTS: AM43x: Add sii9022 dt information
Date: Tue, 18 Mar 2014 12:31:30 +0200	[thread overview]
Message-ID: <53282082.1000208@ti.com> (raw)
In-Reply-To: <1395137278-5065-3-git-send-email-sathyap@ti.com>

[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]

On 18/03/14 12:07, Sathya Prakash M R wrote:
> AM43x-epos and AM437x-gp device use external sii9022
> DPI to HDMI encoder.
> Sii9022 use i2c for communication.
> Sii9022 dt entries are added to corresponding dts.
> 
> Signed-off-by: Sathya prakash M R <sathyap@ti.com>
> ---
>  arch/arm/boot/dts/am437x-gp-evm.dts  |   58 +++++++++++++++++++++++++++++++--
>  arch/arm/boot/dts/am43x-epos-evm.dts |   59 ++++++++++++++++++++++++++++++++--
>  2 files changed, 111 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
> index a178e8d..c4225b1 100644
> --- a/arch/arm/boot/dts/am437x-gp-evm.dts
> +++ b/arch/arm/boot/dts/am437x-gp-evm.dts
> @@ -51,6 +51,41 @@
>  			remote-endpoint = <&dpi_out>;
>  		};
>  	};
> +
> +	sii9022: encoder@0 {
> +		compatible = "sii,sii9022";

See Documentation/devicetree/bindings/vendor-prefixes.txt

The vendor prefix is "sil".

> +		reset-gpio = <&gpio5 8 GPIO_ACTIVE_LOW>;/* 'SelLCDorHDMI' Gpio, LOW to select HDMI */
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			port@0 {
> +				reg = <0>;
> +
> +				sii9022_in: endpoint@0 {
> +					remote-endpoint = <&dpi_out>;
> +				};
> +			};
> +
> +			port@1 {
> +				reg = <1>;
> +
> +				sii9022_out: endpoint@0 {
> +					remote-endpoint = <&hdmi_connector_in>;
> +				};
> +			};
> +		};
> +	};
> +
> +	hdmi0: connector@0 {
> +		compatible = "hdmi-connector";
> +		label = "hdmi";
> +
> +		hdmi_connector_in: endpoint {
> +			remote-endpoint = <&sil9022_out>;
> +		};
> +	};
>  };
>  
>  &am43xx_pinmux {
> @@ -119,6 +154,9 @@
>          status = "okay";
>          pinctrl-names = "default";
>          pinctrl-0 = <&i2c1_pins>;
> +	&sii9022 {
> +		reg = <0x3b>;
> +	}

This looks very very odd... The whole sii9022 node should be here.

>  };
>  
>  &epwmss0 {
> @@ -141,8 +179,22 @@
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&dss_pinctrl>;
>  
> -	dpi_out: endpoint@0 {
> -		remote-endpoint = <&lcd_in>;
> -		data-lines = <24>;
> +	ports {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		port@0 {
> +			reg = <0>;
> +			dpi_out: endpoint@0 {
> +				remote-endpoint = <&lcd_in>;
> +				data-lines = <24>;
> +			};
> +
> +			dpi_out:endpoint@1 {
> +				remote-endpoint = <&sii9022_in>;
> +				data-lines = <24>;
> +
> +			};

You add the same label, "dpi_out" to both endpoints. Does this even compile?

As there's just one port, you can leave out the 'ports' node.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-03-18 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 10:07 [RFC PATCH 0/2] Sil9022 DPI to HDMI Encoder Sathya Prakash M R
2014-03-18 10:07 ` [PATCH 1/2] OMAPDSS: Add Sil9022 DPI-HDMI Encoder Driver Sathya Prakash M R
2014-03-18 11:20   ` Tomi Valkeinen
2014-03-18 10:07 ` [PATCH 2/2] ARM: DTS: AM43x: Add sii9022 dt information Sathya Prakash M R
2014-03-18 10:31   ` Tomi Valkeinen [this message]
2014-03-18 10:57     ` Sathya Prakash
2014-03-18 11:03       ` Tomi Valkeinen
2014-03-18 10:56 ` [RFC PATCH 0/2] Sil9022 DPI to HDMI Encoder Mark Rutland

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=53282082.1000208@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=pawel.moll@arm.com \
    --cc=sathyap@ti.com \
    --cc=tony@atomide.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 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).