All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken.Lin <ken.lin@advantech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot] AR8033 SerDes Test and System Mode Control setting issue
Date: Mon, 16 Jan 2017 14:14:07 -0800	[thread overview]
Message-ID: <WM!f8f7a94730faf97e7355f634098fcf592a54a0cd2e436ae69d541c188024dc7ce0fd699b77201f9e088be67c53d80625!@dg.advantech.com> (raw)
In-Reply-To: 03B5A3CA1724CE4EAC32B27E39292A677FC74217B5@AUSMAIL1.AUS.ADVANTECH.CORP

Hi Joe and Mugunthan,

We encountered the voltage peak issue while doing the IEEE PHY conformance test, which has to do with the AR8033 register (SetDes Test and System Mode Control) setting in u-boot.
In your commit change info, you tried to enable tx clock delay by setting bit 8 to 1 (filling in 0x100, setting the reserved bits to 0) for solving the auto negotiation failure issue.
https://patchwork.ozlabs.org/patch/681801/

After we checked with Qualcomm (Atheros) and they responded that on their platform, the register should be set to 0x2C47 (for the reserved bits) and this would solve the voltage peak issue we experienced.
Could you please help check if it's appropriate to set the reserved bits according to Qualcomm's setting since your commit breaks the original setting (see https://community.nxp.com/message/868898 for more details info)?
Please let me know if you have any suggestions/comments on this.

Thank you

Cheers,
Ken Lin


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

       reply	other threads:[~2017-01-16 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <03B5A3CA1724CE4EAC32B27E39292A677FC74217B5@AUSMAIL1.AUS.ADVANTECH.CORP>
2017-01-16 22:14 ` Ken.Lin [this message]
2017-01-17 11:23   ` [U-Boot] [u-boot] AR8033 SerDes Test and System Mode Control setting issue Sekhar Nori
     [not found]     ` <WM!e204a2dce50f5a3be9a482be4676bbf7b4b8261cb96079c63b1b47a00debe02288acc12e037d79a15cfe72b40d17be0f!@dg.advantech.com>
     [not found]       ` <03B5A3CA1724CE4EAC32B27E39292A677FC7512E38@AUSMAIL1.AUS.ADVANTECH.CORP>
2017-01-31 22:25         ` Ken.Lin

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='WM'\!'f8f7a94730faf97e7355f634098fcf592a54a0cd2e436ae69d541c188024dc7ce0fd699b77201f9e088be67c53d80625'\!'@dg.advantech.com' \
    --to=ken.lin@advantech.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.