From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Lee Jones <lee@kernel.org>, Linus Walleij <linusw@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [PATCH v3 0/4] gpio: timberdale: remove platform data header
Date: Fri, 27 Mar 2026 11:49:06 +0100 [thread overview]
Message-ID: <20260327-gpio-timberdale-swnode-v3-0-9a1bc1b2b124@oss.qualcomm.com> (raw)
There are several GPIO driver header scattered directly under
include/linux/. I'd like to either remove them or move then under
include/linux/gpio/. In case of gpio-timberdale, the platform data
struct can be replaced with generic device properties. This series does
that. It can go either though the MFD tree or GPIO with an Ack from Lee.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
---
Changes in v3:
- Replace magic values with named defines
- Move GPIO_NR_PINS into the MFD driver
- Explain the advantage of using device properties over platform data
- Link to v2: https://patch.msgid.link/20260316-gpio-timberdale-swnode-v2-0-ea0078066871@oss.qualcomm.com
Changes in v2:
- Change the property names to make them consistent with existing ones
used by intel
- Link to v1: https://patch.msgid.link/20260313-gpio-timberdale-swnode-v1-0-4df2e9b1dab5@oss.qualcomm.com
---
Bartosz Golaszewski (4):
mfd: timberdale: move GPIO_NR_PINS into the driver
mfd: timberdale: set up a software node for the GPIO cell
gpio: timberdale: use device properties
gpio: timberdale: remove platform data header
drivers/gpio/gpio-timberdale.c | 26 +++++++++++++-------------
drivers/mfd/timberdale.c | 33 ++++++++++++++++++---------------
drivers/mfd/timberdale.h | 1 -
include/linux/timb_gpio.h | 25 -------------------------
4 files changed, 31 insertions(+), 54 deletions(-)
---
base-commit: e77a5a5cfe43b4c25bd44a3818e487033287517f
change-id: 20260313-gpio-timberdale-swnode-03b1a0945359
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
next reply other threads:[~2026-03-27 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:49 Bartosz Golaszewski [this message]
2026-03-27 10:49 ` [PATCH v3 1/4] mfd: timberdale: move GPIO_NR_PINS into the driver Bartosz Golaszewski
2026-03-27 11:02 ` Andy Shevchenko
2026-04-09 12:51 ` Lee Jones
2026-04-09 13:18 ` (subset) " Lee Jones
2026-04-09 13:20 ` Lee Jones
2026-04-09 13:21 ` Bartosz Golaszewski
2026-04-09 13:45 ` Lee Jones
2026-03-27 10:49 ` [PATCH v3 2/4] mfd: timberdale: set up a software node for the GPIO cell Bartosz Golaszewski
2026-04-30 9:48 ` (subset) " Lee Jones
2026-04-30 9:53 ` Lee Jones
2026-03-27 10:49 ` [PATCH v3 3/4] gpio: timberdale: use device properties Bartosz Golaszewski
2026-03-27 10:49 ` [PATCH v3 4/4] gpio: timberdale: remove platform data header Bartosz Golaszewski
2026-04-09 13:21 ` [PATCH v3 0/4] " Lee Jones
2026-04-30 9:48 ` Lee Jones
2026-04-30 9:52 ` Lee Jones
2026-05-11 7:34 ` Bartosz Golaszewski
2026-05-13 13:39 ` Lee Jones
2026-05-13 13:44 ` Bartosz Golaszewski
2026-05-07 15:28 ` [GIT PULL] Immutable branch between MFD and GPIO due for the v7.2 merge window Lee Jones
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=20260327-gpio-timberdale-swnode-v3-0-9a1bc1b2b124@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).