linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Haijun Zhang <Haijun.Zhang@freescale.com>
Cc: Fleming Andrew-AFLEMING <AFLEMING@freescale.com>,
	linuxppc-dev@lists.ozlabs.org,
	Haijun Zhang <Haijun.Zhang@freescale.com>
Subject: Re: [PATCH] DTS: Add compatible list for eSDHC
Date: Mon, 1 Jul 2013 19:04:35 -0500	[thread overview]
Message-ID: <1372723475.8183.100@snotra> (raw)
In-Reply-To: <1372656110-13876-1-git-send-email-Haijun.Zhang@freescale.com> (from Haijun.Zhang@freescale.com on Mon Jul  1 00:21:50 2013)

On 07/01/2013 12:21:50 AM, Haijun Zhang wrote:
> Add compatible of esdhc for below board:
> p2041   p3041   p4080   p5020   p5040
>=20
> Signed-off-by: Haijun Zhang <Haijun.Zhang@freescale.com>
> CC: Scott Wood <scottwood@freescale.com>
> CC: Fleming Andrew-AFLEMING <AFLEMING@freescale.com>
> ---
>  arch/powerpc/boot/dts/fsl/p2041si-post.dtsi | 1 +
>  arch/powerpc/boot/dts/fsl/p3041si-post.dtsi | 1 +
>  arch/powerpc/boot/dts/fsl/p4080si-post.dtsi | 1 +
>  arch/powerpc/boot/dts/fsl/p5020si-post.dtsi | 1 +
>  arch/powerpc/boot/dts/fsl/p5040si-post.dtsi | 1 +
>  5 files changed, 5 insertions(+)

Is there something specific that depends on this, or are you just =20
trying to conform to other examples?

I don't think we need the SoC name here, given that eSDHC has a version =20
register that you can read (and an SVR in the unlikely case that that =20
isn't adequate).  If you did end up relying on this device tree change, =20
you'd be broken if an older device trees is used.

-Scott=

  reply	other threads:[~2013-07-02  0:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  5:21 [PATCH] DTS: Add compatible list for eSDHC Haijun Zhang
2013-07-02  0:04 ` Scott Wood [this message]
2013-07-02  8:00   ` Zhang Haijun-B42677
2013-07-02 18:54     ` Scott Wood
2013-07-03  2:14       ` Zhang Haijun-B42677

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=1372723475.8183.100@snotra \
    --to=scottwood@freescale.com \
    --cc=AFLEMING@freescale.com \
    --cc=Haijun.Zhang@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 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).