From: Alex Tran <alex.tran@oss.qualcomm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Linus Walleij <linusw@kernel.org>,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] pinctrl: scmi: Replace get function and group info with generic callbacks
Date: Fri, 14 Aug 2026 17:05:27 -0700 [thread overview]
Message-ID: <56107a6d-962d-4508-a1d3-7a6e9e2af887@oss.qualcomm.com> (raw)
In-Reply-To: <an7RL_mTsznZjeIQ@pluto>
> Hi Alex,
>
> I gave it a go at this series on an emulated setup and with these
> changes I get:
>
> root@deb-guest:~# modprobe pinctrl-scmi
> [ 15.329932] scmi-pinctrl scmi_dev.4: error -EINVAL: Failed to register functions
> [ 15.330259] scmi-pinctrl scmi_dev.4: probe with driver scmi-pinctrl failed with error -22
>
> ...not debugged any further.
>
> Thanks,
> Cristian
Hi Cristian,
I've tested this series on sa8797p hardware and did not experience any issues
with registering functions during probe. Can you provide me with the pin
topology of your emulated setup? I have a hunch that the topology may
contain a function with 0 groups which is why -EINVAL is being returned.
The previous pinctrl_scmi_get_function_groups callback considered a function
with no groups invalid.
Best,
Alex
prev parent reply other threads:[~2026-08-15 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:49 [PATCH 0/2] pinctrl: scmi: Replace get function and group info with generic callbacks Alex Tran
2026-07-31 17:49 ` [PATCH 1/2] pinctrl: scmi: Replace pinmux ops get function info with generics Alex Tran
2026-07-31 17:49 ` [PATCH 2/2] pinctrl: scmi: Replace pinctrl ops get group " Alex Tran
2026-08-14 8:26 ` [PATCH 0/2] pinctrl: scmi: Replace get function and group info with generic callbacks Cristian Marussi
2026-08-15 0:05 ` Alex Tran [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=56107a6d-962d-4508-a1d3-7a6e9e2af887@oss.qualcomm.com \
--to=alex.tran@oss.qualcomm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@kernel.org \
/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