From: Stefan Wahren <wahrenst@gmx.net>
To: linux-gpio@vger.kernel.org
Subject: pinctrl: Questions regarding pinconf_ops and bcm2835
Date: Wed, 3 Jan 2024 13:12:40 +0100 [thread overview]
Message-ID: <bbc667b5-366b-430f-afd5-fa8a9326d9b7@gmx.net> (raw)
Hi,
i recently noticed that the BCM2711 (used on Raspberry Pi 4) doesn't
implement pin_config_get, but this SOC is able to read back the bias
settings of the pins. After looking deeper into the pinconf_ops i had
some questions:
1. Are there any other benefits from implementing pin_config_get except
of a proper debugfs output?
2. Since the pin direction of BCM2835/2711 (input/output) is already
handled by pinmux_ops via gpio_set_direction, how should pin_config_set
handle PIN_CONFIG_OUTPUT_ENABLE?
3. In case pin_config_get is implemented should the parameter
PIN_CONFIG_OUTPUT_ENABLE and PIN_CONFIG_OUTPUT be handled?
Best regards
next reply other threads:[~2024-01-03 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 12:12 Stefan Wahren [this message]
2024-01-08 7:33 ` pinctrl: Questions regarding pinconf_ops and bcm2835 Stefan Wahren
-- strict thread matches above, loose matches on Subject: below --
2024-01-20 11:34 Stefan Wahren
2024-01-20 12:42 ` Kent Gibson
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=bbc667b5-366b-430f-afd5-fa8a9326d9b7@gmx.net \
--to=wahrenst@gmx.net \
--cc=linux-gpio@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