devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V2] ARM: dts: Add support for dra72-evm rev C (SR2.0)
Date: Thu, 14 Apr 2016 13:44:53 -0700	[thread overview]
Message-ID: <20160414204452.GO5995@atomide.com> (raw)
In-Reply-To: <1460655958-4639-1-git-send-email-nm@ti.com>

* Nishanth Menon <nm@ti.com> [160414 10:47]:
> DRA72-EVM now has an upgrade to Rev C with SR2.0 silicon. As part of
> this change, a few updates were factored in that were software
> incompatible with previous board in few areas:
> - We now use DP83867 ethernet phy instead of older DP838865 which fails
>   in certain use cases.
> - Two Ethernet ports now instead of the single one in rev B.
> - polarities changed for certain pcf gpios
> - Due to SoC phy current requirements, VDDA supplies are split between
>  ldo3 and ldo2 (ldo2 was previously unused). NOTE: DSS (VDDA_VIDEO) is
>  still supplied by ldo5, HDMI is now supplied by LDO2 instead of using
>  LDO3.
> 
> NOTE: It does not make much sense to spin off a new board compatible
> flag since there is no real benefit for the same.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Updates in v2:
>  - minor fixes + rebase to
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
>   omap-for-v4.7/dt   4cb53a2308a9 ARM: dts: omap3-beagle: Provide NAND ready pin

Thanks for updating this, applying into omap-for-v4.7/dt.

Tony

      reply	other threads:[~2016-04-14 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 17:45 [PATCH V2] ARM: dts: Add support for dra72-evm rev C (SR2.0) Nishanth Menon
2016-04-14 20:44 ` Tony Lindgren [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=20160414204452.GO5995@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.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).