public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: i.MX6Q: Add fixup for RTL8211E Gigabit Ethernet PHY
Date: Wed, 04 Mar 2015 20:44:23 +0100	[thread overview]
Message-ID: <2796821.5chD2g3yoZ@wuerfel> (raw)
In-Reply-To: <4686121425496122@web26g.yandex.ru>

On Wednesday 04 March 2015 22:08:42 ????? ?????? wrote:
> 
> >>  +               phy_register_fixup_for_uid(PHY_ID_RTL8211E, 0xffffffff,
> >>  +                               rtl8211e_phy_fixup);
> >
> > How do you ensure that this fixup is only applied on the boards that need
> > it, rather than all machines that happen to have this phy?
> 
> I've thought that if there no other fixups in code here checking a particular 
> board where they run, this isn't necessary.
> This SoC has only one ethernet MAC and if it is connected to this PHY, 
> it should be initalized this way independently of board, like other code here does, I think.
> 
> This code just does forcibly restart autonegotiation.
> I can wrap it in if(!of_machine_is_compatible(...)){}, if it is need.

Your explanation makes sense to me, though I wonder what the property of this
SoC is that requires the PHY fixup. Is this something we could or should be doing
in a more general way using the PHY API, by having the device driver call a
phy API function to restart autoneg independent of the PHY?

> And I see, mask is wrong - I should use 0x001fffff.
> 
> I'll resend a patch, thanks.

Ok.

	Arnd

  reply	other threads:[~2015-03-04 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 17:42 [PATCH] ARM: i.MX6Q: Add fixup for RTL8211E Gigabit Ethernet PHY Andrey Panov
2015-03-03 23:29 ` Arnd Bergmann
2015-03-04 19:08   ` Панов Андрей
2015-03-04 19:44     ` Arnd Bergmann [this message]
2015-03-04 20:05       ` Панов Андрей
2015-03-04 20:18         ` Fabio Estevam
2015-03-04 20:32           ` Панов Андрей
2015-03-04 21:31             ` Arnd Bergmann
2015-03-05  6:40               ` Панов Андрей
     [not found] <1424892206-18679-1-git-send-email-rockford@yandex.ru>
2015-02-25 19:34 ` Marc Kleine-Budde
2015-03-03  2:57   ` Shawn Guo

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=2796821.5chD2g3yoZ@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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