MTD: Fix problems in SPI locking in mp25x.c driver.  Same problem probably in exists in several other drivers that derive from this this driver as well.

Based on the last PR, review all serial driver vector attachment.  Found one additional error and updated all relevant drivers to current interrupt parameter passing.

i.MX6: Fix a wrong parameter passed when calling irq_attach() in imx_serial.c

Approved-by: Gregory Nutt <gnutt@nuttx.org>

stm32_hrtim: add character driver

Approved-by: Gregory Nutt <gnutt@nuttx.org>

configs:  Add readme for B-L465E-IOT01A Development kit.  This port is currently under consideration (but may not actually happen)

stm32f103-minimum: Fix a small BUG when reading from output pin.  We need a different read_ops to read from output pin. This patch fixes the issue:

nsh> gpio -o 0 /dev/gpout1
Driver: /dev/gpout1
  Output pin:    Value=1
  Writing:       Value=0
  Verify:        Value=1

Now:

nsh> gpio -o 0 /dev/gpout1
Driver: /dev/gpout1
  Output pin:    Value=1
  Writing:       Value=0
  Verify:        Value=0

Whoops -- that #include <cxxabi.h> wasn't supposed to sneak in there. If present, it may already define a __cxxabiv1::__guard that we could use, but that file comes from libstdc++, and I don't think the NuttX buildroot-based toolchain would have that, which is why we need libxx in the first place.

Fix C++ __guard implementation for ARM.  The standard C++ ABI that most platforms follow defines __guard to be 64 bits.  The existing implementation of libxx_cxa_guard.cxx follows this.  However, the 32-bit ARM C++ ABI defines it as 32 bits instead, and changes the meaning slightly so only the lowest bit is used. This matters because GCC creates guard symbols without regards to what libxx_cxa_guard.cxx says.  So on ARM, gcc allocates 4 bytes, but __cxa_guard_release writes 8 bytes, zeroing out another unlucky variable nearby. Fix it by special-casing 32-bit ARM in libxx_cxa_guard.

configs/:  Back out many of the changes in two recent commits:  Too many changes from SPIDEV_WIRELESS to SPIDEV_CONTACTLESS.  Specifically NRF24L01 should still be SPIDEV_WIRELESS.

stm32f103-minimum: dd GPIO device driver example for STM32F103-Minimum.  This chang adds the initialization needed by stm32f103-minimum board to support the NuttX GPIO Subsystem.

STM32L4: Add STM32L475 pinmap.  Initial cut is just the the L476 pinmap with unsupported devices removed.

STM32L4:  Ad support for the STM32L475 family.  Incomplete -- still needs pinmap, rcc, otgfs, syscfg

Kinetis:Fixed waning for kinetis_mpudisable

Approved-by: Gregory Nutt <gnutt@nuttx.org>

  Missing header file added

Upstream kinetis usb

Approved-by: Gregory Nutt <gnutt@nuttx.org>

   Removed the notion of attached. The khci_usbattach is call early in
   the init either in board_initalize or in board_app_initalize. In
   either case it is always done prior to the the class register.
   Therefore the khci_usbattach call only set a flag, and that
   flag is only tested in the class register. The class register will
   enable the soft connect pull up.