From: Linus Walleij <linus.walleij@linaro.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH V4 0/2] pinctrl: bcm2835: Implement pin_conf_get
Date: Thu, 28 Mar 2024 09:52:55 +0100 [thread overview]
Message-ID: <CACRpkda5MSsb5p0FEj=XzV+VsmaSEbKF--BkOon0fEPgoLQXwQ@mail.gmail.com> (raw)
In-Reply-To: <20240307070113.4888-1-wahrenst@gmx.net>
On Thu, Mar 7, 2024 at 8:01 AM Stefan Wahren <wahrenst@gmx.net> wrote:
> 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.
This v4 version applied for kernel v6.10!
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH V4 0/2] pinctrl: bcm2835: Implement pin_conf_get
Date: Thu, 28 Mar 2024 09:52:55 +0100 [thread overview]
Message-ID: <CACRpkda5MSsb5p0FEj=XzV+VsmaSEbKF--BkOon0fEPgoLQXwQ@mail.gmail.com> (raw)
In-Reply-To: <20240307070113.4888-1-wahrenst@gmx.net>
On Thu, Mar 7, 2024 at 8:01 AM Stefan Wahren <wahrenst@gmx.net> wrote:
> 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.
This v4 version applied for kernel v6.10!
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-28 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 7:01 [PATCH V4 0/2] pinctrl: bcm2835: Implement pin_conf_get Stefan Wahren
2024-03-07 7:01 ` Stefan Wahren
2024-03-07 7:01 ` [PATCH V4 1/2] pinctrl: bcm2835: Implement bcm2835_pinconf_get Stefan Wahren
2024-03-07 7:01 ` Stefan Wahren
2024-03-08 6:52 ` Chen-Yu Tsai
2024-03-08 6:52 ` Chen-Yu Tsai
2024-03-07 7:01 ` [PATCH V4 2/2] pinctrl: bcm2835: Implement bcm2711_pinconf_get Stefan Wahren
2024-03-07 7:01 ` Stefan Wahren
2024-03-28 8:52 ` Linus Walleij [this message]
2024-03-28 8:52 ` [PATCH V4 0/2] pinctrl: bcm2835: Implement pin_conf_get Linus Walleij
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='CACRpkda5MSsb5p0FEj=XzV+VsmaSEbKF--BkOon0fEPgoLQXwQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--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 \
--cc=wahrenst@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.