public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] cpsw not working with slave2 port defined only
Date: Mon, 1 Jun 2015 14:40:40 +0530	[thread overview]
Message-ID: <556C2190.5070803@ti.com> (raw)
In-Reply-To: <CAAfyv34Bi=6shMy39CXj0VnqMhV=byEmnTqsr0T_pkWgV7yXVg@mail.gmail.com>

On Tuesday 26 May 2015 01:00 AM, Belisko Marek wrote:
> Hi,
> 
> I have custom am33xx board with phy connected to slave2 port. I
> copy'n'paste cpsw setup from /board/BuR/common/common.c but I'm using
> only slave2 port (RMII mode) so my cpsw_slave_data looks like:
> 
> static struct cpsw_slave_data cpsw_slaves[] = {
> {
>                  .slave_reg_ofs  = 0x308,
>                  .sliver_reg_ofs = 0xdc0,
>                  .phy_addr       = 4,
> },
> };
> 
> with this configuration cpsw driver can detect link but it cannot
> establish any communication (tested with dhcp command). When I add to
> cpsw_slaves dummy slave1 port definition (with e.g. phy_addr = 0) it
> start working.
> 
> mdio bus is working fine (tested with mdio list + mdio read). Pinmux
> is good as it works with dummy slave1 config. Any ideas what I'm doing
> wrong or why only slave2 port cannot be used? I grep whole source code
> but all boards using cpsw use slave1 only or slave1/slave2
> configurations. Many thanks.
> 

Do not remove slave 0 structures and have no of slaves as 2 and set
active slave to 1 as done in the following commit
4c8014b9429b593c28fbf0384a6c7ded8587806a in mainline u-boot.

The driver uses the slave numbers to add mac address to ALE, which will
fail when you remove slaves from the salve structures.

Regards
Mugunthan V N

  parent reply	other threads:[~2015-06-01  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 19:30 [U-Boot] cpsw not working with slave2 port defined only Belisko Marek
2015-05-26  2:51 ` Mx21
2015-05-26  6:06   ` Belisko Marek
2015-05-26 12:29 ` Belisko Marek
2015-05-26 13:51   ` Mx21
2015-05-27  6:54     ` Belisko Marek
2015-06-01  9:10 ` Mugunthan V N [this message]
2015-06-02  6:20   ` Belisko Marek

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=556C2190.5070803@ti.com \
    --to=mugunthanvnm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox