From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Anatolij Gustschin <agust@denx.de>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH v2 0/5] powerpc: convert board-file GPIO chips to using new value setters
Date: Fri, 02 May 2025 10:59:46 +0200 [thread overview]
Message-ID: <20250502-gpiochip-set-rv-powerpc-v2-0-488e43e325bf@linaro.org> (raw)
struct gpio_chip now has callbacks for setting line values that return
an integer, allowing to indicate failures. We're in the process of
converting all GPIO drivers to using the new API. This series converts
all powerpc board-file level controllers.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Changes in v2:
- propagate the return value of i2c_smbus_write_byte_data() in
mcu_gpio_set() (Christophe Leroy)
- Link to v1: https://lore.kernel.org/r/20250408-gpiochip-set-rv-powerpc-v1-0-73dc1ebc6ef1@linaro.org
---
Bartosz Golaszewski (5):
powerpc: sysdev/gpio: use new line value setter callbacks
powerpc: 83xx/gpio: use new line value setter callbacks
powerpc: 44x/gpio: use new line value setter callbacks
powerpc: 52xx/gpio: use new line value setter callbacks
powerpc: 8xx/gpio: use new line value setter callbacks
arch/powerpc/platforms/44x/gpio.c | 7 ++++---
arch/powerpc/platforms/52xx/mpc52xx_gpt.c | 6 ++++--
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 13 ++++++++-----
arch/powerpc/platforms/8xx/cpm1.c | 12 ++++++++----
arch/powerpc/sysdev/cpm_common.c | 6 ++++--
5 files changed, 28 insertions(+), 16 deletions(-)
---
base-commit: 8a2d53ce3c5f82683ad3df9a9a55822816fe64e7
change-id: 20250326-gpiochip-set-rv-powerpc-1e98d28222aa
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
next reply other threads:[~2025-05-02 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 8:59 Bartosz Golaszewski [this message]
2025-05-02 8:59 ` [PATCH v2 1/5] powerpc: sysdev/gpio: use new line value setter callbacks Bartosz Golaszewski
2025-05-02 8:59 ` [PATCH v2 2/5] powerpc: 83xx/gpio: " Bartosz Golaszewski
2025-05-02 9:32 ` Christophe Leroy
2025-05-02 8:59 ` [PATCH v2 3/5] powerpc: 44x/gpio: " Bartosz Golaszewski
2025-05-02 8:59 ` [PATCH v2 4/5] powerpc: 52xx/gpio: " Bartosz Golaszewski
2025-05-02 8:59 ` [PATCH v2 5/5] powerpc: 8xx/gpio: " Bartosz Golaszewski
2025-05-13 9:23 ` [PATCH v2 0/5] powerpc: convert board-file GPIO chips to using new value setters Linus Walleij
2025-05-14 4:03 ` Madhavan Srinivasan
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=20250502-gpiochip-set-rv-powerpc-v2-0-488e43e325bf@linaro.org \
--to=brgl@bgdev.pl \
--cc=agust@denx.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).