From: Shawn Guo <shawnguo2@yeah.net>
To: maudspierings@gocontroll.com
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v6 2/8] arm64: dts: imx8mp: Add pinctrl config definitions
Date: Fri, 9 May 2025 16:05:52 +0800 [thread overview]
Message-ID: <aB23YOkCMnA4F3hV@dragon> (raw)
In-Reply-To: <20250417-initial_display-v6-2-3c6f6d24c7af@gocontroll.com>
On Thu, Apr 17, 2025 at 12:14:03PM +0200, Maud Spierings via B4 Relay wrote:
> From: Maud Spierings <maudspierings@gocontroll.com>
>
> Currently to configure each IOMUXC_SW_PAD_CTL_PAD the raw value of this
> register is written in the dts, these values are not obvious. Add defines
> which describe the fields of this register which can be or-ed together to
> produce readable settings.
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Maud Spierings <maudspierings@gocontroll.com>
> ---
> This patch has already been sent in a different group of patches: [1]
> It was requested there to submit it along with a user, this series also
> includes some users for it.
>
> [1]: https://lore.kernel.org/all/20250218-pinctrl_defines-v2-2-c554cad0e1d2@gocontroll.com/
> ---
> arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h | 33 ++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h b/arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h
> index 0fef066471ba607be02d0ab15da5a048a8a213a7..19a23d148246f4fb990050a9d06d20b6e769f254 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h
> @@ -6,6 +6,39 @@
> #ifndef __DTS_IMX8MP_PINFUNC_H
> #define __DTS_IMX8MP_PINFUNC_H
>
> +/* Drive Strength */
> +#define MX8MP_DSE_X1 0x0
> +#define MX8MP_DSE_X2 0x4
> +#define MX8MP_DSE_X4 0x2
> +#define MX8MP_DSE_X6 0x6
> +
> +/* Slew Rate */
> +#define MX8MP_FSEL_FAST 0x10
> +#define MX8MP_FSEL_SLOW 0x0
> +
> +/* Open Drain */
> +#define MX8MP_ODE_ENABLE 0x20
> +#define MX8MP_ODE_DISABLE 0x0
> +
> +#define MX8MP_PULL_DOWN 0x0
> +#define MX8MP_PULL_UP 0x40
> +
> +/* Hysteresis */
> +#define MX8MP_HYS_CMOS 0x0
> +#define MX8MP_HYS_SCHMITT 0x80
> +
> +#define MX8MP_PULL_ENABLE 0x100
> +#define MX8MP_PULL_DISABLE 0x0
> +
> +/* SION force input mode */
> +#define MX8MP_SION 0x40000000
Can we have all these indents aligned on the same column using tabs?
> +
> +/* long defaults */
> +#define MX8MP_USDHC_DATA_DEFAULT (MX8MP_FSEL_FAST | MX8MP_PULL_UP | \
> + MX8MP_HYS_SCHMITT | MX8MP_PULL_ENABLE)
Can we indent like this?
#define MX8MP_USDHC_DATA_DEFAULT (MX8MP_FSEL_FAST | MX8MP_PULL_UP | \
MX8MP_HYS_SCHMITT | MX8MP_PULL_ENABLE)
Shawn
> +#define MX8MP_I2C_DEFAULT (MX8MP_DSE_X6 | MX8MP_PULL_UP | MX8MP_HYS_SCHMITT | \
> + MX8MP_PULL_ENABLE | MX8MP_SION)
> +
> /*
> * The pin function ID is a tuple of
> * <mux_reg conf_reg input_reg mux_mode input_val>
>
> --
> 2.49.0
>
>
next prev parent reply other threads:[~2025-05-09 8:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 10:14 [PATCH v6 0/8] arm64: dts: freescale: Add support for the GOcontroll Moduline Display Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-04-17 10:14 ` [PATCH v6 1/8] dt-bindings: arm: fsl: Add " Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-04-17 10:14 ` [PATCH v6 2/8] arm64: dts: imx8mp: Add pinctrl config definitions Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-05-09 8:05 ` Shawn Guo [this message]
2025-04-17 10:14 ` [PATCH v6 3/8] MAINTAINERS: add maintainer for the Ka-Ro tx8p-ml81 COM module Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-05-09 8:17 ` Shawn Guo
2025-05-09 8:42 ` Maud Spierings | GOcontroll
2025-05-09 8:58 ` Shawn Guo
2025-05-09 9:03 ` Maud Spierings | GOcontroll
2025-05-21 20:39 ` Ahmad Fatoum
2025-05-22 6:19 ` Krzysztof Kozlowski
2025-05-22 7:36 ` Ahmad Fatoum
2025-04-17 10:14 ` [PATCH v6 4/8] MAINTAINERS: add maintainer for the GOcontroll Moduline controllers Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-04-17 10:14 ` [PATCH v6 5/8] arm64: dts: freescale: add Ka-Ro Electronics tx8p-ml81 COM Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-05-09 8:13 ` Shawn Guo
2025-04-17 10:14 ` [PATCH v6 6/8] arm64: dts: freescale: Add the GOcontroll Moduline Display baseboard Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-04-17 10:14 ` [PATCH v6 7/8] arm64: dts: freescale: Add the BOE av101hdt-a10 variant of the Moduline Display Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
2025-04-17 10:14 ` [PATCH v6 8/8] arm64: dts: freescale: Add the BOE av123z7m-n17 " Maud Spierings
2025-04-17 10:14 ` Maud Spierings via B4 Relay
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=aB23YOkCMnA4F3hV@dragon \
--to=shawnguo2@yeah.net \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maudspierings@gocontroll.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.