The is the bulk of GPIO changes for the v4.16 kernel cycle.

Core changes:

- Disallow open drain and open source flags to be set
  simultaneously. This doesn't make electrical sense, and would
  the hardware actually respond to this setting, the result
  would be short circuit.

- ACPI GPIO has a new core infrastructure for handling quirks.
  The quirks are there to deal with broken ACPI tables centrally
  instead of pushing the work to individual drivers. In the world
  of BIOS writers, the ACPI tables are perfect. Until they find a
  mistake in it. When such a mistake is found, we can patch it
  with a quirk. It should never happen, the problem is that it
  happens. So we accomodate for it.

- Several documentation updates.

- Revert the patch setting up initial direction state from
  reading the device. This was causing bad things for drivers
  that can't read status on all its pins. It is only affecting
  debugfs information quality.

- Label descriptors with the device name if no explicit label is
  passed in.

- Pave the ground for transitioning SPI and regulators to use
  GPIO descriptors by implementing some quirks in the device tree
  GPIO parsing code.

New drivers:

- New driver for the Access PCIe IDIO 24 family.

Other:

- Major refactorings and improvements to the GPIO mockup driver
  used for test and verification.

- Moved the AXP209 driver over to pin control since it gained a
  pin control back-end. These patches will appear (with the same
  hashes) in the pin control pull request as well.

- Convert the onewire GPIO driver w1-gpio to use descriptors.
  This is merged here since the W1 maintainers send very few
  pull requests and he ACKed it.

- Start to clean up driver headers using <linux/gpio.h> to just
  use <linux/gpio/driver.h> as appropriate.
-----BEGIN PGP SIGNATURE-----

iQIcBAABAgAGBQJacIW6AAoJEEEQszewGV1z9b0P/jxWKaCAGFTTu/HZQ79RBAFq
w33nIazzoh+88sN7A9xKexpr4ibOxiCvOwkTtrUBNaxGGy5fslj4+OY5BzunEfBK
1vYxyEqtenvvZK03pOd6CSfHKV+vD5ngnVHGdtGzRvtmDDiSgtzqyEyUhQcXM+l7
PrEh6qrd4TBZezlVR8kn5eqcmclkCBVSQCuLSq+ThMmCKRZuOdf1Im3D6eBzh1/N
P81HdcglqbSsfUl1RcFiHs9Z+KcZOq83CNl2Ej1LePK2JBZbmkx9dR+WSJmV1u4P
6wvzFcQDhfGEiiteg2BS5c+o6aAyShpuRNut+2MLre8icmdfpqUEqFotHbfQjW5y
sqaejGsJ5aHcRBq7UUM+F9s1R0iN3tlafi3L0WEhl0Tn5huRQq3Uqcw6e5l+XrWd
0h+b5PbKJZO/iqzRhSl+rhc0V2CFDJOCwvY+JX6356fvrcF0T6LhvKfDYtKU3Iyb
HB0RG1OcYe228f96azvafCkFyBIYX9mqHBvOXpQQgrZQYXfN1rupLvpOhxC+Wbvn
nsGE2bdD6HA1bytTbkxbL+QWP7faHf5YVcZpaN7UWbO3sOzL46fj8eHwHUim95Tr
pR5kDZRhZd8+9SCNZ/ttpaEbis9MOqS/3Mlxrj4GXtfFFmR53hjFy2bG/Z7R2RB0
MlSEJRc8iDIs+1j3D2RR
=k5nL
-----END PGP SIGNATURE-----
gpio: Timestamp events in hardirq handler

Add a hardirq handler to the GPIO userspace event loop, making
sure to pick up the timestamp there, as close as possible in time
relative to the actual event causing the interrupt.

Tested with a simple pushbutton GPIO on ux500 and seems to work
fine.

Cc: Bartosz Golaszewski <brgl@bgdev.pl>
Reviewed-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Reported-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
1 file changed