Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: <linusw@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <nm@ti.com>, <vigneshr@ti.com>,
	<kristo@kernel.org>, <brgl@kernel.org>
Cc: <linux-gpio@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<y-abhilashchandra@ti.com>, <afd@ti.com>, <u-kumar1@ti.com>
Subject: [PATCH 3/3] arm64: dts: ti: Add TDA54 pinctrl header
Date: Wed, 30 Sep 2026 14:50:20 +0530	[thread overview]
Message-ID: <20260930092020.1047221-4-y-abhilashchandra@ti.com> (raw)
In-Reply-To: <20260930092020.1047221-1-y-abhilashchandra@ti.com>

Add TDA54_PINMUX() and the mux mode defines for use by TDA54 device tree
sources to build pinmux values.

Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
---
Note: I understand that this patch goes through the SoC tree, but is
included here to give reviewers the full context.

 arch/arm64/boot/dts/ti/k3-tda54-pinctrl.h | 29 +++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-tda54-pinctrl.h

diff --git a/arch/arm64/boot/dts/ti/k3-tda54-pinctrl.h b/arch/arm64/boot/dts/ti/k3-tda54-pinctrl.h
new file mode 100644
index 000000000000..a3e730e103ae
--- /dev/null
+++ b/arch/arm64/boot/dts/ti/k3-tda54-pinctrl.h
@@ -0,0 +1,29 @@
+/* SPDX-License-Identifier: GPL-2.0-only OR MIT */
+/*
+ * This header provides constants for TI's TDA54 SoC device tree sources.
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/
+ */
+#ifndef DTS_ARM64_TI_K3_TDA54_PINCTRL_H
+#define DTS_ARM64_TI_K3_TDA54_PINCTRL_H
+
+#define TDA54_PINMUX(pad, mux)		(((pad) << 8) | ((mux) & 0xf))
+
+#define TDA54_MUX_MODE0		0
+#define TDA54_MUX_MODE1		1
+#define TDA54_MUX_MODE2		2
+#define TDA54_MUX_MODE3		3
+#define TDA54_MUX_MODE4		4
+#define TDA54_MUX_MODE5		5
+#define TDA54_MUX_MODE6		6
+#define TDA54_MUX_MODE7		7
+#define TDA54_MUX_MODE8		8
+#define TDA54_MUX_MODE9		9
+#define TDA54_MUX_MODE10		10
+#define TDA54_MUX_MODE11		11
+#define TDA54_MUX_MODE12		12
+#define TDA54_MUX_MODE13		13
+#define TDA54_MUX_MODE14		14
+#define TDA54_MUX_MODE15		15
+
+#endif
-- 
2.34.1



      parent reply	other threads:[~2026-09-30  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  9:20 [PATCH 0/3] Add pin controller support for TI TDA54 SoC Yemike Abhilash Chandra
2026-09-30  9:20 ` [PATCH 1/3] dt-bindings: pinctrl: Add TI TDA54 pin controller Yemike Abhilash Chandra
2026-10-01 21:10   ` Linus Walleij
2026-10-01 21:26     ` Conor Dooley
2026-09-30  9:20 ` [PATCH 2/3] pinctrl: ti: Add TDA54 pin controller driver Yemike Abhilash Chandra
2026-10-01 20:52   ` Linus Walleij
2026-09-30  9:20 ` Yemike Abhilash Chandra [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=20260930092020.1047221-4-y-abhilashchandra@ti.com \
    --to=y-abhilashchandra@ti.com \
    --cc=afd@ti.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=u-kumar1@ti.com \
    --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