devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: balbi@ti.com, Nishanth Menon <nm@ti.com>
Cc: bcousson@baylibre.com, tony@atomide.com,
	devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add DRA7xx CPSW Ethernet support in Device Tree
Date: Thu, 6 Nov 2014 22:33:42 +0530	[thread overview]
Message-ID: <545BA9EE.1040905@ti.com> (raw)
In-Reply-To: <20141103162722.GN27425@saruman>

Tony

On Monday 03 November 2014 09:57 PM, Felipe Balbi wrote:
> On Tue, Oct 21, 2014 at 12:22:23PM -0500, Nishanth Menon wrote:
>> On 15:37-20141021, Mugunthan V N wrote:
>>> Nishanth
>>>
>>> On Tuesday 21 October 2014 03:30 PM, Mugunthan V N wrote:
>>>> Adding device tree entry for CPSW to make it work in Dual EMAC mode.
>>>> These patches were tested with DRA7 hwmod patches on top of linux-next.
>>>> Patches are tested on top of Nishanth's PM tree for v3.17 [1] and pushed
>>>> my tree to [2].
>>>>
>>>> Did a boot test with CPSW and ping test with suspend/resume, the boot logs
>>>> on DRA7xx EVM are posted at [3]
>>>>
>>>> [1] git://github.com/nmenon/linux-2.6-playground.git testing/v3.17/cpu-idle-suspend-dra7-omap5-framework
>>>> [2] git://git.ti.com/~mugunthanvnm/ti-linux-kernel/linux.git v3.17/dra7-evm-cpsw-v3
>>>> [3] http://pastebin.ubuntu.com/8613072/
>>>>
>>>> Changes from v2:
>>>> * Changed pinctrl comments to hold mode0-name.mode-selected-name
>>>> * Changes slave numbers in the pinctrl comments
>>>> * Added cpsw and cpts clocks
>>>>
>>>
>>> I have not added support for dra72x-evm as it has only slave no 2 pinned
>>> out and having issues with bringing up the interface, need some more
>>> time to submit the patch, in the mean time I have submitted dra7-evm
>>> support only so that people can use dra7-evm on linux-next.
>>
>> Quickly tested as well:
>> http://slexy.org/raw/s2vISJxYrR
>>
>> Please feel free to add:
>> Tested-by: Nishanth Menon <nm@ti.com>
>> Acked-by: Nishanth Menon <nm@ti.com>
> 
> I've used these patches with X15 (DRA7xx-based yet-to-be-released board)
> with v3.18-rc2.
> 
> Tested-by: Felipe Balbi <balbi@ti.com>
> 

Ping on this

Regards
Mugunthan V N

  reply	other threads:[~2014-11-06 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 10:00 [PATCH v3 0/2] Add DRA7xx CPSW Ethernet support in Device Tree Mugunthan V N
2014-10-21 10:01 ` [PATCH v3 1/2] ARM: dts: dra7: Add CPSW and MDIO module nodes for dra7 Mugunthan V N
2014-10-21 10:01 ` [PATCH v3 2/2] ARM: dts: dra7-evm: Enable CPSW and MDIO for dra7xx EVM Mugunthan V N
2014-10-21 10:07 ` [PATCH v3 0/2] Add DRA7xx CPSW Ethernet support in Device Tree Mugunthan V N
     [not found]   ` <54463063.80207-l0cyMroinI0@public.gmane.org>
2014-10-21 17:22     ` Nishanth Menon
2014-11-03 16:27       ` Felipe Balbi
2014-11-06 17:03         ` Mugunthan V N [this message]
     [not found]           ` <545BA9EE.1040905-l0cyMroinI0@public.gmane.org>
2014-12-04 20:14             ` Felipe Balbi
2014-12-04 20:14               ` Felipe Balbi
     [not found] ` <1413885661-4850-1-git-send-email-mugunthanvnm-l0cyMroinI0@public.gmane.org>
2014-11-10 17:52   ` 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=545BA9EE.1040905@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@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).