All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Claudio Lanconelli <lanconelli.claudio@eptar.com>
Cc: netdev@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [PATCH][resend] add driver for enc28j60 ethernet chip
Date: Fri, 18 Jan 2008 15:01:39 -0500	[thread overview]
Message-ID: <479105A3.3040508@garzik.org> (raw)
In-Reply-To: <478B32BC.6070206@eptar.com>

Claudio Lanconelli wrote:
> This patch add support for Microchip enc28j60 10Mbps Ethernet chip used 
> in embedded systems
> due to its cheap SPI interface.
> This 2nd version include changes from previous comments by Jeff and 
> Stephen,
> all but NAPI, see comments below at this regard.
> 
> I resend the patch because I didn't receive any feedback.
> 
> Changes to 1st version:
> - use mutex instead of semaphore
> - add carrier detect handling
> - add ethtool support
> - set_multicast_list when the interface is up using a workqueue
> - add restart_work to reset the chip in case of tx_timeout
> - removed kmalloc() for spi_transfer_buf (array defined in the priv struct)
> 
> Jeff Garzik wrote:
>>
>> comments:
>>
>> * Why do interrupt work in a kernel thread?  Your comment says you 
>> cannot, but does not explain.
> The enc28j60 is a SPI to Ethernet adapter, so we cannot access register 
> with simple in() out() instructions, but we need to use the SPI 
> subsystem. The spi_sync() basic operation to read/write a register is a 
> blocking operation, so can't be done in interrupt context.
> Since every basic operation like read interrupt flag register call 
> spi_sync() we need the work queue for almost everything.
> 
>>
>> * should use NAPI
>>
> For the reason I just explained I don't think NAPI is a viable way for 
> enc28j60.
> Furthermore enc28j60 is a 10Mb only device and probably don't suffer to 
> interrupt overload.
> 
> I'm waiting for any comments, please.

applied



      reply	other threads:[~2008-01-18 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 10:00 [PATCH][resend] add driver for enc28j60 ethernet chip Claudio Lanconelli
2008-01-18 20:01 ` Jeff Garzik [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=479105A3.3040508@garzik.org \
    --to=jeff@garzik.org \
    --cc=jgarzik@pobox.com \
    --cc=lanconelli.claudio@eptar.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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.