1. 09 6月, 2007 2 次提交
    • S
      USB: cxacru: ignore error trying to start ADSL in atm_start · fd209e35
      Simon Arlott 提交于
      The sysfs adsl_status attribute ignores (aside from returning -EIO to the
      user) any error sending a START/STOP command to the device and there is at
      least one firmware which never sends a response but appears to work
      regardless.  Therefore atm_start should also continue if an error is received
      so that such firmware is usable.
      
      The official Conexant driver doesn't expect a reply either but this is for
      another device (E2 router) and a commonly used firmware does respond.
      
      Also, there is no point in changing -ECONNRESET to -ETIMEDOUT since nothing
      ever checks for either of these values.
      Signed-off-by: NSimon Arlott <simon@fire.lp0.eu>
      Cc: Duncan Sands <duncan.sands@math.u-psud.fr>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      fd209e35
    • S
      USB: cxacru: create sysfs attributes in atm_start instead of bind · da1f82b5
      Simon Arlott 提交于
      Since usbatm doesn't set the usb_interface driver data until after calling
      bind and heavy_init, it would be NULL when the sysfs attributes are read.
      Reading the MAC address from atm_dev before atm_dev exists would have been
      be possible too.
      
      Calling create_device_file in atm_start will avoid this problem, and the
      data is useless until the first status poll runs.  However, it must be
      ready before a status poll does a printk on line status change otherwise
      userspace could react before the files exist.
      
      For completeness I've moved remove_device_file to atm_stop so it's not
      called in unbind when it's not needed.  There's no point starting ADSL if
      atm_start could still fail either.
      Signed-off-by: NSimon Arlott <simon@fire.lp0.eu>
      Cc: Duncan Sands <duncan.sands@math.u-psud.fr>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      da1f82b5
  2. 10 5月, 2007 1 次提交
  3. 09 5月, 2007 1 次提交
  4. 28 4月, 2007 4 次提交
  5. 26 4月, 2007 4 次提交
  6. 17 2月, 2007 1 次提交
  7. 08 2月, 2007 1 次提交
  8. 08 12月, 2006 1 次提交
  9. 02 12月, 2006 2 次提交
  10. 22 11月, 2006 1 次提交
  11. 18 10月, 2006 8 次提交
  12. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  13. 04 10月, 2006 1 次提交
  14. 28 9月, 2006 1 次提交
  15. 22 6月, 2006 2 次提交
  16. 09 5月, 2006 2 次提交
  17. 15 4月, 2006 4 次提交
  18. 01 2月, 2006 3 次提交
新手
引导
客服 返回
顶部