All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: davem@davemloft.net, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, f.fainelli@gmail.com,
	netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] net: qualcomm: new Ethernet over SPI driver for QCA7000
Date: Tue, 29 Apr 2014 17:54:12 +0200	[thread overview]
Message-ID: <535FCB24.2010507@i2se.com> (raw)
In-Reply-To: <4860368.6Apskanc4s@wuerfel>

Hi,

Am 29.04.2014 10:14, schrieb Arnd Bergmann:
> i think it's more important to use standard interfaces here. A random
> user trying to debug a problem with this hardware may know about
> ethtool or find that documented somewhere, but wouldn't know about the
> debugfs interfaces without reading the driver source code. The ethtool
> interface is also easier to maintain than the debugfs files. 

okay, i'll try it.

> As far as I know it's also not mandatory.
>
> If the hardware interfaces require calling sleeping functions, it
> may not actually be possible, but if you can use it, it normally
> provides better performance.

As i understood NAPI is good for high load on 1000 MBit ethernet, but
the QCA7000 has
in best case only a 10 MBit powerline connection. Additionally these
packets must be transfered
over a half duplex SPI. So i think the current driver implementation
isn't a bottle neck.

>
>> Does this mean the current state of the driver should better go to staging?
> Probably not, the driver doesn't look bad overall.
>
> 	Arnd
>

I'm relieved to hear that. Thanks for your comments.

Stefan<http://dict.leo.org/#/search=that.&searchLoc=0&resultOrder=basic&multiwordShowSingle=on>

  reply	other threads:[~2014-04-29 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 17:54 [PATCH RFC 0/2] add Qualcomm QCA7000 ethernet driver Stefan Wahren
2014-04-28 17:54 ` [PATCH RFC 1/2] Documentation: add Device tree bindings for QCA7000 Stefan Wahren
2014-04-28 19:57   ` Arnd Bergmann
2014-04-29  6:30     ` Stefan Wahren
2014-04-29  7:57       ` Arnd Bergmann
2014-04-29 22:36   ` Mark Rutland
2014-04-30  7:30     ` Stefan Wahren
2014-04-28 17:54 ` [PATCH RFC 2/2] net: qualcomm: new Ethernet over SPI driver " Stefan Wahren
2014-04-28 20:09   ` Arnd Bergmann
2014-04-29  6:51     ` Stefan Wahren
2014-04-29  8:14       ` Arnd Bergmann
2014-04-29 15:54         ` Stefan Wahren [this message]
2014-04-29 18:14           ` Arnd Bergmann
2014-04-30  8:09             ` Stefan Wahren
2014-04-30  9:32               ` Arnd Bergmann
2014-04-30 15:36             ` Stefan Wahren

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=535FCB24.2010507@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.