From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v6 01/12] pinctrl: Add pinmux property support to pinctrl-generic
Date: Fri, 9 Oct 2020 09:00:56 -0400 [thread overview]
Message-ID: <20201009130056.GI14816@bill-the-cat> (raw)
In-Reply-To: <20200914150206.90002-2-seanga2@gmail.com>
On Mon, Sep 14, 2020 at 11:01:55AM -0400, Sean Anderson wrote:
> The pinmux property allows for smaller and more compact device trees,
> especially when there are many pins which need to be assigned individually.
> Instead of specifying an array of strings to be parsed as pins and a
> function property, the pinmux property contains an array of integers
> representing pinmux groups. A pinmux group consists of the pin identifier
> and mux settings represented as a single integer or an array of integers.
> Each individual pin controller driver specifies the exact format of a
> pinmux group. As specified in the Linux documentation, a pinmux group may
> be multiple integers long. However, no existing drivers use multi-integer
> pinmux groups, so I have chosen to omit this feature. This makes the
> implementation easier, since there is no need to allocate a buffer to do
> endian conversions.
>
> Support for the pinmux property is done differently than in Linux. As far
> as I can tell, inversion of control is used when implementing support for
> the pins and groups properties to avoid allocating. This results in some
> duplication of effort; every property in a config node is parsed once for
> each pin in that node. This is not such an overhead with pins and groups
> properties, since having multiple pins in one config node does not occur
> especially often. However, the semantics of the pinmux property make such a
> configuration much more appealing. A future patch could parse all config
> properties at once and store them in an array. This would make it easier to
> create drivers which do not function solely as callbacks from
> pinctrl-generic.
>
> This commit increases the size of the sandbox build by approximately 48
> bytes. However, it also decreases the size of the K210 device tree by 2
> KiB from the previous version of this series.
>
> The documentation has been updated from the last Linux commit before it was
> split off into yaml files.
>
> Signed-off-by: Sean Anderson <seanga2@gmail.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201009/a0beb5f2/attachment.sig>
next prev parent reply other threads:[~2020-10-09 13:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 15:01 [PATCH v6 00/12] riscv: Add FPIOA and GPIO support for Kendryte K210 Sean Anderson
2020-09-14 15:01 ` [PATCH v6 01/12] pinctrl: Add pinmux property support to pinctrl-generic Sean Anderson
2020-10-09 13:00 ` Tom Rini [this message]
2020-09-14 15:01 ` [PATCH v6 02/12] pinctrl: Reformat documentation in dm/pinctrl.h Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:01 ` [PATCH v6 03/12] test: pinmux: Add test for pin muxing Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:01 ` [PATCH v6 04/12] pinctrl: Add support for Kendryte K210 FPIOA Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:01 ` [PATCH v6 05/12] gpio: dw: Fix warnings about casting int to pointer Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 06/12] gpio: dw: Add a trailing underscore to generated name Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 07/12] gpio: dw: Return output value when direction is out Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 08/12] led: gpio: Default to using node name if label is absent Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 09/12] test: dm: Test for default led naming Sean Anderson
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 10/12] riscv: Add pinmux and gpio bindings for Kendryte K210 Sean Anderson
2020-09-30 7:43 ` Rick Chen
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 11/12] riscv: add DT binding for BOOT button on Maix board Sean Anderson
2020-09-30 7:44 ` Rick Chen
2020-10-09 13:01 ` Tom Rini
2020-09-14 15:02 ` [PATCH v6 12/12] riscv: Add FPIOA and GPIO support for Kendryte K210 Sean Anderson
2020-09-18 7:37 ` Leo Liang
2020-09-18 10:46 ` Sean Anderson
2020-10-09 13:02 ` Tom Rini
2020-10-07 19:30 ` [PATCH v6 00/12] " Sean Anderson
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=20201009130056.GI14816@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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