From: David Daney <ddaney@caviumnetworks.com>
To: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: David Daney <ddaney@caviumnetworks.com>
Subject: [PATCH 0/2] of/phylib: Use device tree properties for PHY configuration.
Date: Wed, 17 Nov 2010 15:54:29 -0800 [thread overview]
Message-ID: <1290038071-13296-1-git-send-email-ddaney@caviumnetworks.com> (raw)
Here is my first take at using the device tree to control PHY
configuration. This first set enables some Marvell PHYs. If the
scheme is deemed acceptable, I would probably do something similar for
Broadcom PHYs as well.
The first patch is the meat of the change. The second adds support
for the 88E1149R PHY that I have on one of my boards.
David Daney (2):
of/phylib: Use device tree properties to initialize Marvell PHYs.
phylib: Add support for Marvell 88E1149R devices.
drivers/net/phy/marvell.c | 135 +++++++++++++++++++++++++++++++++++++++++++
include/linux/marvell_phy.h | 1 +
2 files changed, 136 insertions(+), 0 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-11-17 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 23:54 David Daney [this message]
2010-11-17 23:54 ` [PATCH 1/2] of/phylib: Use device tree properties to initialize Marvell PHYs David Daney
2010-11-18 0:01 ` David Daney
[not found] ` <marvell-phy@mdm.bga.com>
2010-11-18 17:40 ` [1/2] " David Daney
2010-11-18 19:32 ` [PATCH 1/2] " Cyril Chemparathy
2010-11-18 20:40 ` Grant Likely
2010-11-18 23:48 ` David Daney
2010-11-19 0:39 ` Grant Likely
2010-11-17 23:54 ` [PATCH 2/2] phylib: Add support for Marvell 88E1149R devices David Daney
2010-11-18 19:46 ` David Miller
2010-11-18 20:44 ` Grant Likely
2010-11-18 20:57 ` David Miller
2010-11-18 21:06 ` David Daney
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=1290038071-13296-1-git-send-email-ddaney@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®