linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: Add support for dra72-evm rev C (ES2.0)
Date: Wed, 13 Apr 2016 16:54:14 -0500	[thread overview]
Message-ID: <570EC006.7050900@ti.com> (raw)
In-Reply-To: <20160412211322.GE5995@atomide.com>

On 04/12/2016 04:13 PM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [160324 15:53]:
>> DRA72-EVM now has an upgrade to Rev C with ES2.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 usecases.
>> - 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
>>  ldo5 and ldo2 (ldo2 was previously unused). NOTE: DSS (VDDA_VIDEO) is
>>  still supplied by ldo5.
>>
>> NOTE: It does not make much sense to spin off a new board compatible
>> flag since there is no real benefit for the same.
> 
> I guess that can always be added later on if needed.
> 
> Can you please repost this against current omap-for-v4.7/dt as it
> no longer applies?

Will do. thanks.
-- 
Regards,
Nishanth Menon

  reply	other threads:[~2016-04-13 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 22:52 [PATCH 0/2] ARM: DRA72: Add support for rev C evm Nishanth Menon
2016-03-24 22:52 ` [PATCH 1/2] ARM: dts: Add support for dra72-evm rev C (ES2.0) Nishanth Menon
2016-04-12 21:13   ` Tony Lindgren
2016-04-13 21:54     ` Nishanth Menon [this message]
2016-03-24 22:52 ` [PATCH 2/2] ARM: omap2plus_defconfig: Enable DP83867 support Nishanth Menon
2016-04-13 21:42   ` Tony Lindgren

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=570EC006.7050900@ti.com \
    --to=nm@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).