From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 5/5] arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
Date: Tue, 25 Nov 2014 09:56:22 -0800 [thread overview]
Message-ID: <5474C2C6.1050302@freescale.com> (raw)
In-Reply-To: <1413530796-12881-5-git-send-email-b18965@freescale.com>
On 10/17/2014 12:26 AM, Alison Wang wrote:
> EC1 pins in RCW can be selected as RGMII1, GPIO3, CAN1/2, FTM1 or
> SAI1/2. There is a bug that EC3 RGMII could not work when selecting EC1
> as other functionality except RGMII. The workaround is to select
> ge2_clk125 for eTSEC clock muxing in register SCFG_ETSECCMCR.
>
> Signed-off-by: Alison Wang <alison.wang@freescale.com>
> ---
> Change log:
> v2: New patch.
>
> board/freescale/ls1021aqds/ls1021aqds.c | 1 +
> 1 file changed, 1 insertion(+)
Applied to u-boot-fsl-qoriq master. Awaiting upstream. Thanks.
York
next prev parent reply other threads:[~2014-11-25 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 7:26 [U-Boot] [PATCH v2 1/5] arm: ls102xa: Add snoop disable for slave port 0, 1 and 2 Alison Wang
2014-10-17 7:26 ` [U-Boot] [PATCH v2 2/5] arm: ls102xa: Remove bit reversing for SCFG registers Alison Wang
2014-11-25 17:55 ` York Sun
2014-10-17 7:26 ` [U-Boot] [PATCH v2 3/5] ls102xa: ifc: nor: fix the write issue when bytes unaligned Alison Wang
2014-11-25 17:55 ` York Sun
2014-10-17 7:26 ` [U-Boot] [PATCH v2 4/5] arm: ls102xa: Add SystemID EEPROM support for LS1021ATWR board Alison Wang
2014-11-25 17:56 ` York Sun
2014-10-17 7:26 ` [U-Boot] [PATCH v2 5/5] arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing Alison Wang
2014-11-25 17:56 ` York Sun [this message]
2014-11-25 17:54 ` [U-Boot] [PATCH v2 1/5] arm: ls102xa: Add snoop disable for slave port 0, 1 and 2 York Sun
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=5474C2C6.1050302@freescale.com \
--to=yorksun@freescale.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.