From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code.
Date: Mon, 14 Mar 2016 15:27:51 -0400 (EDT) [thread overview]
Message-ID: <20160314.152751.2108458769066613871.davem@davemloft.net> (raw)
In-Reply-To: <1457718791-6505-1-git-send-email-ddaney.cavm@gmail.com>
From: David Daney <ddaney.cavm@gmail.com>
Date: Fri, 11 Mar 2016 09:53:08 -0800
> Changes from v1:
>
> - In 1/3 Add back check for non-OF objects in bgx_init_of_phy(). It
> is probably not necessary, but better safe than sorry...
>
> The firmware on many Cavium Thunder systems configures the MDIO bus
> hardware to be probed as a PCI device. In order to use the MDIO bus
> drivers in this configuration, we must add PCI probing to the driver.
>
> There are two parts to this set of three patches:
>
> 1) Cleanup the PHY probing code in thunder_bgx.c to handle the case
> where there is no PHY attached to a port, as well as being more
> robust in the face of driver loading order by use of
> -EPROBE_DEFER.
>
> 2) Split mdio-octeon.c into two drivers, one with platform probing,
> and the other with PCI probing. Common code is shared between the
> two.
>
> Tested on several different Thunder and OCTEON systems, also compile
> tested on x86_64.
Series applied, thanks David.
next prev parent reply other threads:[~2016-03-14 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:53 [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code David Daney
2016-03-11 17:53 ` [PATCH v2 1/3] net: thunderx: Cleanup PHY probing code David Daney
2016-03-11 17:53 ` [PATCH v2 2/3] phy: mdio-octeon: Refactor into two files/modules David Daney
2016-03-11 17:53 ` [PATCH v2 3/3] phy: mdio-thunder: Add driver for Cavium Thunder SoC MDIO buses David Daney
2016-03-16 22:50 ` Andreas Färber
2016-03-16 22:54 ` David Daney
2016-03-16 23:24 ` Andreas Färber
2016-03-12 0:08 ` [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code David Daney
2016-03-14 19:27 ` David Miller [this message]
2016-03-14 20:12 ` David Daney
2016-03-14 20:18 ` David Miller
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=20160314.152751.2108458769066613871.davem@davemloft.net \
--to=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).