From: Nathan Chancellor <nathan@kernel.org>
To: Jia Wang <wangjia@ultrarisc.com>, Linus Walleij <linusw@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver
Date: Sat, 13 Jun 2026 12:48:47 -0400 [thread overview]
Message-ID: <20260613164847.GA3152104@ax162> (raw)
In-Reply-To: <20260610-ultrarisc-pinctrl-v4-2-b7e9b2a8ed84@ultrarisc.com>
On Wed, Jun 10, 2026 at 01:29:56PM +0800, Jia Wang wrote:
> diff --git a/drivers/pinctrl/ultrarisc/pinctrl-ultrarisc.c b/drivers/pinctrl/ultrarisc/pinctrl-ultrarisc.c
> new file mode 100644
> index 000000000000..8fb5b0ea5b93
> --- /dev/null
> +++ b/drivers/pinctrl/ultrarisc/pinctrl-ultrarisc.c
...
> +static bool ur_function_is_gpio(struct pinctrl_dev *pctldev,
> + unsigned int selector)
> +{
> + const struct function_desc *function;
> +
> + function = pinmux_generic_get_function(pctldev, selector);
> + if (!function)
> + return false;
> +
> + for (u32 i = 0; i < function->func->ngroups; i++) {
> + const char *func_name;
> + int group_selector;
> +
> + group_selector = pinctrl_get_group_selector(pctldev,
> + function->func->groups[i]);
> + if (group_selector < 0)
> + return false;
> +
> + func_name = ur_get_group_function(pctldev, group_selector, 0);
> + if (!func_name || strcmp(func_name, "gpio"))
> + return false;
> + }
> +
> + return true;
> +}
The usage of pinctrl_get_group_selector() in this function breaks the
build when this driver is a module because pinctrl_get_group_selector()
is not exported for modules:
ERROR: modpost: "pinctrl_get_group_selector" [drivers/pinctrl/ultrarisc/pinctrl-ultrarisc.ko] undefined!
Also reported by the robots:
https://lore.kernel.org/202606130210.ytVPxHlm-lkp@intel.com/
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-06-13 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 5:29 [PATCH v4 0/2] pinctrl: ultrarisc: add DP1000 pinctrl support Jia Wang via B4 Relay
2026-06-10 5:29 ` [PATCH v4 1/2] dt-bindings: pinctrl: Add UltraRISC DP1000 pinctrl controller Jia Wang via B4 Relay
2026-06-10 5:29 ` [PATCH v4 2/2] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver Jia Wang via B4 Relay
2026-06-10 7:16 ` Bartosz Golaszewski
2026-06-13 16:48 ` Nathan Chancellor [this message]
2026-06-11 12:24 ` [PATCH v4 0/2] pinctrl: ultrarisc: add DP1000 pinctrl support Linus Walleij
2026-06-12 1:05 ` Jia Wang
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=20260613164847.GA3152104@ax162 \
--to=nathan@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wangjia@ultrarisc.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