linux.git/drivers/pinctrl/intel, branch v5.5-rc2

pinctrl: lewisburg: Update pin list according to v1.1v6

2019-11-21T14:04:16+00:00

Version 1.1v6 of pin list has some changes in pin names for Intel Lewisburg.

Update the driver accordingly.

Note, it reveals the bug in the driver that misses two pins in GPP_L and
has rather two extra ones. That's why the ordering of some groups is changed.

Fixes: e480b745386e ("pinctrl: intel: Add Intel Lewisburg GPIO support")
Signed-off-by: Andy Shevchenko 
Link: https://lore.kernel.org/r/20191120133739.54332-1-andriy.shevchenko@linux.intel.com
Acked-by: Mika Westerberg 
Signed-off-by: Linus Walleij

pinctrl: cherryview: Missed type change to unsigned int

2019-11-07T09:12:10+00:00

We converted 'unsigned' type to be 'unsigned int' in the driver,
but there are couple of leftovers. So, finish the task now.

Signed-off-by: Andy Shevchenko

pinctrl: intel: Missed type change to unsigned int

2019-11-07T09:10:02+00:00

We converted 'unsigned' type to be 'unsigned int' in the driver,
but there are couple of leftovers. So, finish the task now.

Signed-off-by: Andy Shevchenko

pinctrl: intel: Add Intel Tiger Lake pin controller support

2019-10-30T14:05:18+00:00

This driver adds pinctrl/GPIO support for Intel Tiger Lake SoC. The
GPIO controller is based on the next generation GPIO hardware but still
compatible with the one supported by the Intel core pinctrl/GPIO driver.

Signed-off-by: Mika Westerberg 
Signed-off-by: Andy Shevchenko

pinctrl: intel: Use helper to restore register values on ->resume()

2019-10-30T14:05:18+00:00

We can restore only values that had been changed and do not spam kernel log
with unnecessary messages. Convert intel_gpio_update_pad_mode() to a helper
function that will be used across few callers.

Suggested-by: Mika Westerberg 
Signed-off-by: Andy Shevchenko 
Acked-by: Mika Westerberg

pinctrl: intel: Drop level from warning to debug in intel_restore_hostown()

2019-10-30T14:05:18+00:00

Since we didn't get any new reports from users about wrong settings
of pad ownership, there is no point to spam kernel log with it. Thus,
drop level from warning to debug.

Also, modify format to be in align with the rest restore helpers.

Signed-off-by: Andy Shevchenko 
Acked-by: Mika Westerberg

pinctrl: intel: Introduce intel_restore_intmask() helper

2019-10-30T14:05:18+00:00

Refactor restoring GPI_IE registers by using an introduced helper.

Signed-off-by: Andy Shevchenko 
Acked-by: Mika Westerberg

pinctrl: intel: Introduce intel_restore_hostown() helper

2019-10-30T14:05:18+00:00

Refactor restoring HOSTSW_OWN registers by using an introduced helper.

Signed-off-by: Andy Shevchenko 
Acked-by: Mika Westerberg

pinctrl: intel: Introduce intel_restore_padcfg() helper

2019-10-30T14:05:18+00:00

Deduplicate restoring PADCFGx registers by using a common helper.

Signed-off-by: Andy Shevchenko 
Acked-by: Mika Westerberg

pinctrl: cherryview: Allocate IRQ chip dynamic

2019-10-30T14:05:18+00:00

Keeping the IRQ chip definition static shares it with multiple instances
of the GPIO chip in the system. This is bad and now we get this warning
from GPIO library:

"detected irqchip that is shared with multiple gpiochips: please fix the driver."

Hence, move the IRQ chip definition from being driver static into the struct
intel_pinctrl. So a unique IRQ chip is used for each GPIO chip instance.

This patch is heavily based on the attachment to the bug by Christoph Marz.

BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=202543
Fixes: 6e08d6bbebeb ("pinctrl: Add Intel Cherryview/Braswell pin controller support")
Depends-on: 83b9dc11312f ("pinctrl: cherryview: Associate IRQ descriptors to irqdomain")
Signed-off-by: Andy Shevchenko 
Signed-off-by: Mika Westerberg