Searched hist:"9 bd59157e16c64b45da5315f5b49b659fe51984b" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/pinctrl/intel/ |
| H A D | pinctrl-intel.h | diff 9bd59157e16c64b45da5315f5b49b659fe51984b Mon Apr 13 06:18:24 CDT 2020 Andy Shevchenko <andriy.shevchenko@linux.intel.com> pinctrl: intel: Introduce new flag to force GPIO base to be 0
In some cases not the first group would like to have GPIO base to be 0.
It's not possible right now due to 0 has special meaning already. Thus,
introduce a new flag to allow drivers to force GPIO base to be 0 on
a certain group. It's assumed that it can be only one group per device
with such flag enabled.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
|
| H A D | pinctrl-intel.c | diff 9bd59157e16c64b45da5315f5b49b659fe51984b Mon Apr 13 06:18:24 CDT 2020 Andy Shevchenko <andriy.shevchenko@linux.intel.com> pinctrl: intel: Introduce new flag to force GPIO base to be 0
In some cases not the first group would like to have GPIO base to be 0.
It's not possible right now due to 0 has special meaning already. Thus,
introduce a new flag to allow drivers to force GPIO base to be 0 on
a certain group. It's assumed that it can be only one group per device
with such flag enabled.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
|