From: David Miller <davem@davemloft.net>
To: tony@atomide.com
Cc: mugunthanvnm@ti.com, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] net: davinci_emac: Fix platform data handling and make usable for am3517
Date: Thu, 05 Dec 2013 20:39:55 -0500 (EST) [thread overview]
Message-ID: <20131205.203955.1282361417309480469.davem@davemloft.net> (raw)
In-Reply-To: <20131203231301.GN26766@atomide.com>
From: Tony Lindgren <tony@atomide.com>
Date: Tue, 3 Dec 2013 15:13:02 -0800
> When booted with device tree, we may still have platform data passed
> as auxdata. For am3517 this is needed for passing the interrupt_enable
> and interrupt_disable callbacks that access the omap system control module
> registers. These callback functions will eventually go away when we have
> a separate system control module driver.
>
> Some of the things that are currently passed as platform data we don't need
> to set up as device tree properties as they are always the same on am3517.
> So let's use a new compatible flag for those so we can get those from
> the device tree match data.
>
> Also note that we need to fix setting of phy_dev to NULL instead of an empty
> string as the code later on uses that to find the first phy on the mdio bus.
> This seems to have been caused by 5d69e0076a72 (net: davinci_emac: switch to
> new mdio).
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
Applied, thanks.
prev parent reply other threads:[~2013-12-06 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 23:13 [PATCH] net: davinci_emac: Fix platform data handling and make usable for am3517 Tony Lindgren
2013-12-06 1:39 ` David Miller [this message]
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=20131205.203955.1282361417309480469.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=tony@atomide.com \
/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).