From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org,
Manuel Lauss <manuel.lauss@googlemail.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] alchemy: add au1000-eth platform device
Date: Tue, 18 Aug 2009 18:56:37 +0400 [thread overview]
Message-ID: <4A8AC125.3020602@ru.mvista.com> (raw)
In-Reply-To: <200908170105.38154.florian@openwrt.org>
Hello.
Florian Fainelli wrote:
> This patch adds the board code to register a per-board au1000-eth
> platform device to be used wit the au1000-eth platform driver in a
> subsequent patch. Note that the au1000-eth driver knows about the
> default driver settings such that we do not need to pass any
> platform_data informations in most cases except db1x00.
Sigh, NAK...
Please don't register the SoC device per board, do it in
alchemy/common/platfrom.c and find a way to pass the board specific platform
data from the board file there instead -- something like
arch/arm/mach-davinci/usb.c does.
> Signed-off-by: Florian Fainelli <florian@openwrt.org>
[...]
> diff --git a/arch/mips/include/asm/mach-au1x00/au1xxx_eth.h b/arch/mips/include/asm/mach-au1x00/au1xxx_eth.h
> new file mode 100644
> index 0000000..6d1543e
> --- /dev/null
> +++ b/arch/mips/include/asm/mach-au1x00/au1xxx_eth.h
> @@ -0,0 +1,33 @@
> +#ifndef __AU1X00_ETH_DATA_H
> +#define __AU1X00_ETH_DATA_H
> +
> +/* Macro to help defining the Ethernet MAC resources */
> +#define MAC_RES(_base, _enable, _irq) \
> + { \
> + .start = CPHYSADDR(_base), \
> + .end = CPHYSADDR(_base + 0xffff), \
> + .flags = IORESOURCE_MEM, \
> + }, \
> + { \
> + .start = CPHYSADDR(_enable), \
> + .end = CPHYSADDR(_enable + 0x4), \
s/4/3/.
WBR, Sergei
next prev parent reply other threads:[~2009-08-18 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 23:05 [PATCH 1/2] alchemy: add au1000-eth platform device Florian Fainelli
2009-08-18 14:56 ` Sergei Shtylyov [this message]
2009-08-18 16:01 ` Florian Fainelli
2009-08-21 16:53 ` Florian Fainelli
2009-08-21 17:23 ` Manuel Lauss
2009-08-24 18:02 ` Sergei Shtylyov
2009-08-27 12:42 ` Florian Fainelli
2009-08-27 14:15 ` Sergei Shtylyov
2009-08-27 14:55 ` Florian Fainelli
2009-10-17 8:48 ` Florian Fainelli
2009-10-23 16:51 ` Sergei Shtylyov
2009-11-03 21:14 ` Florian Fainelli
-- strict thread matches above, loose matches on Subject: below --
2009-11-10 0:13 Florian Fainelli
2009-11-12 16:41 ` Ralf Baechle
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=4A8AC125.3020602@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).