Commit 9bd59157 authored by Andy Shevchenko's avatar Andy Shevchenko

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: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
parent d4b41f8b
...@@ -1281,6 +1281,9 @@ static int intel_pinctrl_add_padgroups(struct intel_pinctrl *pctrl, ...@@ -1281,6 +1281,9 @@ static int intel_pinctrl_add_padgroups(struct intel_pinctrl *pctrl,
case INTEL_GPIO_BASE_MATCH: case INTEL_GPIO_BASE_MATCH:
gpps[i].gpio_base = gpps[i].base; gpps[i].gpio_base = gpps[i].base;
break; break;
case INTEL_GPIO_BASE_ZERO:
gpps[i].gpio_base = 0;
break;
case INTEL_GPIO_BASE_NOMAP: case INTEL_GPIO_BASE_NOMAP:
default: default:
break; break;
......
...@@ -70,10 +70,12 @@ struct intel_padgroup { ...@@ -70,10 +70,12 @@ struct intel_padgroup {
/** /**
* enum - Special treatment for GPIO base in pad group * enum - Special treatment for GPIO base in pad group
* *
* @INTEL_GPIO_BASE_ZERO: force GPIO base to be 0
* @INTEL_GPIO_BASE_NOMAP: no GPIO mapping should be created * @INTEL_GPIO_BASE_NOMAP: no GPIO mapping should be created
* @INTEL_GPIO_BASE_MATCH: matches with starting pin number * @INTEL_GPIO_BASE_MATCH: matches with starting pin number
*/ */
enum { enum {
INTEL_GPIO_BASE_ZERO = -2,
INTEL_GPIO_BASE_NOMAP = -1, INTEL_GPIO_BASE_NOMAP = -1,
INTEL_GPIO_BASE_MATCH = 0, INTEL_GPIO_BASE_MATCH = 0,
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment