From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
brgl@kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH v3 0/6] MIPS: alchemy: attach software nodes to GPIO controllers and use properties
Date: Wed, 27 May 2026 10:05:59 +0200 [thread overview]
Message-ID: <ahal58iuLAap2v6s@alpha.franken.de> (raw)
In-Reply-To: <20260526-gpio-swnode-alchemy-v3-0-2aaa1238ae4a@oss.qualcomm.com>
On Tue, May 26, 2026 at 06:40:31PM +0200, Bartosz Golaszewski wrote:
> This series of patches updates board previously converted to use static
> device properties/software nodes to attach and use nodes attached to the
> respective gpiochip devices rather than simply defining unattached
> software nodes with matching name. This is a requirement of newer
> gpiolib code. Note that there is currently a workaround preserving the
> lookup based on the software node name, but it will be removed soon.
>
> The additional 4 patches convert the remaining 2 boards to use software
> nodes as well and fix some build warnings.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> ---
> Changes in v3:
> - Avoid compound literals as older MIPS gcc seems to struggle with them
> - Link to v2: https://patch.msgid.link/20260505-gpio-swnode-alchemy-v2-0-cb208afc5b56@oss.qualcomm.com
>
> Changes in v2:
> - Add two patches fixing build warnings with missing prototypes
> - Use the new swnode field of struct platform_device_info
> - Link to v1: https://patch.msgid.link/20260309-alchemy-v1-0-f55e9dc60ba1@gmail.com
>
> ---
> Bartosz Golaszewski (2):
> MIPS: alchemy: platform: add missing include
> MIPS: alchemy: provide visible function prototypes to board files
>
> Dmitry Torokhov (4):
> MIPS: alchemy: mtx1: attach software nodes to GPIO chips
> MIPS: alchemy: db1000: use nodes attached to GPIO chips in properties
> MIPS: alchemy: gpr: switch to static device properties
> MIPS: alchemy: db1300: switch to static device properties
>
> arch/mips/alchemy/board-gpr.c | 127 ++++++++------
> arch/mips/alchemy/board-mtx1.c | 34 ++--
> arch/mips/alchemy/common/gpiolib.c | 45 ++++-
> arch/mips/alchemy/devboards/db1000.c | 31 ++--
> arch/mips/alchemy/devboards/db1200.c | 1 +
> arch/mips/alchemy/devboards/db1300.c | 219 ++++++++++++++++--------
> arch/mips/alchemy/devboards/db1550.c | 2 +
> arch/mips/alchemy/devboards/db1xxx.c | 11 +-
> arch/mips/alchemy/devboards/db1xxx.h | 18 ++
> arch/mips/alchemy/devboards/platform.c | 2 +
> arch/mips/include/asm/mach-au1x00/gpio-au1000.h | 5 +
> arch/mips/include/asm/mach-au1x00/gpio-au1300.h | 3 +
> 12 files changed, 322 insertions(+), 176 deletions(-)
> ---
> base-commit: e7ae89a0c97ce2b68b0983cd01eda67cf373517d
> change-id: 20260505-gpio-swnode-alchemy-3bff9c11e54c
series applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-05-27 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 16:40 [PATCH v3 0/6] MIPS: alchemy: attach software nodes to GPIO controllers and use properties Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 1/6] MIPS: alchemy: platform: add missing include Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 2/6] MIPS: alchemy: provide visible function prototypes to board files Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 3/6] MIPS: alchemy: mtx1: attach software nodes to GPIO chips Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 4/6] MIPS: alchemy: db1000: use nodes attached to GPIO chips in properties Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 5/6] MIPS: alchemy: gpr: switch to static device properties Bartosz Golaszewski
2026-05-26 16:40 ` [PATCH v3 6/6] MIPS: alchemy: db1300: " Bartosz Golaszewski
2026-05-27 8:05 ` Thomas Bogendoerfer [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=ahal58iuLAap2v6s@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=manuel.lauss@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