1. 04 12月, 2013 1 次提交
    • M
      VME: Provide access to VME bus enumeration and fix vme_user match function · 978f47d6
      Martyn Welch 提交于
      The match function for vme_user is completely wrong. It will blindly bind
      against the first VME slot on each bus (at this point that would be just the
      first bus as the driver can only handle one bus).
      
      The original intention (before some major subsystem changes) was that the
      driver bind against the slot to which the bridge was attached in the VME
      system and to the bus(es) provided via the "bus" module parameter.
      
      To do this cleanly (i.e. without poking arround in the subsystems internal
      stuctures) a functionality has been added to provide access to the bus
      enumeration.
      Signed-off-by: NMartyn Welch <martyn.welch@ge.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      978f47d6
  2. 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
  3. 10 2月, 2012 1 次提交
  4. 02 12月, 2011 1 次提交
  5. 27 11月, 2011 1 次提交
  6. 18 10月, 2011 3 次提交
    • M
      staging: vme: get rid of struct vme_device_id and slots · a916a391
      Manohar Vanga 提交于
      Previously, the device-driver matching mechanism depended on the
      vme_device_id structure due to the need for a bind table per driver.
      This method of matching is no longer used so this patch merges the
      fields of struct vme_device_id into struct vme_dev. Since this also
      renders the slot field meaningless, it has also been removed in this
      patch.
      Signed-off-by: NManohar Vanga <manohar.vanga@cern.ch>
      Cc: Martyn Welch <martyn.welch@ge.com>
      Reviewed-by: NEmilio G. Cota <cota@braap.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a916a391
    • M
      staging: vme: make match() driver specific to improve non-VME64x support · 5d6abf37
      Manohar Vanga 提交于
      For jumper based boards (non VME64x), there is no mechanism
      for detecting the card that is plugged into a specific slot. This
      leads to issues in non-autodiscovery crates/cards when a card is
      plugged into a slot that is "claimed" by a different driver. In
      reality, there is no problem, but the driver rejects such a
      configuration due to its dependence on the concept of slots.
      
      This patch makes the concept of slots less critical and pushes the
      driver match() to individual drivers (similar to what happens in the
      ISA bus in driver/base/isa.c). This allows drivers to register the
      number of devices that they expect without any restrictions. Devices
      in this new model are now formatted as $driver_name-$bus_id.$device_id
      (as compared to the earlier vme-$bus_id.$slot_number).
      
      This model also makes the device model more logical as devices
      are only registered when they actually exist whereas earlier,
      a set of devices were being created automatically regardless of
      them actually being there.
      
      Another change introduced in this patch is that devices are now created
      within the VME driver structure rather than in the VME bridge structure.
      This way, things don't go haywire if the bridge driver is removed while
      a driver is using it.
      Signed-off-by: NManohar Vanga <manohar.vanga@cern.ch>
      Cc: Martyn Welch <martyn.welch@ge.com>
      Reviewed-by: NEmilio G. Cota <cota@braap.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      5d6abf37
    • M
      staging: vme: add struct vme_dev for VME devices · 8f966dc4
      Manohar Vanga 提交于
      Instead of using a vanilla 'struct device' for VME devices, add new
      'struct vme_dev'. Modifications have been made to the VME framework
      API as well as all in-tree VME drivers.
      
      The new vme_dev structure has the following advantages from the
      current model used by the driver:
      
          * Driver functions (probe, remove) now receive a VME device
            instead of a pointer to the bridge device (cleaner design)
          * It's easier to differenciate API calls as bridge-based or
            device-based (ie. cleaner interface).
      Signed-off-by: NManohar Vanga <manohar.vanga@cern.ch>
      Cc: Martyn Welch <martyn.welch@ge.com>
      Reviewed-by: NEmilio G. Cota <cota@braap.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      8f966dc4
  7. 29 6月, 2011 1 次提交
  8. 04 3月, 2010 2 次提交
  9. 12 12月, 2009 2 次提交
  10. 16 9月, 2009 3 次提交