From: Peter Rosin <peda@axentia.se>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Pankaj Bansal <pankaj.bansal@nxp.com>
Subject: [PATCH 0/2] mux: a couple of patches for 5.2-rc1
Date: Tue, 30 Apr 2019 19:52:33 +0000 [thread overview]
Message-ID: <20190430195226.8965-1-peda@axentia.se> (raw)
Hi Greg,
A small addition to the mmio mux so that it can handle non-syscon
regmaps. The bindings patch should probably have had Robs tag,
but after a bit of back and forth I got the impression that it
wasn't really needed, since it's basically just a file rename
plus addition of a compatible [1]. The patches have been in -next
for a week or so.
But, if I misunderstood or if you have a tag to spare Rob, now
is the time. :-)
Cheers,
Peter
[1] https://marc.info/?l=devicetree&m=155121843503590
"That would have saved me reviewing the whole thing again..."
Pankaj Bansal (2):
dt-bindings: add register based devices' mux controller DT bindings
mux: mmio: add generic regmap bitfield-based multiplexer
Documentation/devicetree/bindings/mux/mmio-mux.txt | 60 ----------
Documentation/devicetree/bindings/mux/reg-mux.txt | 129 +++++++++++++++++++++
drivers/mux/Kconfig | 12 +-
drivers/mux/mmio.c | 6 +-
4 files changed, 140 insertions(+), 67 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/mux/mmio-mux.txt
create mode 100644 Documentation/devicetree/bindings/mux/reg-mux.txt
--
2.11.0
next reply other threads:[~2019-04-30 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 19:52 Peter Rosin [this message]
2019-04-30 19:52 ` [PATCH 1/2] dt-bindings: add register based devices' mux controller DT bindings Peter Rosin
2019-04-30 19:52 ` [PATCH 2/2] mux: mmio: add generic regmap bitfield-based multiplexer Peter Rosin
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=20190430195226.8965-1-peda@axentia.se \
--to=peda@axentia.se \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pankaj.bansal@nxp.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).