linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Sinkovsky <msink@permonline.ru>
To: Florian Fainelli <florian@openwrt.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	msink@permonline.ru
Subject: Re: [PATCH v2] ethernet driver for the WIZnet W5300 chip
Date: Thu, 22 Mar 2012 12:58:10 +0600	[thread overview]
Message-ID: <4F6ACD82.2030505@permonline.ru> (raw)
In-Reply-To: <4F69EA7E.4030606@openwrt.org>

21.03.2012 20:49, Florian Fainelli wrote:
>> +#if defined(CONFIG_WIZNET_BUS_DIRECT)
>> +#define detect_bus_mode(priv, mem_size) do {} while(0)
>> +#define read_reg_u16    read_u16_direct
>> +#define write_reg_u16    write_u16_direct
>> +
>> +#elif defined(CONFIG_WIZNET_BUS_INDIRECT)
>> +#define detect_bus_mode(priv, mem_size) do {} while(0)
>> +#define read_reg_u16    read_u16_indirect
>> +#define write_reg_u16    write_u16_indirect
> Looks like you don't have to make such decisions at compile-time. 
> Since it is a platform driver, better supply this through 
> platform_data instead.
Interface bus mode can be selected in .config (make menuconfig etc.)
If don't selected explicitly in .config, platform_device.resource[] is 
used in runtime to setup callbacks.
This hack was done for performance reasons, but may be not necessary, 
I'm not sure.


> Please implement phylib to properly report the link state to the 
> networking stack and ethtool.
This chip don't allow any access to phy interface, it completely hidden 
for host processor.
The only way I found - to wire pin LINK from W5300 to some GPIO, then 
ise RIGING/FALLING interrupt for tthat GPIO:
> +static irqreturn_t w5300_detect_link(int irq, void *ndev_instance)
> +{
> +        struct net_device *ndev = ndev_instance;
> +        struct w5300_private *priv = netdev_priv(ndev);
> +
> +        if (netif_running(ndev)) {
> +                if (gpio_get_value(priv->link) == 0)
> +                        netif_carrier_off(ndev);
> +                else
> +                        netif_carrier_on(ndev);
> +        }
> +
> +        return IRQ_HANDLED;
> +}
Isn't it enough for networking stack?


> Allow platform_data to pass a valid MAC address to this driver instead 
> of defaulting to random unconditionnaly.
>
Do you mean - create .h file in /include/linux/platform_data/ ?
Ok, will do in next version.

Thanks.

---
Mike



  reply	other threads:[~2012-03-22  6:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  9:23 [PATCH v2] ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-03-20 18:08 ` Ben Hutchings
2012-03-21 14:49 ` Florian Fainelli
2012-03-22  6:58   ` Mike Sinkovsky [this message]
2012-03-24 11:02 ` [PATCH v3] Ethernet " Mike Sinkovsky
2012-03-24 15:53   ` Joe Perches
2012-03-24 16:10   ` Eric Dumazet
2012-03-26  9:05     ` Mike Sinkovsky
2012-03-26  9:07 ` [PATCH v4] " Mike Sinkovsky
2012-03-28  2:35   ` David Miller
2012-03-30  7:00   ` [PATCH v5 1/2] " Mike Sinkovsky
2012-03-31 21:45     ` Mark Brown
2012-03-30  7:00   ` [PATCH v5 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky
2012-03-30  9:23     ` Eric Dumazet
2012-03-31  9:40       ` Francois Romieu
2012-03-31  9:46         ` Francois Romieu
2012-03-31  9:52       ` Mike Sinkovsky
2012-03-31 10:24         ` Eric Dumazet
2012-03-31 21:23     ` Mark Brown
2012-04-02  9:40       ` Mike Sinkovsky
2012-04-02 11:21         ` Mark Brown
2012-04-03 10:58   ` [PATCH v6 0/2] Ethernet drivers for WIZnet chips Mike Sinkovsky
2012-04-03 11:39     ` Eric Dumazet
2012-04-03 12:15       ` Mike Sinkovsky
2012-04-03 12:29         ` Eric Dumazet
2012-04-04  5:58           ` Mike Sinkovsky
2012-04-04  6:17             ` Eric Dumazet
2012-04-04  7:25               ` Mike Sinkovsky
2012-04-04  7:23     ` [PATCH v7 " Mike Sinkovsky
2012-04-04 11:57       ` [PATCH v8 " Mike Sinkovsky
2012-04-05  1:15         ` David Miller
2012-04-05  5:36           ` Mike Sinkovsky
2012-04-04 11:57       ` [PATCH v8 1/2] Ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-04-04 11:57       ` [PATCH v8 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky
2012-04-04 12:08       ` [PATCH v8 0/2] Ethernet drivers for WIZnet chips Mike Sinkovsky
2012-04-05  5:33         ` [PATCH v9 " Mike Sinkovsky
2012-04-05  5:47           ` David Miller
2012-04-05  5:33         ` [PATCH v9 1/2] Ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-04-05  5:33         ` [PATCH v9 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky
2012-04-04 12:08       ` [PATCH v8 1/2] Ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-04-04 12:08       ` [PATCH v8 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky
2012-04-04  7:23     ` [PATCH v7 1/2] Ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-04-04  7:23     ` [PATCH v7 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky
2012-04-03 10:58   ` [PATCH v6 1/2] Ethernet driver for the WIZnet W5300 chip Mike Sinkovsky
2012-04-03 13:36     ` Mark Brown
2012-04-04  6:18       ` Mike Sinkovsky
2012-04-04 10:01         ` Mark Brown
2012-04-04 11:00           ` Mike Sinkovsky
2012-04-03 10:58   ` [PATCH v6 2/2] Ethernet driver for the WIZnet W5100 chip Mike Sinkovsky

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=4F6ACD82.2030505@permonline.ru \
    --to=msink@permonline.ru \
    --cc=florian@openwrt.org \
    --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;
as well as URLs for NNTP newsgroup(s).