Skip to contentSkip to conversation

intel-pinctrl for 5.9-1

GIT PULL Andy Shevchenko 3 participants 4 messages Jul 21, 2020 – Jul 22, 2020 GPIO

lore
Share & tools
lore
#0 lore raw

Hi Linus,

Intel pin controller driver for v5.9. No conflicts found, no build / other issues. Nevertheless it contains one fix that has been already applied during v5.8 cycle.

Thanks,

With Best Regards,
Andy Shevchenko

The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:

Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)

are available in the Git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v5.9-1

for you to fetch changes up to b4f2fcb534875e2e57c96a0358267f2109d68004:

pinctrl: intel: Add Intel Emmitsburg pin controller support (2020-07-21 11:44:21 +0300)

----------------------------------------------------------------
intel-pinctrl for v5.9-1

* New driver for Emmitsburg
* New driver for Tiger Lake-H
* Part 3 of Cherryview driver clean up
* Fix a glitch on Baytrail platforms

The following is an automated git shortlog grouped by driver:

ARM/orion/gpio:
- Make use of for_each_requested_gpio()

at91:
- Make use of for_each_requested_gpio()

baytrail:

 -  Use fallthrough pseudo-keyword
 -  Fix pin being driven low for a while on gpiod_get(..., GPIOD_OUT_HIGH)
 -  Drop no-op ACPI_PTR() call

cherryview:

 -  Re-use data structures from pinctrl-intel.h (part 3)
 -  Convert chv_writel() to use chv_padreg()
 -  Introduce helpers to IO with common registers
 -  Introduce chv_readl() helper

gpio:
- xra1403: Make use of for_each_requested_gpio()
- mvebu: Make use of for_each_requested_gpio()

gpiolib:
- Introduce for_each_requested_gpio_in_range() macro

intel:

 -  Add Intel Emmitsburg pin controller support
 -  Make use of for_each_requested_gpio_in_range()
 -  Protect IO in few call backs by lock
 -  Split intel_config_get() to three functions
 -  Drop the only label in the code for consistency
 -  Get rid of redundant 'else' in intel_config_set_debounce()
 -  Make use of IRQ_RETVAL()
 -  Reduce scope of the lock
 -  Disable input and output buffer when switching to GPIO
 -  Allow drivers to define ACPI address space ID
 -  Allow drivers to define total amount of IRQs per community

lynxpoint:

 -  Drop no-op ACPI_PTR() call
 -  Introduce helpers to enable or disable input
 -  Make use of for_each_requested_gpio()

merrifield:
- Add I²S bus 2 pins to groups and functions
- Update pin names in accordance with official list

tigerlake:
- Add support for Tiger Lake-H

----------------------------------------------------------------
Andy Shevchenko (26):
gpiolib: Introduce for_each_requested_gpio_in_range() macro ARM/orion/gpio: Make use of for_each_requested_gpio()
gpio: mvebu: Make use of for_each_requested_gpio()
gpio: xra1403: Make use of for_each_requested_gpio()
pinctrl: at91: Make use of for_each_requested_gpio()
pinctrl: cherryview: Introduce chv_readl() helper
pinctrl: cherryview: Introduce helpers to IO with common registers
pinctrl: cherryview: Convert chv_writel() to use chv_padreg()
pinctrl: intel: Allow drivers to define total amount of IRQs per community
pinctrl: intel: Allow drivers to define ACPI address space ID
pinctrl: cherryview: Re-use data structures from pinctrl-intel.h (part 3)
pinctrl: intel: Disable input and output buffer when switching to GPIO
pinctrl: intel: Reduce scope of the lock
pinctrl: intel: Make use of IRQ_RETVAL()
pinctrl: intel: Get rid of redundant 'else' in intel_config_set_debounce()
pinctrl: intel: Drop the only label in the code for consistency
pinctrl: intel: Split intel_config_get() to three functions
pinctrl: intel: Protect IO in few call backs by lock
pinctrl: intel: Make use of for_each_requested_gpio_in_range()
pinctrl: lynxpoint: Make use of for_each_requested_gpio()
pinctrl: lynxpoint: Introduce helpers to enable or disable input
pinctrl: lynxpoint: Drop no-op ACPI_PTR() call
pinctrl: baytrail: Drop no-op ACPI_PTR() call
pinctrl: merrifield: Update pin names in accordance with official list
pinctrl: merrifield: Add I²S bus 2 pins to groups and functions
pinctrl: intel: Add Intel Emmitsburg pin controller support

Gustavo A. R. Silva (1):
pinctrl: baytrail: Use fallthrough pseudo-keyword

Hans de Goede (1):
pinctrl: baytrail: Fix pin being driven low for a while on gpiod_get(..., GPIOD_OUT_HIGH)

Mika Westerberg (1):
pinctrl: tigerlake: Add support for Tiger Lake-H

 arch/arm/plat-orion/gpio.c                 |   8 +-
 drivers/gpio/gpio-mvebu.c                  |   8 +-
 drivers/gpio/gpio-xra1403.c                |   8 +-
 drivers/pinctrl/intel/Kconfig              |   8 +
 drivers/pinctrl/intel/Makefile             |   1 +
 drivers/pinctrl/intel/pinctrl-baytrail.c   |  74 +++--
 drivers/pinctrl/intel/pinctrl-cherryview.c | 418 +++++++++++++++--------------
 drivers/pinctrl/intel/pinctrl-emmitsburg.c | 387 ++++++++++++++++++++++++++
 drivers/pinctrl/intel/pinctrl-intel.c      | 192 ++++++++-----
 drivers/pinctrl/intel/pinctrl-intel.h      |   4 +
 drivers/pinctrl/intel/pinctrl-lynxpoint.c  |  28 +-
 drivers/pinctrl/intel/pinctrl-merrifield.c |  50 ++--
 drivers/pinctrl/intel/pinctrl-tigerlake.c  | 358 ++++++++++++++++++++++++
 drivers/pinctrl/pinctrl-at91.c             |   7 +-
 include/linux/gpio/driver.h                |  16 ++
 15 files changed, 1215 insertions(+), 352 deletions(-)
 create mode 100644 drivers/pinctrl/intel/pinctrl-emmitsburg.c
Signature · 2 lines
With Best Regards,
Andy Shevchenko
#1 lore raw

Hi Andy!

Quoted 5 lines · Andy Shevchenko

ARM/orion/gpio:
- Make use of for_each_requested_gpio()

at91:
- Make use of for_each_requested_gpio()

(...)

Quoted 3 lines

gpio:
- xra1403: Make use of for_each_requested_gpio()
- mvebu: Make use of for_each_requested_gpio()

Are these dependent on this:

Quoted 2 lines

gpiolib:
- Introduce for_each_requested_gpio_in_range() macro

Because if they only need for_each_requested_gpio() I could just merge it to the gpio tree, since I have merged the immutable branch for that into both trees. Then I'd prefer to have one pinctrl and one gpio pull request.

However if they explicitly need for_each_requested_gpio_in_range() I say I can compromise and merge it all into pinctrl.

Yours,
Linus Walleij

#2 lore raw
Quoted 18 lines · Linus Walleij
Quoted 5 lines · Andy Shevchenko

ARM/orion/gpio:
- Make use of for_each_requested_gpio()

at91:
- Make use of for_each_requested_gpio()

(...)

Quoted 3 lines

gpio:
- xra1403: Make use of for_each_requested_gpio()
- mvebu: Make use of for_each_requested_gpio()

Are these dependent on this:

Quoted 2 lines

gpiolib:
- Introduce for_each_requested_gpio_in_range() macro

Quoted 7 lines

Because if they only need for_each_requested_gpio() I could just merge it to the gpio tree, since I have merged the immutable branch for that into both trees. Then I'd prefer to have one pinctrl and one gpio pull request.

However if they explicitly need for_each_requested_gpio_in_range() I say I can compromise and merge it all into pinctrl.

It uses usual practice, i.e. merge of immutable branches. The pin control stuff is dependent on this immutable branch (first patch).

I would like to avoid rebasing and doing it differently.

P.S. It should be no-op from Git perspective.

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#3 lore raw
Quoted 6 lines · Andy Shevchenko

It uses usual practice, i.e. merge of immutable branches. The pin control stuff is dependent on this immutable branch (first patch).

I would like to avoid rebasing and doing it differently.

P.S. It should be no-op from Git perspective.

Ahh I see, yeah this is the situation when the shortlog becomes quite confusing.

No problem, pulled it in now!

Yours,
Linus Walleij