Add locking to mlx(4) to make it MPSAFE along with some other fixes:
- Use callout(9) rather than timeout(9).
- Add a mutex as an I/O lock that protects the adapter and is used
  for the I/O path.
- Add an sx lock as a configuration lock that protects the relationship
  of configured volumes.
- Freeze the request queue when a DMA load is deferred with EINPROGRESS
  and unfreeze the queue when the DMA callback is invoked.
- Explicitly poll the hardware while waiting to submit a command to
  allow completed commands to free up slots in the command ring.
- Remove driver-wide 'initted' variable from mlx_*_fw_handshake() routines.
  That state should be per-controller instead.  Add it as an argument
  since the first caller knows when it is the first caller.
- Remove explicit bus_space tag/handle and use bus_*() rather than
  bus_space_*().
- Move duplicated PCI device ID probing into a  mlx_pci_match() routine.
- Don't check for PCIM_CMD_MEMEN (the PCI bus will enable that when
  allocating the resource) and use pci_enable_busmaster() rather than
  manipulating the register directly.

Tested by:	no one despite multiple requests (hope it works)


git-svn-id: svn://svn.freebsd.org/base/head@240608 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Implement support for USB Audio v2.0. Remove some redundant
USB audio v1.0 debug data, hence userspace tools like lsusb
exist to show this information properly.


git-svn-id: svn://svn.freebsd.org/base/head@240609 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Add UQ_UMS_IGNORE quirk.
Wrap two long lines.
Some minor spelling correction.

PR:	usb/171721


git-svn-id: svn://svn.freebsd.org/base/head@240615 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
This is the first of several commits which will add NVM Express (NVMe)
support to FreeBSD.  A full description of the overall functionality
being added is below.  nvmexpress.org defines NVM Express as "an optimized
register interface, command set and feature set fo PCI Express (PCIe)-based
Solid-State Drives (SSDs)."

This commit adds nvme(4) and nvd(4) driver source code and Makefiles
to the tree.

Full NVMe functionality description:
Add nvme(4) and nvd(4) drivers and nvmecontrol(8) for NVM Express (NVMe)
device support.

There will continue to be ongoing work on NVM Express support, but there
is more than enough to allow for evaluation of pre-production NVM Express
devices as well as soliciting feedback.  Questions and feedback are welcome.

nvme(4) implements NVMe hardware abstraction and is a provider of NVMe
namespaces.  The closest equivalent of an NVMe namespace is a SCSI LUN.
nvd(4) is an NVMe consumer, surfacing NVMe namespaces as GEOM disks.
nvmecontrol(8) is used for NVMe configuration and management.

The following are currently supported:
nvme(4)
- full mandatory NVM command set support
- per-CPU IO queues (enabled by default but configurable)
- per-queue sysctls for statistics and full command/completion queue
     dumps for debugging
- registration API for NVMe namespace consumers
- I/O error handling (except for timeoutsee below)
- compilation switches for support back to stable-7

nvd(4)
- BIO_DELETE and BIO_FLUSH (if supported by controller)
- proper BIO_ORDERED handling

nvmecontrol(8)
- devlist: list NVMe controllers and their namespaces
- identify: display controller or namespace identify data in
      human-readable or hex format
- perftest: quick and dirty performance test to measure raw
      performance of NVMe device without userspace/physio/GEOM
      overhead

The following are still work in progress and will be completed over the
next 3-6 months in rough priority order:
- complete man pages
- firmware download and activation
- asynchronous error requests
- command timeout error handling
- controller resets
- nvmecontrol(8) log page retrieval

This has been primarily tested on amd64, with light testing on i386.  I
would be happy to provide assistance to anyone interested in porting
this to other architectures, but am not currently planning to do this
work myself.  Big-endian and dmamap sync for command/completion queues
are the main areas that would need to be addressed.

The nvme(4) driver currently has references to Chatham, which is an
Intel-developed prototype board which is not fully spec compliant.
These references will all be removed over time.

Sponsored by:        Intel
Contributions from:  Joe Golio/EMC <joseph dot golio at emc dot com>


git-svn-id: svn://svn.freebsd.org/base/head@240616 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Integrate nvme(4) and nvd(4) into the amd64 and i386 builds.

Sponsored by:	Intel


git-svn-id: svn://svn.freebsd.org/base/head@240618 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Add nvme(4) and nvd(4) Makefiles to the tree.

Noticed by:	pluknet
Pointy-hat to:  jimharris


git-svn-id: svn://svn.freebsd.org/base/head@240619 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Add nvmecontrol(8) source code and beginnings of a man page to the tree.

Sponsored by:		Intel
Contributions from:	Joe Golio/EMC <joseph dot golio at emc dot com>


git-svn-id: svn://svn.freebsd.org/base/head@240620 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Integrate nvmecontrol(8) into the amd64 and i386 builds.

This includes adding NVMe header files to /usr/include/dev/nvme.

Sponsored by:  Intel


git-svn-id: svn://svn.freebsd.org/base/head@240621 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
yes(1) actually comes from V7.

Submitted by:	Simon Gerraty <sjg@juniper.net>


git-svn-id: svn://svn.freebsd.org/base/head@240622 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Rename AH_MIMO_MAX_CHAINS to AH_MAX_CHAINS, for compatibility with
internal atheros HAL code.


git-svn-id: svn://svn.freebsd.org/base/head@240623 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Merge remote-tracking branch 'upstream/master'