From: <Ryan.Wanner@microchip.com>
To: <ludovic.desroches@microchip.com>, <linus.walleij@linaro.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<claudiu.beznea@microchip.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <manikandan.M@microchip.com>,
Ryan Wanner <Ryan.Wanner@microchip.com>
Subject: [PATCH 2/2] pinctrl: at91: adding new macros
Date: Thu, 9 Feb 2023 08:45:44 -0700 [thread overview]
Message-ID: <20230209154544.535136-3-Ryan.Wanner@microchip.com> (raw)
In-Reply-To: <20230209154544.535136-1-Ryan.Wanner@microchip.com>
From: Ryan Wanner <Ryan.Wanner@microchip.com>
Adding macros for sama7g drive strength.
Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
---
include/dt-bindings/pinctrl/at91.h | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/include/dt-bindings/pinctrl/at91.h b/include/dt-bindings/pinctrl/at91.h
index e8e117306b1b..fd0a389b2a0f 100644
--- a/include/dt-bindings/pinctrl/at91.h
+++ b/include/dt-bindings/pinctrl/at91.h
@@ -42,8 +42,14 @@
#define AT91_PERIPH_C 3
#define AT91_PERIPH_D 4
-#define ATMEL_PIO_DRVSTR_LO 1
+#define ATMEL_PIO_DRVSTR_LO_0 0
+#define ATMEL_PIO_DRVSTR_LO_1 1
#define ATMEL_PIO_DRVSTR_ME 2
#define ATMEL_PIO_DRVSTR_HI 3
+#define ATMEL_PIO_DRVSTR_LO_D 0
+#define ATMEL_PIO_DRVSTR_HI_A 1
+#define ATMEL_PIO_DRVSTR_LO_C 2
+#define ATMEL_PIO_DRVSTR_LO_B 3
+
#endif /* __DT_BINDINGS_AT91_PINCTRL_H__ */
--
2.37.2
next prev parent reply other threads:[~2023-02-09 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:45 [PATCH 0/2] pinctrl: Sama7g5 drive strength options updated Ryan.Wanner
2023-02-09 15:45 ` [PATCH 1/2] pinctrl: at91-pio4: Implement the correct drive values for sama7g5 Ryan.Wanner
2023-02-09 15:45 ` Ryan.Wanner [this message]
2023-02-09 15:50 ` [PATCH 2/2] pinctrl: at91: adding new macros Krzysztof Kozlowski
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=20230209154544.535136-3-Ryan.Wanner@microchip.com \
--to=ryan.wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=manikandan.M@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
/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