ACPI / property: Allow holes in reference properties

DT allows holes or empty phandles for references. This is used for example
in SPI subsystem where some chip selects are native and others are regular
GPIOs. In ACPI _DSD we currently do not support this but instead the
preceding reference consumes all following integer arguments.

For example we would like to support something like the below ASL fragment
for SPI:

  Package () {
      "cs-gpios",
      Package () {
          ^GPIO, 19, 0, 0, // GPIO CS0
          0,               // Native CS
          ^GPIO, 20, 0, 0, // GPIO CS1
      }
  }

The zero in the middle means "no entry" or NULL reference. To support this
we change acpi_data_get_property_reference() to take firmware node and
num_args as argument and rename it to __acpi_node_get_property_reference().
The function returns -ENOENT if the given index resolves to "no entry"
reference and -ENODATA when there are no more entries in the property.

We then add static inline wrapper acpi_node_get_property_reference() that
passes MAX_ACPI_REFERENCE_ARGS as num_args to support the existing
behaviour which some drivers have been relying on.

Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

path: root/REPORTING-BUGS

For reporting bugs send an email to the <netsniff-ng@googlegroups.com> list.

Alternatively, you can create an issue on our Github project:

  * https://github.com/netsniff-ng/netsniff-ng/issues

If you use Fedora or have a RHEL subscription, you can also report bugs to:

  * https://bugzilla.redhat.com/

If you use Debian Linux, we might also process / track bugs there:

  * http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=netsniff-ng

In any way, you'll get a reply from us. Please do not contact individual
developers directly in case of netsniff-ng issues or patches, but rather
always our mailing list. By this, you're not wasting time of a single
developer and increase your chances of getting a reply from us.

In general, we are also highly interested in how you use the toolkit, what
problems you are trying to solve and what kind of things you would like to have
improved. So feel free to drop us some feature requests as well.