From: Chintan Vankar <c-vankar@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Peter Rosin <peda@axentia.se>,
<tglx@linutronix.de>, <gregkh@linuxfoundation.org>,
<vigneshr@ti.com>, <nm@ti.com>, <s-vadapalli@ti.com>,
<danishanwar@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<c-vankar@ti.com>
Subject: [RFC PATCH 0/2] Extend mmio-mux driver to configure mux with
Date: Fri, 28 Feb 2025 01:52:04 +0530 [thread overview]
Message-ID: <20250227202206.2551305-1-c-vankar@ti.com> (raw)
This series extends mmio-mux driver's capability to configure driver in
with extended property.
In current driver implementation, driver is parsing register's offset,
mask and value from two different device tree property which makes it
complex to specify a specific register or set of registers. Introducing
mux-reg-masks-states will make it easier to specify the same values for
particular register or set of registers.
This series is based on linux next tagged next-20250227.
Chintan Vankar (2):
devicetree: bindings: mux: reg-mux: Update bindings for reg-mux for
new property
mux: mmio: Extend mmio-mux driver to configure mux with new DT
property
.../devicetree/bindings/mux/reg-mux.yaml | 29 +++-
drivers/mux/mmio.c | 148 +++++++++++++++---
2 files changed, 149 insertions(+), 28 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-27 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 20:22 Chintan Vankar [this message]
2025-02-27 20:22 ` [RFC PATCH 1/2] devicetree: bindings: mux: reg-mux: Update bindings for reg-mux for new property Chintan Vankar
2025-02-27 21:26 ` Andrew Davis
2025-02-28 18:52 ` Conor Dooley
2025-02-28 21:38 ` Vankar, Chintan
2025-03-03 16:58 ` Conor Dooley
2025-03-03 18:45 ` Vankar, Chintan
2025-02-27 20:22 ` [RFC PATCH 2/2] mux: mmio: Extend mmio-mux driver to configure mux with new DT property Chintan Vankar
2025-02-27 21:39 ` Andrew Davis
2025-03-04 5:16 ` Vankar, Chintan
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=20250227202206.2551305-1-c-vankar@ti.com \
--to=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=tglx@linutronix.de \
--cc=vigneshr@ti.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