From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, mfe@pengutronix.de,
Jules Maselbas <jmaselbas@kalray.eu>
Subject: Re: [PATCH v2 00/10] Fix gpio-hogs and sync with Linux gpiolib
Date: Wed, 14 Jun 2023 16:19:43 +0200 [thread overview]
Message-ID: <20230614141943.GZ18491@pengutronix.de> (raw)
In-Reply-To: <20230614100747.3368109-1-a.fatoum@pengutronix.de>
On Wed, Jun 14, 2023 at 12:07:37PM +0200, Ahmad Fatoum wrote:
> Quoting v1:
>
> the purpose of this series is to fix the gpio-hogs mechanism since this
> is broken since commit 3641d381e6 ("gpiolib: Add of_xlate support").
>
> Patch1: Revert the above mentioned commit to make the gpio-hogs working
> again.
>
> Patch2-10: Add the of_xlate support required for the upcoming sunxi
> pinctrl driver. The mechanism is now more in sync with kernel
> gpiolib. This allows to sync easier with the kernel gpiolib
> in case of new features or fixes.
>
> I've incorporated feedback and tested this still works on a i.mx8mn.
> Patch 1 should be ok to go into master and the rest to next IMO.
>
> Changelog in each patch.
>
> Marco Felsch (10):
> gpiolib: fix gpio-hog functionality
> gpiolib: simplify for loop break condition
> gpiolib: rename local gpio-line-names variable
> gpiolib: fix gpio name memory leak
> gpiolib: fix missing error check while query gpio-line-names
> gpiolib: refactor gpio-line-names parsing
> gpiolib: introduce of_gpiochip_add to bundle all of functions
> OF: gpio: sync of_get_named_gpio_flags variable with kernel
> OF: gpio: call of_node_put in of_get_named_gpio_flags
> gpiolib: add of_xlate support
>
> drivers/gpio/gpiolib.c | 207 ++++++++++++++++++++++++++++++-----------
> drivers/of/of_gpio.c | 69 ++++++++++----
> include/gpio.h | 30 +++++-
> 3 files changed, 231 insertions(+), 75 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-06-14 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:07 Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 01/10] gpiolib: fix gpio-hog functionality Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 02/10] gpiolib: simplify for loop break condition Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 03/10] gpiolib: rename local gpio-line-names variable Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 04/10] gpiolib: fix gpio name memory leak Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 05/10] gpiolib: fix missing error check while query gpio-line-names Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 06/10] gpiolib: refactor gpio-line-names parsing Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 07/10] gpiolib: introduce of_gpiochip_add to bundle all of functions Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 08/10] OF: gpio: sync of_get_named_gpio_flags variable with kernel Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 09/10] OF: gpio: call of_node_put in of_get_named_gpio_flags Ahmad Fatoum
2023-06-14 10:07 ` [PATCH v2 10/10] gpiolib: add of_xlate support Ahmad Fatoum
2023-06-16 8:14 ` Sascha Hauer
2023-06-16 12:13 ` Marco Felsch
2023-06-14 14:19 ` Sascha Hauer [this message]
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=20230614141943.GZ18491@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@kalray.eu \
--cc=mfe@pengutronix.de \
/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