From: Stefan Wahren <stefan.wahren@i2se.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Eric Anholt <eric@anholt.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>,
Peter Robinson <pbrobinson@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC V2 0/4] pinctrl: bcm2835: improve libgpiod output
Date: Mon, 28 Jan 2019 10:23:35 +0100 [thread overview]
Message-ID: <1363edbf-51cf-54d4-e2a2-79ee4c3e501b@i2se.com> (raw)
In-Reply-To: <CACRpkdb1fUYz+a9QrO_jEcKgMNJO3ApZAVDR0gqz_Hd=WVQ35g@mail.gmail.com>
Hi Linus,
Am 28.01.19 um 09:06 schrieb Linus Walleij:
> On Mon, Jan 21, 2019 at 8:11 AM Stefan Wahren <stefan.wahren@i2se.com> wrote:
>
>> Based on a recent discussion [1],[2] about the unexpected output of gpioinfo
>> this patch series tries to improve the situation. Patches 1-3 are specific
>> changes for bcm2835 while the last one is the intended improvement for gpiolib.
>>
>> Changes in V2:
>> - take strict mode into account as suggested by Linus
>> - add bcm2835 specific changes
> Ooops started to apply this but now I noticed it's in RFC state so I
> backed them out and wait for a non-RFC version first.
i will split this series and resend the non-controversial part (Patch 1+2).
Stefan
>
> Yours,
> Linus Walleij
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-28 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 7:11 [PATCH RFC V2 0/4] pinctrl: bcm2835: improve libgpiod output Stefan Wahren
2019-01-21 7:11 ` [PATCH RFC V2 1/4] pinctrl: bcm2835: declare pin config as generic Stefan Wahren
2019-01-28 8:02 ` Linus Walleij
2019-01-21 7:11 ` [PATCH RFC V2 2/4] pinctrl: bcm2835: Direct GPIO config changes to generic pinctrl Stefan Wahren
2019-01-21 7:11 ` [PATCH RFC V2 3/4] pinctrl: bcm2835: activate strict mux mode Stefan Wahren
[not found] ` <20190121073419.iosy3bd6tcnexya7@wunner.de>
2019-01-21 9:57 ` Stefan Wahren
2019-01-21 7:11 ` [PATCH RFC V2 4/4] gpiolib: Take MUX usage into account Stefan Wahren
2019-01-28 9:06 ` Linus Walleij
2019-01-28 8:06 ` [PATCH RFC V2 0/4] pinctrl: bcm2835: improve libgpiod output Linus Walleij
2019-01-28 9:23 ` Stefan Wahren [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=1363edbf-51cf-54d4-e2a2-79ee4c3e501b@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bgolaszewski@baylibre.com \
--cc=eric@anholt.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=pbrobinson@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).