From: Mugunthan V N <mugunthanvnm@ti.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, devicetree-discuss@lists.ozlabs.org,
linux-omap@vger.kernel.org, Mugunthan V N <mugunthanvnm@ti.com>
Subject: [net-next PATCH 0/3] Adding phy register fixup in DT
Date: Mon, 22 Apr 2013 23:50:35 +0530 [thread overview]
Message-ID: <1366654838-26479-1-git-send-email-mugunthanvnm@ti.com> (raw)
In earlier days phy fixup was added to phy frame work in board files.
As there won't be any board files here after the same has to be done in DT
This patch series adds the following features
* support for adding phy resigter fixup via DT
* adds phy id for EVMsk n DTS file
* adds phy fixup for AM335x EVM and EVMsk
Mugunthan V N (3):
drivers: of: add phy fixup support in DT
ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk
ARM: dts: AM33XX: add phy fixup for evm and evmsk boards
.../devicetree/bindings/net/phy-fixup.txt | 26 ++++++
arch/arm/boot/dts/am335x-evm.dts | 10 +++
arch/arm/boot/dts/am335x-evmsk.dts | 18 ++++
drivers/of/of_net.c | 92 ++++++++++++++++++++
include/linux/of_net.h | 6 ++
5 files changed, 152 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/phy-fixup.txt
--
1.7.9.5
next reply other threads:[~2013-04-22 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 18:20 Mugunthan V N [this message]
2013-04-22 18:20 ` [net-next PATCH 1/3] drivers: of: add phy fixup support in DT Mugunthan V N
2013-04-25 7:56 ` David Miller
2013-04-25 10:04 ` Mugunthan V N
2013-04-25 16:09 ` Ben Hutchings
2013-04-22 18:20 ` [net-next PATCH 2/3] ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk Mugunthan V N
2013-04-22 18:20 ` [net-next PATCH 3/3] ARM: dts: AM33XX: add phy fixup for evm and evmsk boards Mugunthan V N
2013-04-23 8:02 ` [net-next PATCH 0/3] Adding phy register fixup in DT Sascha Hauer
[not found] ` <20130423080257.GQ32299-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-24 8:42 ` Mugunthan V N
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=1366654838-26479-1-git-send-email-mugunthanvnm@ti.com \
--to=mugunthanvnm@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).