From: Linus Walleij <linusw@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:PIN CONTROLLER - SINGLE"
<linux-arm-kernel@lists.infradead.org>,
"open list:PIN CONTROLLER - SINGLE" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/2] Utilize pinctrl-single for bcm7038-style chips
Date: Thu, 9 Apr 2026 10:44:14 +0200 [thread overview]
Message-ID: <CAD++jLm10MOYt5Xx9Am+Oqs8rOFse+L7WDOc-W_5OS5fXuSSHQ@mail.gmail.com> (raw)
In-Reply-To: <20260407235611.550515-1-florian.fainelli@broadcom.com>
On Wed, Apr 8, 2026 at 1:56 AM Florian Fainelli
<florian.fainelli@broadcom.com> wrote:
> This patch set allows Broadcom STB chips with the BCM7038-style
> pinmux/configuration blocks to use pinctrl-single. This does not
> preclude us from making use of a more sophisticated driver in the
> future, should we need to.
Patches applied for v7.1!
Yours,
Linus Walleij
prev parent reply other threads:[~2026-04-09 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 23:56 [PATCH 0/2] Utilize pinctrl-single for bcm7038-style chips Florian Fainelli
2026-04-07 23:56 ` [PATCH 1/2] dt-bindings: pinctrl: pinctrl-single: Add brcm,bcm7038-padconf Florian Fainelli
2026-04-08 9:11 ` Krzysztof Kozlowski
2026-04-07 23:56 ` [PATCH 2/2] pinctrl: single: Add bcm7038-padconf compatible matching Florian Fainelli
2026-04-09 8:43 ` [PATCH 0/2] Utilize pinctrl-single for bcm7038-style chips Linus Walleij
2026-04-09 8:44 ` Linus Walleij [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=CAD++jLm10MOYt5Xx9Am+Oqs8rOFse+L7WDOc-W_5OS5fXuSSHQ@mail.gmail.com \
--to=linusw@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=haojian.zhuang@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).