1. 25 7月, 2013 1 次提交
  2. 17 7月, 2013 1 次提交
    • G
      staging: csr: remove driver · ade7615d
      Greg Kroah-Hartman 提交于
      This driver is not being updated as the specifications are not able to
      be gotten from CSR or anyone else.  Without those, getting this driver
      into proper mergable shape is going to be impossible.  So remove the
      driver from the tree.
      
      If the specifications ever become available, this patch can be reverted
      and the driver fixed up properly.
      Reported-by: NLidza Louina <lidza.louina@gmail.com>
      Cc: Veli-Pekka Peltola <veli-pekka.peltola@bluegiga.com>
      Cc: Mikko Virkkilä <mikko.virkkila@bluegiga.com>
      Cc: Lauri Hintsala <Lauri.Hintsala@bluegiga.com>
      Cc: Riku Mettälä <riku.mettala@bluegiga.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ade7615d
  3. 04 6月, 2013 1 次提交
    • A
      staging: MIPS: add Octeon USB HCD support · b164935b
      Aaro Koskinen 提交于
      Add support for Octeon USB HCD. Tested on EdgeRouter Lite with USB
      mass storage.
      
      The driver has been extracted from GPL sources of EdgeRouter Lite firmware
      (based on Linux 2.6.32.13). Some minor fixes and cleanups have been done
      to make it work with 3.10-rc3.
      
      $ uname -a
      Linux (none) 3.10.0-rc3-edge-00005-g86cb5bc #41 SMP PREEMPT Sat Jun 1 20:41:46 EEST 2013 mips64 GNU/Linux
      $ modprobe octeon-usb
      [   37.971683] octeon_usb: module is from the staging directory, the quality is unknown, you have been warned.
      [   37.983649] OcteonUSB: Detected 1 ports
      [   37.999360] OcteonUSB OcteonUSB.0: Octeon Host Controller
      [   38.004847] OcteonUSB OcteonUSB.0: new USB bus registered, assigned bus number 1
      [   38.012332] OcteonUSB OcteonUSB.0: irq 122, io mem 0x00000000
      [   38.019970] hub 1-0:1.0: USB hub found
      [   38.023851] hub 1-0:1.0: 1 port detected
      [   38.028101] OcteonUSB: Registered HCD for port 0 on irq 122
      [   38.391443] usb 1-1: new high-speed USB device number 2 using OcteonUSB
      [   38.586922] usb-storage 1-1:1.0: USB Mass Storage device detected
      [   38.597375] scsi0 : usb-storage 1-1:1.0
      [   39.604111] scsi 0:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 4
      [   39.619113] sd 0:0:0:0: [sda] 7579008 512-byte logical blocks: (3.88 GB/3.61 GiB)
      [   39.630696] sd 0:0:0:0: [sda] Write Protect is off
      [   39.635945] sd 0:0:0:0: [sda] No Caching mode page present
      [   39.641464] sd 0:0:0:0: [sda] Assuming drive cache: write through
      [   39.651341] sd 0:0:0:0: [sda] No Caching mode page present
      [   39.656917] sd 0:0:0:0: [sda] Assuming drive cache: write through
      [   39.664296]  sda: sda1 sda2
      [   39.675574] sd 0:0:0:0: [sda] No Caching mode page present
      [   39.681093] sd 0:0:0:0: [sda] Assuming drive cache: write through
      [   39.687223] sd 0:0:0:0: [sda] Attached SCSI removable disk
      Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
      Cc: David Daney <ddaney.cavm@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b164935b
  4. 28 5月, 2013 1 次提交
    • E
      thermal: introduce TI SoC thermal driver · eb982001
      Eduardo Valentin 提交于
      This patch moves the ti-soc-thermal driver out of
      the staging tree to the thermal tree.
      
      Cc: Grant Likely <grant.likely@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Rob Landley <rob@landley.net>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Zhang Rui <rui.zhang@intel.com>
      Cc: Eduardo Valentin <eduardo.valentin@ti.com>
      Cc: J Keerthy <j-keerthy@ti.com>
      Cc: Radhesh Fadnis <radhesh.fadnis@ti.com>
      Cc: Cyril Roelandt <tipecaml@gmail.com>
      Cc: devicetree-discuss@lists.ozlabs.org
      Cc: linux-doc@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Cc: devel@driverdev.osuosl.org
      Cc: linux-pm@vger.kernel.org
      Signed-off-by: NEduardo Valentin <eduardo.valentin@ti.com>
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      eb982001
  5. 17 5月, 2013 2 次提交
  6. 15 5月, 2013 1 次提交
  7. 20 4月, 2013 1 次提交
    • D
      staging: net: remove pc300 driver · f33cb17d
      Daniel Borkmann 提交于
      To quote the TODO from staging/net/:
      
        PC300:
      
        The driver is very broken and cannot work with the current TTY
        layer. It is inevitable to convert it to the new TTY API. If no
        one steps in to adopt the driver, it will be removed in the 3.7
        release.
      
      Nothing has changed since more than _one_ year on this driver, thus
      just remove it since we already moved past 3.7. If somebody steps
      up and does a whole rework, he/she, of course, is free to resubmit
      it. Since this is the only one in the net directory, we can remove
      it as well.
      Signed-off-by: NDaniel Borkmann <dborkman@redhat.com>
      Cc: Jiri Slaby <jslaby@suse.cz>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f33cb17d
  8. 26 3月, 2013 1 次提交
  9. 15 3月, 2013 2 次提交
  10. 12 3月, 2013 2 次提交
  11. 17 2月, 2013 1 次提交
    • R
      drm/omap: move out of staging · 8bb0daff
      Rob Clark 提交于
      Now that the omapdss interface has been reworked so that omapdrm can use
      dispc directly, we have been able to fix the remaining functional kms
      issues with omapdrm.  And in the mean time the PM sequencing and many
      other of that open issues have been solved.  So I think it makes sense
      to finally move omapdrm out of staging.
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      8bb0daff
  12. 25 1月, 2013 1 次提交
  13. 19 1月, 2013 2 次提交
  14. 16 1月, 2013 1 次提交
  15. 29 11月, 2012 1 次提交
  16. 17 11月, 2012 1 次提交
  17. 16 11月, 2012 1 次提交
  18. 14 11月, 2012 1 次提交
  19. 27 10月, 2012 2 次提交
  20. 22 9月, 2012 2 次提交
  21. 18 9月, 2012 1 次提交
  22. 08 9月, 2012 1 次提交
  23. 06 9月, 2012 2 次提交
    • D
      staging: ramster: move to new zcache2 codebase · faca2ef7
      Dan Magenheimer 提交于
      [V2: rebased to apply to 20120905 staging-next, no other changes]
      
      The original zcache in staging is a "demo" version, and this is a massive
      rewrite.  This was intended to result in a merged zcache and ramster, but
      that option has been blocked so, to continue forward progress on ramster
      and future related projects, only ramster moves to the new codebase.
      To differentiate between the old demo zcache and the rewrite, we refer
      to the latter as zcache2, config'd as CONFIG_ZCACHE2.  Zcache and zcache2
      cannot be built in the same kernel, so CONFIG_ZCACHE2 implies !CONFIG_ZCACHE.
      
      This developer still has hope that zcache and zcache2 will be merged
      into one codebase.  Until then, zcache2 can be considered a one-node
      version of ramster.
      
      No history of changes was recorded during the zcache2 rewrite and recreating
      a sane one would be a Sisyphean task but, since ramster is still in
      staging and has been unchanged since it was merged, presumably this
      is acceptable.
      
      This commit also provides the hooks in zcache2 for ramster, but all
      ramster-specific code is provided in a separate commit.
      
      Some of the highlights of this rewritten codebase for zcache2:
      (Note: If you are not familiar with the tmem terminology, you can review
      it here: http://lwn.net/Articles/454795/ )
       1. Merge of "demo" zcache and the v1.1 version of zcache in ramster.  Zcache
          and ramster had a great deal of duplicate code which is now merged.
          In essence, zcache2 *is* ramster but with no remote machine available,
          but !CONFIG_RAMSTER will avoid compiling lots of ramster-specific code.
       2. Allocator.  Previously, persistent pools used zsmalloc and ephemeral pools
          used zbud.  Now a completely rewritten zbud is used for both.  Notably
          this zbud maintains all persistent (frontswap) and ephemeral (cleancache)
          pageframes in separate queues in LRU order.
       3. Interaction with page allocator.  Zbud does no page allocation/freeing,
          it is done entirely in zcache2 where it can be tracked more effectively.
       4. Better pre-allocation.  Previously, on put, if a new pageframe could not be
          pre-allocated, the put would fail, even if the allocator had plenty of
          partial pages where the data could be stored; this is now fixed.
       5. Ouroboros ("eating its own tail") allocation.  If no pageframe can be
          allocated AND no partial pages are available, the least-recently-used
          ephemeral pageframe is reclaimed immediately (including flushing tmem
          pointers to it) and re-used.  This ensures that most-recently-used
          cleancache pages are more likely to be retained than LRU pages and also
          that, as in the core mm subsystem, anonymous pages have a higher priority
          than clean page cache pages.
       6. Zcache and zbud now use debugfs instead of sysfs.  Ramster uses debugfs
          where possible and sysfs where necessary.  (Some ramster configuration
          is done from userspace so some sysfs is necessary.)
       7. Modularization.  As some have observed, the monolithic zcache-main.c code
          included zbud code, which has now been separated into its own code module.
          Much ramster-specific code in the old ramster zcache-main.c has also been
          moved into ramster.c so that it does not get compiled with !CONFIG_RAMSTER.
       8. Rebased to 3.5.
      
      This new codebase also provides hooks for several future new features:
       A. WasActive patch, requires some mm/frontswap changes previously posted.
          A new version of this patch will be provided separately.
          See ifdef __PG_WAS_ACTIVE
       B. Exclusive gets.  It seems tmem _can_ support exclusive gets with a
          minor change to both zcache2 and a small backwards-compatible change
          to frontswap.c.  Explanation and frontswap patch will be provided
          separately.  See ifdef FRONTSWAP_HAS_EXCLUSIVE_GETS
       C. Ouroboros writeback.  Since persistent (frontswap) pages may now also be
          reclaimed in LRU order, the foundation is in place to properly writeback
          these pages back into the swap cache and then the swap disk.  This is still
          under development and requires some other mm changes which are prototyped.
          See ifdef FRONTSWAP_HAS_UNUSE.
      
      A new feature that desperately needs attention (if someone is looking for
      a way to contribute) is kernel module support.  A preliminary version of
      a patch was posted by Erlangen University and needs to be integrated and
      tested for zcache2 and brought up to kernel standards.
      
      If anybody is interested on helping out with any of these, let me know!
      Acked-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Signed-off-by: NDan Magenheimer <dan.magenheimer@oracle.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      faca2ef7
    • D
      staging: ramster: remove old driver to prep for new base · c857ce16
      Dan Magenheimer 提交于
      [V2: rebased to apply to 20120905 staging-next, no other changes]
      
      To prep for moving the ramster codebase on top of the new
      redesigned zcache2 codebase, we remove ramster (as well
      as its contained diverged v1.1 version of zcache) entirely.
      Acked-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Signed-off-by: NDan Magenheimer <dan.magenheimer@oracle.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c857ce16
  24. 17 7月, 2012 1 次提交
  25. 20 6月, 2012 1 次提交
    • G
      Staging: add CSR Wifi "os helper" module · 15a4bc17
      Greg Kroah-Hartman 提交于
      This module is used by the CSR wifi driver to "abstract" away the
      OS-specific parts of core functions.  It will be eventually deleted, but
      for now is needed as the CSR driver relies on it.
      
      Cc: Mikko Virkkilä <mikko.virkkila@bluegiga.com>
      Cc: Lauri Hintsala <Lauri.Hintsala@bluegiga.com>
      Cc: Riku Mettälä <riku.mettala@bluegiga.com>
      Cc: Veli-Pekka Peltola <veli-pekka.peltola@bluegiga.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      15a4bc17
  26. 13 6月, 2012 1 次提交
  27. 16 5月, 2012 1 次提交
    • M
      staging: usb: gadget: Add Configurable Composite Gadget driver · 332bb43f
      Mike Lockwood 提交于
      The Configurable Gadget driver is a composite driver that allows
      userspace to change at runtime the list of functions enabled in
      its configuration and to configure these functions. It supports
      multiple functions: acm, rndis, and mass storage.
      
      It is usually controlled by a daemon that changes the configuration
      based on user settings. For example, rndis is enabled when the user
      enables sharing the phone data connection.
      
      As an example on how to use it, the following shell commands will
      make the gadget disconnect from the host and make it be re-enumerated
      as a composite with 1 rndis and 2 acm interfaces, and a different
      product id:
      
      echo 0       > /sys/class/ccg_usb/ccg0/enable
      echo rndis,acm > /sys/class/ccg_usb/ccg0/functions
      echo 2       > /sys/class/ccg_usb/ccg0/f_acm/instances
      echo -n 0x2d01 > /sys/module/g_ccg/parameters/idProduct
      echo 1       > /sys/class/ccg_usb/ccg0/enable
      
      The driver requires a gadget controller that supports software
      control of the D+ pullup and the controller driver must support
      disabling the pullup during composite_bind.
      Signed-off-by: NMike Lockwood <lockwood@android.com>
      Signed-off-by: NBenoit Goby <benoit@android.com>
      	[import from android.c, implement review comments, remove adb,mtp,ptp,accessory]
      Signed-off-by: NAndrzej Pietrasiewicz <andrzej.p@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      332bb43f
  28. 15 5月, 2012 2 次提交
  29. 11 5月, 2012 1 次提交
  30. 10 5月, 2012 1 次提交
  31. 02 5月, 2012 1 次提交
  32. 27 4月, 2012 1 次提交
    • G
      Staging: VME: move VME drivers out of staging · db3b9e99
      Greg Kroah-Hartman 提交于
      This moves the VME core, VME board drivers, and VME bridge drivers out
      of the drivers/staging/vme/ area to drivers/vme/.
      
      The VME device drivers have not moved out yet due to some API questions
      they are still working through, that should happen soon, hopefully.
      
      Cc: Martyn Welch <martyn.welch@ge.com>
      Cc: Manohar Vanga <manohar.vanga@cern.ch>
      Cc: Vincent Bossier <vincent.bossier@gmail.com>
      Cc: "Emilio G. Cota" <cota@braap.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      db3b9e99