[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <94ab71e1-2e68-def2-95b8-33162172f65c@axentia.se>
Date: Sun, 2 Jan 2022 23:34:12 +0100
From: Peter Rosin <peda@...ntia.se>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Aswath Govindraju <a-govindraju@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: mux for 5.17-rc1
Hi Greg,
These have been in -next since around x-mas, and hopefully it's not too
late to push them for the upcoming window.
Patch 5/6 fails check-patch due to lacking a message body, because I
forgot to actually check that and now I can't find it in me to re-spin
for that seemingly insignificant issue. If it really is a no-no, then
please just drop that patch.
Also, I really would have liked to squash patch 6/6 into patch 3/6, but
I don't know how to retain credits properly if I do that. I did remove
the Fixes tag from 6/6, since the commit hash will be trash by the time
you make your commit. It was:
Fixes: xxxxxxxxxxxx ("mux: Add support for reading mux state from consumer DT node")
(In case you can find it in you to add it back with a proper hash.)
Anyway, the big change here is the new support for pointing at a
specific mux state from a device tree node.
Cheers,
Peter
Aswath Govindraju (3):
dt-bindings: ti-serdes-mux: Add defines for J721S2 SoC
dt-bindings: mux: Document mux-states property
mux: Add support for reading mux state from consumer DT node
Peter Rosin (2):
mux: add missing mux_state_get
mux: fix grammar, missing "is".
Yang Li (1):
mux: Fix struct mux_state kernel-doc comment
.../devicetree/bindings/mux/gpio-mux.yaml | 11 +-
.../devicetree/bindings/mux/mux-consumer.yaml | 21 ++
.../devicetree/bindings/mux/mux-controller.yaml | 26 ++-
Documentation/driver-api/driver-model/devres.rst | 1 +
drivers/mux/core.c | 241 +++++++++++++++++++--
include/dt-bindings/mux/ti-serdes.h | 22 ++
include/linux/mux/consumer.h | 20 ++
7 files changed, 317 insertions(+), 25 deletions(-)
Powered by blists - more mailing lists