]> git.baikalelectronics.ru Git - kernel.git/commit
drm/i915/bxt: use NULL for GPIO connection ID
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Thu, 17 Aug 2017 10:55:41 +0000 (13:55 +0300)
committerJani Nikula <jani.nikula@intel.com>
Fri, 18 Aug 2017 12:57:51 +0000 (15:57 +0300)
commitcd55a1fbd21a820b7dd85a208b3170aa0b06adfa
tree1f2e853bf1abd2950824276e22b286089e3b9adf
parent636918f130296fac1ab195ba087688f91bd627f8
drm/i915/bxt: use NULL for GPIO connection ID

The commit 213e08ad60ba
("drm/i915/bxt: add bxt dsi gpio element support")
enables GPIO support for Broxton based platforms.

While using that API we might get into troubles in the future, because
we can't rely on label name in the driver since vendor firmware might
provide any GPIO pin there, e.g. "reset", and even mark it in _DSD (in
which case the request will fail).

To avoid inconsistency and potential issues we have two options:
a) generate GPIO ACPI mapping table and supply it via
   acpi_dev_add_driver_gpios(), or
b) just pass NULL as connection ID.

The b) approach is much simpler and would work since the driver relies
on GPIO indices only. Moreover, the _CRS fallback mechanism, when
requesting GPIO, has been made stricter, and supplying non-NULL
connection ID when neither _DSD, nor GPIO ACPI mapping is present, is
making request fail.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101921
Fixes: f10e4bf6632b ("gpio: acpi: Even more tighten up ACPI GPIO lookups")
Cc: Mika Kahola <mika.kahola@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Tested-by: Mika Kahola <mika.kahola@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20170817105541.63914-1-andriy.shevchenko@linux.intel.com
drivers/gpu/drm/i915/intel_dsi_vbt.c