[OpenWrt-Devel] [PATCH 2/2] kernel: add at803x fix for sgmii mode

Christian Lamparter chunkeey at googlemail.com
Sun Dec 20 15:20:21 EST 2015


On Sunday, December 20, 2015 08:20:12 PM Roman Yeryomin wrote:
> On 20 December 2015 at 15:13, Christian Lamparter
> <chunkeey at googlemail.com> wrote:
> > On Sunday, December 20, 2015 02:30:39 AM Roman Yeryomin wrote:
> >> Some (possibly broken) bootloaders incorreclty initialize at8033
> >> phy. This patch enables sgmii autonegotiation mode.
> >>
> >> Signed-off-by: Roman Yeryomin <roman at advem.lv>
> >> ---
> > Can you tell us a bit about the "possibly broken" bootloaders you talk
> > about? Like what devices (based "possibly" on QCA956x) have those and
> > from where you are getting this information?
> The device is uapac.
Unifi AP AC? So, GPL - Sources are hard to come by... Sad.

> But I'm taking about phy setup itself...
> > I'm asking because we (Chris and I) encountered similar issues with the
> > Cisco Merakin MR18. It has a AR8035-A (confirmed by opening up the device)
> > but calls it a AR8033. The PHY apparently connected via RGMII
> > (uses QCA955X_ETH_CFG_RGMII_EN [0]) but the device needs to write some
> > calibration values to SGMII and SERDES registers in order to work [1].
> > We are quite keen to know what's going on since this seems counter-intuitive.
> ..and you are talking about SoC's gmac setup, which is completely
> different thing.
> Also, FYI, AR8035 doesn't have sgmii, it has rgmii only.
Exactly, this is the issue here. The AR803x datasheet lists it as RGMII
only. But the Cisco's source tells me the opposite. I hoped to find a QCA
device which uses SGMII properly to check if they do the same "calibrations"
code or if the stuff is specific to the MR18. But because this device comes
from Ubiquiti, then this is probably not going to happen.

openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list