1. 17 7月, 2012 1 次提交
  2. 25 6月, 2012 1 次提交
    • K
      usb: gadget: Fix g_ether interface link status · 31bde1ce
      Kevin Cernekee 提交于
      A "usb0" interface that has never been connected to a host has an unknown
      operstate, and therefore the IFF_RUNNING flag is (incorrectly) asserted
      when queried by ifconfig, ifplugd, etc.  This is a result of calling
      netif_carrier_off() too early in the probe function; it should be called
      after register_netdev().
      
      Similar problems have been fixed in many other drivers, e.g.:
      
          e826eafa (bonding: Call netif_carrier_off after register_netdevice)
          0d672e9f (drivers/net: Call netif_carrier_off at the end of the probe)
          6a3c869a (cxgb4: fix reported state of interfaces without link)
      
      Fix is to move netif_carrier_off() to the end of the function.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NKevin Cernekee <cernekee@gmail.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      31bde1ce
  3. 11 5月, 2012 1 次提交
  4. 10 9月, 2011 1 次提交
    • K
      usb gadget: clean up FSF boilerplate text · 28c9fc68
      Klaus Schwarzkopf 提交于
      remove the following two paragraphs as they are not needed:
      
      This program is distributed in the hope that it will be useful, but
      WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
      FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public
      License for more details.
      
      You should have received a copy of the GNU General Public License along with
      this program; if not, write to the Free Software Foundation, Inc.,59
      Temple Place - Suite 330, Boston, MA  02111-1307, USA.
      Signed-off-by: NKlaus Schwarzkopf <schwarzkopf@sensortherm.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      28c9fc68
  5. 08 7月, 2011 1 次提交
  6. 29 6月, 2011 1 次提交
  7. 03 3月, 2011 1 次提交
  8. 24 12月, 2010 1 次提交
    • T
      usb: don't use flush_scheduled_work() · 569ff2de
      Tejun Heo 提交于
      flush_scheduled_work() is being deprecated.  Directly flush or cancel
      work items instead.
      
      * u_ether, isp1301_omap, speedtch conversions are straight-forward.
      
      * ochi-hcd should only flush when quirk_nec() is true as otherwise the
        work wouldn't have been initialized.
      
      * In oti6858, cancel_delayed_work() + flush_scheduled_work() ->
        cancel_delayed_work_sync().
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Cc: Duncan Sands <duncan.sands@free.fr>
      Cc: linux-usb@vger.kernel.org
      569ff2de
  9. 11 12月, 2010 1 次提交
  10. 02 11月, 2010 1 次提交
  11. 29 10月, 2010 1 次提交
  12. 11 8月, 2010 1 次提交
  13. 21 5月, 2010 1 次提交
  14. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  15. 03 3月, 2010 1 次提交
  16. 24 9月, 2009 1 次提交
  17. 23 9月, 2009 1 次提交
    • B
      USB: gadget: Add EEM gadget driver · 9b39e9dd
      Brian Niebuhr 提交于
      This patch adds a CDC EEM ethernet gadget driver.  CDC EEM is a newer
      USB ethernet specification that uses a simpler interface than the older
      CDC ECM.  This makes CDC EEM usable by a wider set of USB hardware.
      By default the ethernet gadget will still use CDC ECM/Subset, but kernel
      configuration and/or a module parameter will allow alternative use of
      the CDC EEM protocol.
      
      Changes since last version:
      	- Brought in missing RNDIS changes that caused compile error
      	- Modified 'sentinel CRC' checking to match EEM host driver
      Signed-off-by: NBrian Niebuhr <bniebuhr@efjohnson.com>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      9b39e9dd
  18. 02 9月, 2009 1 次提交
  19. 01 9月, 2009 1 次提交
  20. 06 7月, 2009 1 次提交
  21. 13 6月, 2009 1 次提交
  22. 18 4月, 2009 1 次提交
  23. 08 1月, 2009 1 次提交
  24. 20 11月, 2008 1 次提交
  25. 28 10月, 2008 1 次提交
  26. 18 10月, 2008 1 次提交
    • D
      usb gadget: cdc ethernet notification bugfix · 29bac7b7
      David Brownell 提交于
      Bugfix for the new CDC Ethernet code:  as part of activating the
      network interface's USB link, make sure its link management code
      knows whether the interface is open or not.
      
      Without this fix, the link won't work right when it's brought up
      before the link is active ... because the initial notification it
      sends will have the wrong link state (down, not up).  Makes it
      hard to bridge these links (on the host side), among other things.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: stable <stable@kernel.org> [2.6.27]
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      29bac7b7
  27. 17 10月, 2008 1 次提交
  28. 26 7月, 2008 1 次提交
  29. 22 7月, 2008 1 次提交
    • D
      usb ethernet gadget: split out network core · 2b3d942c
      David Brownell 提交于
      Abstract the peripheral side Ethernet-over-USB link layer code from
      the all-in-one Ethernet gadget driver into a component that can be
      called by various functions, so the various flavors can be split
      apart and selectively reused.
      
      A notable difference from the approach taken with the serial link
      layer code (beyond talking to NET not TTY) is that because of the
      initialization requirements, this only supports one network link.
      (And one set of Ethernet link addresses.)
      
      That is, each configuration may have only one instance of a network
      function.  This doesn't change behavior; the current code has that
      same restriction.  If you want multiple logical links, that can
      easily be done using network layer tools.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      2b3d942c