[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2157c96-0b5c-5b7a-31c2-9eb4df71c73d@cogentembedded.com>
Date: Thu, 22 Sep 2016 20:08:47 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: David Miller <davem@...emloft.net>, sean.wang@...iatek.com
Cc: john@...ozen.org, nbd@...nwrt.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
andrew@...n.ch, f.fainelli@...il.com, keyhaede@...il.com,
objelf@...il.com
Subject: Re: [PATCH net-next v2 0/3] add support for RGMII on GMAC0 through
TRGMII hardware module
Hello.
On 09/22/2016 03:22 PM, David Miller wrote:
>> By default, GMAC0 is connected to built-in switch called
>> MT7530 through the proprietary interface called Turbo RGMII
>> (TRGMII). TRGMII also supports well for RGMII as generic external
>> PHY uses but requires some slight changes to the setup of TRGMII
>> and doesn't have well support on current driver.
>>
>> So this patchset
>> 1) provides the slight changes of the setup for RGMII can work
>> through TRGMII
>> 2) adds additional setting "trgmii" as PHY_INTERFACE_MODE_TRGMII
>> about phy-mode on device tree to make GMAC0 distinguish which
>> mode it runs
>> 3) changes dynamically source clock, TX/RX delay and interface
>> mode on TRGMII for adapting various link
>>
>> Changes since v1:
>> - fixed the style of comment which doesn't have a space at
>> the beginning and end of comment lines
>> - add support for phy-mode "trgmii" as PHY_INTERFACE_MODE_TRGMII
>> into linux/phy.h
>> - enhance the Documentation about device tree binding for trgmii
>> which is applicable only for GMAC0 which uses fixed-link
>
> Series applied.
Despite my comments? Sigh...
MBR, Sergei
Powered by blists - more mailing lists