All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/4] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC
Date: Thu, 29 Jan 2015 19:24:44 -0600	[thread overview]
Message-ID: <20150130012444.GB19864@home.buserror.net> (raw)
In-Reply-To: <1422517947-28722-1-git-send-email-Shengzhou.Liu@freescale.com>

On Thu, Jan 29, 2015 at 03:52:24PM +0800, Shengzhou Liu wrote:
> +/include/ "qoriq-i2c-0.dtsi"
> +/include/ "qoriq-i2c-1.dtsi"

t1023 has only three i2c controllers -- where do you disable the fourth? 

> +/include/ "t1023si-post.dtsi"
> +
> +/ {
> +	aliases {
> +		vga = &display;
> +		display = &display;
> +	};
> +};
> +
> +&soc {
> +	display:display@180000 {
> +		compatible = "fsl,t1024-diu", "fsl,diu";
> +		reg = <0x180000 1000>;
> +		interrupts = <74 2 0 0>;
> +	};
> +};

There are other differences between t1023 an t1024.  Where do you
describe t1024's QE?  Where do you describe the DDR and IFC differences? 
Ccan they be detected at runtime?  t1024 supports deep sleep, but t1023
doesn't -- yet you label both chips as having t1024 rcpm.

-Scott

      parent reply	other threads:[~2015-01-30  1:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  7:52 [PATCH 1/4] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC Shengzhou Liu
2015-01-29  7:52 ` [PATCH 2/4] powerpc/fsl-booke: Add T1024 QDS board support Shengzhou Liu
2015-01-29  7:52 ` [PATCH 3/4] powerpc/fsl-booke: Add T1024RDB " Shengzhou Liu
2015-01-29  7:52 ` [PATCH 4/4] powerpc/fsl-booke: Add T1023 RDB " Shengzhou Liu
2015-01-30  1:19 ` [1/4] powerpc/fsl-booke: Add device tree support for T1024/T1023 SoC Scott Wood
2015-03-30 11:08   ` Shengzhou.Liu
2015-03-30 23:00     ` Scott Wood
2015-03-31  3:32       ` Shengzhou.Liu
2015-03-31  3:37         ` Scott Wood
2015-01-30  1:24 ` Scott Wood [this message]

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=20150130012444.GB19864@home.buserror.net \
    --to=scottwood@freescale.com \
    --cc=Shengzhou.Liu@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.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 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.