linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH V3 0/2] dt-bindings: pinctrl: pins, groups & functions
Date: Fri, 10 Dec 2021 12:42:20 +0100	[thread overview]
Message-ID: <20211210114222.26581-1-zajec5@gmail.com> (raw)

From: Rafał Miłecki <rafal@milecki.pl>

This is my minimalized attempt of setting up pins, groups & functions
bindings.

I've been warned that Linux pinctrl subsystem may require refactoring
before it's ready to handle such bindings properly and that appears to
be correct. I'll need to invest more time into reorganizing Linux
structs. Right now it's not ready for tree-like design and it uses
more-or-less magic numbers to handle pins <-> groups relation.

Meanwhile I'd like to get dt-bindings reviewed & possibly merged. To be
honest - my initial reason for that work was developing U-Boot drivers.

Please kindly review those bindings and optionally treat my WIP work on
Linux implementation as proof of concept.

Reference:
RFC: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20211110231436.8866-1-zajec5@gmail.com/
V1: https://patchwork.ozlabs.org/project/linux-gpio/list/?series=272685&submitter=&state=*&q=&archive=&delegate=
V2: https://patchwork.ozlabs.org/project/linux-gpio/list/?series=273711&submitter=&state=*&q=&archive=&delegate=

Rafał Miłecki (2):
  dt-bindings: pinctrl: support specifying pins, groups & functions
  dt-bindings: pinctrl: brcm,ns-pinmux: describe pins, groups &
    functions

 .../bindings/pinctrl/brcm,ns-pinmux.yaml      | 38 ++++++++++++++++++-
 .../devicetree/bindings/pinctrl/pinctrl.yaml  | 34 +++++++++++++++++
 2 files changed, 71 insertions(+), 1 deletion(-)

-- 
2.31.1


             reply	other threads:[~2021-12-10 11:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 11:42 Rafał Miłecki [this message]
2021-12-10 11:42 ` [PATCH V3 1/2] dt-bindings: pinctrl: support specifying pins, groups & functions Rafał Miłecki
2021-12-10 23:26   ` Linus Walleij
2021-12-11 11:16     ` Rafał Miłecki
2021-12-14 19:59       ` Rob Herring
2021-12-14 20:10         ` Rafał Miłecki
2021-12-14 21:50           ` Rafał Miłecki
2021-12-10 11:42 ` [PATCH V3 2/2] dt-bindings: pinctrl: brcm,ns-pinmux: describe " Rafał Miłecki
2021-12-10 14:02   ` Rob Herring
2021-12-11  7:07   ` Tony Lindgren

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=20211210114222.26581-1-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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).