From: Rob Herring <robh@kernel.org>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: nm@ti.com, vigneshr@ti.com, kristo@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-pinctrl: Introduce deep sleep macros
Date: Fri, 15 Nov 2024 09:48:22 -0600 [thread overview]
Message-ID: <20241115154822.GA2954187-robh@kernel.org> (raw)
In-Reply-To: <20241112115650.988943-2-s-vadapalli@ti.com>
On Tue, Nov 12, 2024 at 05:26:49PM +0530, Siddharth Vadapalli wrote:
> The behavior of pins in deep sleep mode can be configured by programming
> the corresponding bits in the respective Pad Configuration register. Add
> macros to support this.
>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-pinctrl.h | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-pinctrl.h b/arch/arm64/boot/dts/ti/k3-pinctrl.h
> index 22b8d73cfd32..cac7cccc1112 100644
> --- a/arch/arm64/boot/dts/ti/k3-pinctrl.h
> +++ b/arch/arm64/boot/dts/ti/k3-pinctrl.h
> @@ -12,6 +12,12 @@
> #define PULLTYPESEL_SHIFT (17)
> #define RXACTIVE_SHIFT (18)
> #define DEBOUNCE_SHIFT (11)
> +#define FORCE_DS_EN_SHIFT (15)
> +#define DS_EN_SHIFT (24)
> +#define DS_OUT_DIS_SHIFT (25)
> +#define DS_OUT_VAL_SHIFT (26)
> +#define DS_PULLUD_EN_SHIFT (27)
> +#define DS_PULLTYPE_SEL_SHIFT (28)
>
> #define PULL_DISABLE (1 << PULLUDEN_SHIFT)
> #define PULL_ENABLE (0 << PULLUDEN_SHIFT)
> @@ -38,6 +44,19 @@
> #define PIN_DEBOUNCE_CONF5 (5 << DEBOUNCE_SHIFT)
> #define PIN_DEBOUNCE_CONF6 (6 << DEBOUNCE_SHIFT)
>
> +#define PIN_DS_FORCE_DISABLE (0 << FORCE_DS_EN_SHIFT)
> +#define PIN_DS_FORCE_ENABLE (1 << FORCE_DS_EN_SHIFT)
> +#define PIN_DS_IO_OVERRIDE_DISABLE (0 << DS_IO_OVERRIDE_EN_SHIFT)
> +#define PIN_DS_IO_OVERRIDE_ENABLE (1 << DS_IO_OVERRIDE_EN_SHIFT)
> +#define PIN_DS_OUT_ENABLE (0 << DS_OUT_DIS_SHIFT)
> +#define PIN_DS_OUT_DISABLE (1 << DS_OUT_DIS_SHIFT)
> +#define PIN_DS_OUT_VALUE_ZERO (0 << DS_OUT_VAL_SHIFT)
> +#define PIN_DS_OUT_VALUE_ONE (1 << DS_OUT_VAL_SHIFT)
> +#define PIN_DS_PULLUD_ENABLE (0 << DS_PULLUD_EN_SHIFT)
> +#define PIN_DS_PULLUD_DISABLE (1 << DS_PULLUD_EN_SHIFT)
> +#define PIN_DS_PULL_DOWN (0 << DS_PULLTYPE_SEL_SHIFT)
> +#define PIN_DS_PULL_UP (1 << DS_PULLTYPE_SEL_SHIFT)
Are you going to go add the 0 defines to all the existing cases? If you
do, it's a lot of pointless churn. If you don't, then it is inconsistent
when they do get used. I would drop them all.
Rob
next prev parent reply other threads:[~2024-11-15 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 11:56 [PATCH 0/2] Add Deep Sleep pinmux macros for TI's K3 SoCs Siddharth Vadapalli
2024-11-12 11:56 ` [PATCH 1/2] arm64: dts: ti: k3-pinctrl: Introduce deep sleep macros Siddharth Vadapalli
2024-11-15 15:48 ` Rob Herring [this message]
2024-11-18 5:19 ` Siddharth Vadapalli
2024-11-12 11:56 ` [PATCH 2/2] arm64: dts: ti: k3-am62x-sk-common: Support SoC wakeup using USB1 wakeup Siddharth Vadapalli
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=20241115154822.GA2954187-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-vadapalli@ti.com \
--cc=srk@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;
as well as URLs for NNTP newsgroup(s).