From: "Sharma, Rahul" <r-sharma3@ti.com>
To: <peda@axentia.se>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC uL PATCH 0/2] Add TI's event mux router driver and build
Date: Fri, 13 Mar 2026 12:05:22 +0530 [thread overview]
Message-ID: <f55b008a-ad34-4fee-ae7f-eefec8629bb8@ti.com> (raw)
In-Reply-To: <20260313060437.3704592-1-r-sharma3@ti.com>
Hi,
A note point for this patch series,
1) Subject prefix has "uL" which means upstream Linux. This got added by
mistake.
2) In both the patches of this series the commit header should use "mux"
instead of "mux-controller".
I will correct above but would wait for 1st round of comments before
re-spin.
BR,
Rahul
On 3/13/2026 11:34 AM, Rahul Sharma wrote:
> This series contains the event mux router support present in TI's K3
> platforms. The event mux router are of 2 types
> 1) gpio-mux router
> 2) timesync router
>
> In normal scenarios, GPIO signals are received by CPU via GIC, but the
> gpio mux router routes the incoming GPIO signal to BCDMA(Block copy
> DMA) which the DMA upon receiving uses as HW triger to perform a single
> block transfer or as configured.
>
> Time sync router does the same but for the time synchronization based
> events.
>
> This driver supports both the routers but this patch series adds support
> only for GPIO-mux router.
>
> Rahul Sharma (2):
> dt-bindings: mux-controller: ti: add binding for event mux router
> mux-controller: ti: add driver for event mux router
>
> .../mux/ti,am62l-event-mux-router.yaml | 79 ++++++
> drivers/mux/Kconfig | 15 ++
> drivers/mux/Makefile | 2 +
> drivers/mux/ti-k3-event-mux.c | 235 ++++++++++++++++++
> 4 files changed, 331 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mux/ti,am62l-event-mux-router.yaml
> create mode 100644 drivers/mux/ti-k3-event-mux.c
>
prev parent reply other threads:[~2026-03-13 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 6:04 [RFC uL PATCH 0/2] Add TI's event mux router driver and build Rahul Sharma
2026-03-13 6:04 ` [RFC uL PATCH 1/2] dt-bindings: mux-controller: ti: add binding for event mux router Rahul Sharma
2026-03-13 6:04 ` [RFC uL PATCH 2/2] mux-controller: ti: add driver " Rahul Sharma
2026-03-13 6:35 ` Sharma, Rahul [this message]
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=f55b008a-ad34-4fee-ae7f-eefec8629bb8@ti.com \
--to=r-sharma3@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--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