From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] pinctrl: uniphier: omit redundant input enable bit information
Date: Tue, 1 Aug 2017 10:15:42 +0200 [thread overview]
Message-ID: <CACRpkdYpLYcKCbvpMQ34iLsdjroGKy=UvFqG3nqQk5VyA8CB0A@mail.gmail.com> (raw)
In-Reply-To: <1501482071-9819-5-git-send-email-yamada.masahiro@socionext.com>
On Mon, Jul 31, 2017 at 8:21 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> For LD11/20 SoCs (capable of per-pin input enable), the iectrl bit
> number matches its pin number. So, this is redundant information.
> Instead, we just need a flag to know if the iectrl gating exists or not.
>
> With this refactoring, 5 bits in pin data will be saved.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-08-01 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 6:21 [PATCH 0/6] pinctrl: uniphier: UniPhier pinctrl updates for v4.14 Masahiro Yamada
2017-07-31 6:21 ` [PATCH 1/6] pinctrl: uniphier: remove unneeded EXPORT_SYMBOL_GPL() Masahiro Yamada
2017-08-01 8:10 ` Linus Walleij
2017-07-31 6:21 ` [PATCH 2/6] pinctrl: uniphier: fix pin_config_get() for input-enable Masahiro Yamada
2017-08-01 8:11 ` Linus Walleij
2017-07-31 6:21 ` [PATCH 4/6] pinctrl: uniphier: omit redundant input enable bit information Masahiro Yamada
2017-08-01 8:15 ` Linus Walleij [this message]
2017-07-31 6:21 ` [PATCH 5/6] pinctrl: uniphier: add suspend / resume support Masahiro Yamada
2017-08-01 8:16 ` Linus Walleij
2017-07-31 6:21 ` [PATCH 6/6] pinctrl: uniphier: add UniPhier PXs3 pinctrl driver Masahiro Yamada
2017-08-01 8:18 ` Linus Walleij
[not found] ` <1501482071-9819-4-git-send-email-yamada.masahiro@socionext.com>
2017-08-01 8:14 ` [PATCH 3/6] pinctrl: uniphier: clean up GPIO port muxing 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='CACRpkdYpLYcKCbvpMQ34iLsdjroGKy=UvFqG3nqQk5VyA8CB0A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).