From: Theo Debrouwere <theo.debrouwere@gmail.com>
To: linux-amlogic@lists.infradead.org
Cc: Theo Debrouwere <theo.debrouwere@faytech.de>
Subject: [PATCH 1/2] pinctrl: meson-g12a: add pwm_d option
Date: Thu, 5 Sep 2024 17:29:50 +0200 [thread overview]
Message-ID: <20240905152951.83481-1-theo.debrouwere@faytech.de> (raw)
Add missing PWM_D pin muxing for GPIOA_4.
Signed-off-by: Theo Debrouwere <theo.debrouwere@faytech.de>
---
drivers/pinctrl/meson/pinctrl-meson-g12a.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/meson/pinctrl-meson-g12a.c b/drivers/pinctrl/meson/pinctrl-meson-g12a.c
index 32830269a5b4..6d927abbf8d0 100644
--- a/drivers/pinctrl/meson/pinctrl-meson-g12a.c
+++ b/drivers/pinctrl/meson/pinctrl-meson-g12a.c
@@ -277,6 +277,7 @@ static const unsigned int pwm_c_x5_pins[] = { GPIOX_5 };
static const unsigned int pwm_c_x8_pins[] = { GPIOX_8 };
/* pwm_d */
+static const unsigned int pwm_d_a4_pins[] = { GPIOA_4 };
static const unsigned int pwm_d_x3_pins[] = { GPIOX_3 };
static const unsigned int pwm_d_x6_pins[] = { GPIOX_6 };
@@ -773,6 +774,7 @@ static struct meson_pmx_group meson_g12a_periphs_groups[] = {
GROUP(mclk0_a, 1),
GROUP(mclk1_a, 2),
GROUP(pwm_f_a, 3),
+ GROUP(pwm_d_a4, 3),
};
/* uart_ao_a */
@@ -1066,7 +1068,7 @@ static const char * const pwm_c_groups[] = {
};
static const char * const pwm_d_groups[] = {
- "pwm_d_x3", "pwm_d_x6",
+ "pwm_d_x3", "pwm_d_x6", "pwm_d_a4",
};
static const char * const pwm_e_groups[] = {
--
2.45.2
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2024-09-05 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 15:29 Theo Debrouwere [this message]
2024-09-05 15:29 ` [PATCH 2/2] arm64: dts: meson-g12-common: " Theo Debrouwere
2024-09-09 20:34 ` Martin Blumenstingl
2024-09-09 20:31 ` [PATCH 1/2] pinctrl: meson-g12a: " Martin Blumenstingl
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=20240905152951.83481-1-theo.debrouwere@faytech.de \
--to=theo.debrouwere@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=theo.debrouwere@faytech.de \
/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
all inboxes | Powered by JetHome®