From: Ramon Fried <ramon.fried@linux.intel.com>
To: linus.walleij@linaro.org, bgolaszewski@baylibre.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: pinctrl: -EAGAIN not supported but documented
Date: Mon, 21 Jan 2019 15:28:50 +0200 [thread overview]
Message-ID: <94b9acab-a739-a014-b068-768f40de38ec@linux.intel.com> (raw)
Hi Linus,
Stated in Documentation/driver-api/pinctl.rst:
Since some controllers have special logic for handling entire groups of pins
they can exploit the special whole-group pin control function. The
pin_config_group_set() callback is allowed to return the error code -EAGAIN,
for groups it does not want to handle, or if it just wants to do some
group-level handling and then fall through to iterate over all pins, in
which
case each individual pin will be treated by separate pin_config_set()
calls as
well.
----
This is not supported, and there's no code for handling it.
Should we add the necessary code or just remove the wrong documentation.
Thanks,
Ramon
next reply other threads:[~2019-01-21 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 13:28 Ramon Fried [this message]
2019-01-21 14:26 ` pinctrl: -EAGAIN not supported but documented Linus Walleij
2019-01-21 14:27 ` Ramon Fried
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=94b9acab-a739-a014-b068-768f40de38ec@linux.intel.com \
--to=ramon.fried@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).