From: Yixun Lan <dlan@kernel.org>
To: Junhui Liu <junhui.liu@pigmoral.tech>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] gpio/pinctrl: spacemit: Add GPIO pin configuration support for K1
Date: Thu, 12 Mar 2026 19:21:49 +0800 [thread overview]
Message-ID: <20260312112149-GKG302167@kernel.org> (raw)
In-Reply-To: <20260312-k1-gpio-set-config-v1-0-8c3541da16b1@pigmoral.tech>
Hi Junhui,
On 16:42 Thu 12 Mar , Junhui Liu wrote:
> This add GPIO pin configuration support for the Spacemit K1 SoC. Some
> use cases require configuring pin attributes like pull-up/down when using
> GPIO lines.
>
> A practical example is the SD card detection pin on the Banana Pi BPI-F3
> board. Since it lacks an external pull-up circuit, the pin must be
> configured with an internal pull-up to function correctly. Such
> configurations can be specified directly in the devicetree:
>
> cd-gpios = <&gpio K1_GPIO(80) (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
>
> To address this, add the set_config() callback to the gpio-spacemit-k1
> driver to enable pin configuration through pinctrl, and modify the
> pinctrl driver to return -ENOTSUPP instead of -EINVAL for unsupported
> parameters, allowing the GPIO subsystem to gracefully handle them.
>
Thanks for working on this, for the series
Reviewed-by: Yixun Lan <dlan@kernel.org>
> ---
> Junhui Liu (2):
> pinctrl: spacemit: return -ENOTSUPP for unsupported pin configurations
> gpio: spacemit-k1: Add set_config callback support
>
> drivers/gpio/gpio-spacemit-k1.c | 1 +
> drivers/pinctrl/spacemit/pinctrl-k1.c | 21 ++++++++++++---------
> 2 files changed, 13 insertions(+), 9 deletions(-)
> ---
> base-commit: b29fb8829bff243512bb8c8908fd39406f9fd4c3
> change-id: 20260312-k1-gpio-set-config-f0873e92ebac
>
> Best regards,
> --
> Junhui Liu <junhui.liu@pigmoral.tech>
>
--
Yixun Lan (dlan)
WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Junhui Liu <junhui.liu@pigmoral.tech>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] gpio/pinctrl: spacemit: Add GPIO pin configuration support for K1
Date: Thu, 12 Mar 2026 19:21:49 +0800 [thread overview]
Message-ID: <20260312112149-GKG302167@kernel.org> (raw)
In-Reply-To: <20260312-k1-gpio-set-config-v1-0-8c3541da16b1@pigmoral.tech>
Hi Junhui,
On 16:42 Thu 12 Mar , Junhui Liu wrote:
> This add GPIO pin configuration support for the Spacemit K1 SoC. Some
> use cases require configuring pin attributes like pull-up/down when using
> GPIO lines.
>
> A practical example is the SD card detection pin on the Banana Pi BPI-F3
> board. Since it lacks an external pull-up circuit, the pin must be
> configured with an internal pull-up to function correctly. Such
> configurations can be specified directly in the devicetree:
>
> cd-gpios = <&gpio K1_GPIO(80) (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
>
> To address this, add the set_config() callback to the gpio-spacemit-k1
> driver to enable pin configuration through pinctrl, and modify the
> pinctrl driver to return -ENOTSUPP instead of -EINVAL for unsupported
> parameters, allowing the GPIO subsystem to gracefully handle them.
>
Thanks for working on this, for the series
Reviewed-by: Yixun Lan <dlan@kernel.org>
> ---
> Junhui Liu (2):
> pinctrl: spacemit: return -ENOTSUPP for unsupported pin configurations
> gpio: spacemit-k1: Add set_config callback support
>
> drivers/gpio/gpio-spacemit-k1.c | 1 +
> drivers/pinctrl/spacemit/pinctrl-k1.c | 21 ++++++++++++---------
> 2 files changed, 13 insertions(+), 9 deletions(-)
> ---
> base-commit: b29fb8829bff243512bb8c8908fd39406f9fd4c3
> change-id: 20260312-k1-gpio-set-config-f0873e92ebac
>
> Best regards,
> --
> Junhui Liu <junhui.liu@pigmoral.tech>
>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-12 11:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:42 [PATCH 0/2] gpio/pinctrl: spacemit: Add GPIO pin configuration support for K1 Junhui Liu
2026-03-12 8:42 ` Junhui Liu
2026-03-12 8:42 ` [PATCH 1/2] pinctrl: spacemit: return -ENOTSUPP for unsupported pin configurations Junhui Liu
2026-03-12 8:42 ` Junhui Liu
2026-03-13 13:37 ` Yao Zi
2026-03-13 13:37 ` Yao Zi
2026-03-13 13:52 ` Bartosz Golaszewski
2026-03-13 13:52 ` Bartosz Golaszewski
2026-03-14 8:20 ` Anand Moon
2026-03-14 8:20 ` Anand Moon
2026-03-12 8:42 ` [PATCH 2/2] gpio: spacemit-k1: Add set_config callback support Junhui Liu
2026-03-12 8:42 ` Junhui Liu
2026-03-13 14:05 ` Bartosz Golaszewski
2026-03-13 14:05 ` Bartosz Golaszewski
2026-03-19 12:54 ` Linus Walleij
2026-03-19 12:54 ` Linus Walleij
2026-03-14 8:20 ` Anand Moon
2026-03-14 8:20 ` Anand Moon
2026-03-12 11:21 ` Yixun Lan [this message]
2026-03-12 11:21 ` [PATCH 0/2] gpio/pinctrl: spacemit: Add GPIO pin configuration support for K1 Yixun Lan
2026-03-19 12:53 ` Linus Walleij
2026-03-19 12:53 ` Linus Walleij
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=20260312112149-GKG302167@kernel.org \
--to=dlan@kernel.org \
--cc=brgl@kernel.org \
--cc=junhui.liu@pigmoral.tech \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.