From: Stefan Wahren <wahrenst@gmx.net>
To: Linus Walleij <linus.walleij@linaro.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <wahrenst@gmx.net>
Subject: [PATCH RFC 0/2] pinctrl: bcm2835: Implement pin_conf_get
Date: Sun, 4 Feb 2024 17:58:50 +0100 [thread overview]
Message-ID: <20240204165852.166157-1-wahrenst@gmx.net> (raw)
For years, the Raspberry Pi users relied on userspace programs to read
the pin configuration. In the meantime, it has become apparent that this
approach has reached its limits for various reasons.
This patch series now attempts to improve the debugging possibilities on
the kernel side in order to reduce the dependency on these userspace
programs.
Stefan Wahren (2):
pinctrl: bcm2835: Implement bcm2835_pinconf_get
pinctrl: bcm2835: Implement bcm2711_pinconf_get
drivers/pinctrl/bcm/pinctrl-bcm2835.c | 78 ++++++++++++++++++++++++++-
1 file changed, 76 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-04 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 16:58 Stefan Wahren [this message]
2024-02-04 16:58 ` [PATCH RFC 1/2] pinctrl: bcm2835: Implement bcm2835_pinconf_get Stefan Wahren
2024-02-04 16:58 ` [PATCH RFC 2/2] pinctrl: bcm2835: Implement bcm2711_pinconf_get Stefan Wahren
2024-02-07 10:56 ` [PATCH RFC 0/2] pinctrl: bcm2835: Implement pin_conf_get Linus Walleij
2024-02-07 11:33 ` Stefan Wahren
2024-02-07 18:22 ` Florian Fainelli
2024-02-25 10:01 ` Stefan Wahren
2024-02-27 0:22 ` Florian Fainelli
2024-02-27 20:07 ` Stefan Wahren
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=20240204165852.166157-1-wahrenst@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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