From: Linus Walleij <linus.walleij@linaro.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V4 2/2] pinctrl: bcm: add driver for BCM4908 pinmux
Date: Tue, 25 Jan 2022 01:43:01 +0100 [thread overview]
Message-ID: <CACRpkdanFtHyvg9kt2xuB0d9cZLcWNP8WOAo2x8f5++bpbSnmg@mail.gmail.com> (raw)
In-Reply-To: <20220124102243.14912-2-zajec5@gmail.com>
On Mon, Jan 24, 2022 at 11:22 AM Rafał Miłecki <zajec5@gmail.com> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> BCM4908 has its own pins layout so it needs a custom binding and a Linux
> driver.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> ---
> V2: Formatting fixes
> Kconfig fix
> Cleanup of #include-s
> Use devm_kasprintf_strarray()
> V3: Bring back OF dependency - required by pinconf_generic_dt_node_to_map()
> V4: Rebased on top of the latest for-next which includes 5.17-rc1 now
Patch applied!
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-01-25 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:22 [PATCH V4 1/2] dt-bindings: pinctrl: Add binding for BCM4908 pinctrl Rafał Miłecki
2022-01-24 10:22 ` [PATCH V4 2/2] pinctrl: bcm: add driver for BCM4908 pinmux Rafał Miłecki
2022-01-25 0:43 ` Linus Walleij [this message]
2022-01-25 0:42 ` [PATCH V4 1/2] dt-bindings: pinctrl: Add binding for BCM4908 pinctrl 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=CACRpkdanFtHyvg9kt2xuB0d9cZLcWNP8WOAo2x8f5++bpbSnmg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=rafal@milecki.pl \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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 NNTP newsgroup(s).