From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/9] NET: fec_mxc.c: Add support for MII for MX5 SOCs
Date: Tue, 12 Jun 2012 19:02:16 +0200 [thread overview]
Message-ID: <4FD77618.8050804@denx.de> (raw)
In-Reply-To: <4FB24E86.5010509@de.bosch.com>
On 15/05/2012 14:39, Dirk Behme wrote:
> On 22.02.2012 11:24, Stefano Babic wrote:
>> Signed-off-by: Stefano Babic <sbabic@denx.de>
>> CC: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
Hi Dirk,
>> drivers/net/fec_mxc.c | 5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/net/fec_mxc.c b/drivers/net/fec_mxc.c
>> index 1fdd071..201e5d2 100644
>> --- a/drivers/net/fec_mxc.c
>> +++ b/drivers/net/fec_mxc.c
>> @@ -419,8 +419,13 @@ static int fec_open(struct eth_device *edev)
>> while (readw(&fec->eth->miigsk_enr) & MIIGSK_ENR_READY)
>> udelay(2);
>>
>> +#if !defined(CONFIG_MII)
>> /* configure gasket for RMII, 50 MHz, no loopback, and no echo */
>> writew(MIIGSK_CFGR_IF_MODE_RMII, &fec->eth->miigsk_cfgr);
>> +#else
>> + /* configure gasket for MII, no loopback, and no echo */
>> + writew(MIIGSK_CFGR_IF_MODE_MII, &fec->eth->miigsk_cfgr);
>> +#endif
>>
>> /* re-enable the gasket */
>> writew(MIIGSK_ENR_EN, &fec->eth->miigsk_enr);
>
> I have this patch on my list of pending patches.
>
> What's the status of this?
This patch must be reworked. See also the discussion about Timo's patch
on http://patchwork.ozlabs.org/patch/153695/
There is some confusion about how to set the interface type. At the
beginning, CONFIG_MII or CONFIG_RMII was used, but after the
introduction of the MX28, CONFIG_FEC_XCV_TYPE is used. This should be
unified, and I tend to use CONFIG_FEC_XCV_TYPE for all i.MX
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2012-06-12 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 10:24 [U-Boot] [PATCH 1/9] Define UART4 and UART5 base addresses Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 2/9] NET: fec_mxc.c: Add support for MII for MX5 SOCs Stefano Babic
2012-05-15 12:39 ` Dirk Behme
2012-06-12 17:02 ` Stefano Babic [this message]
2012-02-22 10:24 ` [U-Boot] [PATCH 3/9] NET: fec_mxc.c: Add a way to disable auto negotiation Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 4/9] MX5: Add definitions for SATA controller Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 5/9] SATA: check for return value from sata functions Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 6/9] MX53: add function to set SATA clock to internal Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 7/9] SATA: add driver for MX5 / MX6 SOCs Stefano Babic
2012-02-22 10:24 ` [U-Boot] [PATCH 8/9] MX53: Add support to ESG ima3 board Stefano Babic
2012-02-22 10:30 ` Dirk Behme
2012-02-22 10:46 ` Stefano Babic
2012-02-22 11:46 ` Dirk Behme
2012-02-22 10:24 ` [U-Boot] [PATCH 9/9] MX53: mx53loco: Add SATA support Stefano Babic
2012-02-23 15:40 ` Jason Hui
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=4FD77618.8050804@denx.de \
--to=sbabic@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox