From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux pin control <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-pinctrl for 6.15-1
Date: Wed, 12 Mar 2025 11:45:07 +0200 [thread overview]
Message-ID: <Z9FXo5qO8RCZCKzk@black.fi.intel.com> (raw)
Hi Linux pin control maintainers,
A batch of the updates to the Intel pin control driver. Due to driver core
changes some other subsystem drivers were touched and the respective
maintainers provided needed tags. The changes were in Linux Next for a few
weeks without any problems reported. Please, pull for v6.15-rc1.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v6.15-1
for you to fetch changes up to 0ee2261d08aa21a7327f145cbf1bfb6ac2205c7d:
pinctrl: intel: drop repeated config dependency (2025-03-03 16:20:51 +0200)
----------------------------------------------------------------
intel-pinctrl for v6.15-1
* Introduce devm_kmemdup_array() and convert Intel pin control drivers
* Update PWM handling for the cases when it's provided by Intel pin control
* Miscellaneous fixes, updates, and cleanups
The following is an automated git shortlog grouped by driver:
baytrail:
- copy communities using devm_kmemdup_array()
- Use dedicated helpers for chained IRQ handlers
cherryview:
- use devm_kmemdup_array()
devres:
- Introduce devm_kmemdup_array()
driver core:
- Split devres APIs to device/devres.h
err.h:
- move IOMEM_ERR_PTR() to err.h
iio:
- adc: xilinx-xadc-core: use devm_kmemdup_array()
- imu: st_lsm9ds0: Replace device.h with what is needed
input:
- ipaq-micro-keys: use devm_kmemdup_array()
- sparse-keymap: use devm_kmemdup_array()
intel:
- drop repeated config dependency
- copy communities using devm_kmemdup_array()
- Fix wrong bypass assignment in intel_pinctrl_probe_pwm()
- Import PWM_LPSS namespace for devm_pwm_lpss_probe()
lynxpoint:
- Use dedicated helpers for chained IRQ handlers
MAINTAINERS:
- Add pin control and GPIO to the Intel MID record
pwm:
- lpss: Clarify the bypass member semantics in struct pwm_lpss_boardinfo
- lpss: Actually use a module namespace by defining the namespace earlier
pxa2xx:
- use devm_kmemdup_array()
tangier:
- use devm_kmemdup_array()
----------------------------------------------------------------
Andy Shevchenko (9):
pinctrl: baytrail: Use dedicated helpers for chained IRQ handlers
pinctrl: lynxpoint: Use dedicated helpers for chained IRQ handlers
MAINTAINERS: Add pin control and GPIO to the Intel MID record
pwm: lpss: Clarify the bypass member semantics in struct pwm_lpss_boardinfo
pinctrl: intel: Fix wrong bypass assignment in intel_pinctrl_probe_pwm()
driver core: Split devres APIs to device/devres.h
iio: imu: st_lsm9ds0: Replace device.h with what is needed
Merge patch series "Split devres APIs to device/devres.h and introduce devm_kmemdup_array()"
Merge tag 'ib-devres-iio-input-pinctrl-v6.15' into intel/pinctrl
Raag Jadav (11):
err.h: move IOMEM_ERR_PTR() to err.h
devres: Introduce devm_kmemdup_array()
pinctrl: intel: copy communities using devm_kmemdup_array()
pinctrl: baytrail: copy communities using devm_kmemdup_array()
pinctrl: cherryview: use devm_kmemdup_array()
pinctrl: tangier: use devm_kmemdup_array()
pinctrl: pxa2xx: use devm_kmemdup_array()
iio: adc: xilinx-xadc-core: use devm_kmemdup_array()
input: sparse-keymap: use devm_kmemdup_array()
input: ipaq-micro-keys: use devm_kmemdup_array()
pinctrl: intel: drop repeated config dependency
Uwe Kleine-König (2):
pinctrl: intel: Import PWM_LPSS namespace for devm_pwm_lpss_probe()
pwm: lpss: Actually use a module namespace by defining the namespace earlier
MAINTAINERS | 7 ++
drivers/iio/adc/xilinx-xadc-core.c | 4 +-
drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_i2c.c | 2 +-
drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c | 2 +-
drivers/input/keyboard/ipaq-micro-keys.c | 5 +-
drivers/input/sparse-keymap.c | 3 +-
drivers/pinctrl/intel/Kconfig | 2 -
drivers/pinctrl/intel/pinctrl-baytrail.c | 11 +--
drivers/pinctrl/intel/pinctrl-cherryview.c | 5 +-
drivers/pinctrl/intel/pinctrl-intel.c | 8 +-
drivers/pinctrl/intel/pinctrl-lynxpoint.c | 5 +-
drivers/pinctrl/intel/pinctrl-tangier.c | 5 +-
drivers/pinctrl/pxa/pinctrl-pxa2xx.c | 8 +-
drivers/pwm/pwm-lpss.c | 4 +-
include/linux/device.h | 119 +------------------------
include/linux/device/devres.h | 129 ++++++++++++++++++++++++++++
include/linux/err.h | 3 +
include/linux/io.h | 2 -
include/linux/platform_data/x86/pwm-lpss.h | 33 ++++++-
19 files changed, 200 insertions(+), 157 deletions(-)
create mode 100644 include/linux/device/devres.h
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2025-03-12 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:45 Andy Shevchenko [this message]
2025-03-13 9:00 ` [GIT PULL] intel-pinctrl for 6.15-1 Linus Walleij
2025-03-13 9:18 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z9FXo5qO8RCZCKzk@black.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox