All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: at91: sama5d2: Wrap cpu detection to fix macb driver
Date: Mon, 25 Mar 2019 11:08:39 +0100	[thread overview]
Message-ID: <5345167.Z57H08VWhP@ada> (raw)
In-Reply-To: <b6f99319-50ba-9db1-235a-160ac6c3d10d@microchip.com>

Hello Eugen,

Am Montag, 25. März 2019, 09:46:02 CET schrieb Eugen.Hristev at microchip.com:
> Are you sure there is a problem with this commit itself:
> 
> net: macb: Fix GEM hardware detection
> 
> as it looks , this commit fixes the interpretation of the MID register 
> w.r.t. the gem capability... not an issue there that your patch fixes.

Well, without the changeset "net: macb: Fix GEM hardware detection" the actual 
problem I had, would not trigger, because the SAMA5D2 is not recognized having 
the gem capability. That's why I asked if that additional fixes line is 
correct.

> More likely your patch fixes the fact that the sama5d2 soc was not 
> properly defining that macro, which was turned into a function, so your 
> patch fixes the code that changed the macro into a function, which broke 
> things... is my understanding correct ?

My patch fixes that soc detection only. The behaviour on SAMA5D2 however is as 
follows:

1) Without both patches (as in v2019.01): SAMA5D2 mac is not detected as gem → 
soc detection in function 'gem_is_gigabit_capable()' is not relevant for 
gigabit detection -> ethernet works (maybe accidentally, gem actually used 
like old mac?)

2) With my patch only: mac is not detected as gem AND soc is detected as 
SAMA5D2 → no gigabit detected → ethernet might work as in 1), not tested 
though

3) With the gem hw detect fix only (as in v2019.04-rc3 already): mac is 
detected as gem, soc is not detected as SAMA5D2 → falsely detected gigabit 
capability → ethernet broken (can you reproduce this?)

4) With both patches: hw recognized as gem, soc recognized as SAMA5D2 → mac 
used as gem, but without gigabit caps → works for me on custom board

Greets
Alex

  reply	other threads:[~2019-03-25 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 13:25 [U-Boot] [PATCH] ARM: at91: sama5d2: Wrap cpu detection to fix macb driver Alexander Dahl
2019-03-23  8:46 ` Alexander Dahl
2019-03-24  9:01   ` Bin Meng
2019-03-25  9:17 ` Alexander Dahl
2019-03-25  9:46   ` Eugen.Hristev at microchip.com
2019-03-25 10:08     ` Alexander Dahl [this message]
2019-03-28  7:27 ` Eugen.Hristev at microchip.com

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=5345167.Z57H08VWhP@ada \
    --to=ada@thorsis.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.