From: Linus Walleij <linus.walleij@linaro.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Michael Walle <michael@walle.cc>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Jonas Gorski <jonas.gorski@gmail.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 00/12] pinctrl: add BCM63XX pincontrol support
Date: Wed, 3 Mar 2021 10:29:16 +0100 [thread overview]
Message-ID: <CACRpkdZQRtTi75KMFDpM6eJ9hVuPLNJBBs6bHKMt7_PNW8gcFQ@mail.gmail.com> (raw)
In-Reply-To: <20210302191613.29476-1-noltari@gmail.com>
On Tue, Mar 2, 2021 at 8:16 PM Álvaro Fernández Rojas <noltari@gmail.com> wrote:
> v2: introduce changes suggested by Linus Walleij and remove interrupts
> - In order to use GPIO_REGMAP, the need to get gpio_chip from gpio_regmap
> and use it for pinctrl_add_gpio_range() and gpio_chip.direction_input()
> and gpio_chip.direction_output().
Looking so much better don't you think? :)
If you also get rid of the exposed struct using DT gpio-ranges we are
done I think, just need some DT review slack for the DT maintainers
for the bindings.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-03-03 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 19:16 [PATCH v2 00/12] pinctrl: add BCM63XX pincontrol support Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 01/12] Documentation: add BCM6328 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 02/12] pinctrl: add a pincontrol driver for BCM6328 Álvaro Fernández Rojas
2021-03-02 20:01 ` Michael Walle
2021-03-02 19:16 ` [PATCH v2 03/12] Documentation: add BCM6358 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 04/12] pinctrl: add a pincontrol driver for BCM6358 Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 05/12] Documentation: add BCM6362 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 06/12] pinctrl: add a pincontrol driver for BCM6362 Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 07/12] Documentation: add BCM6368 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 08/12] pinctrl: add a pincontrol driver for BCM6368 Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 09/12] Documentation: add BCM63268 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 10/12] pinctrl: add a pincontrol driver for BCM63268 Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 11/12] Documentation: add BCM6318 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-02 19:16 ` [PATCH v2 12/12] pinctrl: add a pincontrol driver for BCM6318 Álvaro Fernández Rojas
2021-03-03 9:29 ` Linus Walleij [this message]
2021-03-03 9:32 ` [PATCH v2 00/12] pinctrl: add BCM63XX pincontrol support Álvaro Fernández Rojas
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=CACRpkdZQRtTi75KMFDpM6eJ9hVuPLNJBBs6bHKMt7_PNW8gcFQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fazilyildiran@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=noltari@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).