Received-SPF: pass (google.com: domain of linux-kernel+bounces-54327-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
        Rob Herring
	<robh+dt@kernel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>, Tony
 Lindgren <tony@atomide.com>,
        Haojian Zhuang <haojian.zhuang@linaro.org>, Nishanth Menon <nm@ti.com>,
        Tero Kristo <kristo@kernel.org>,
        Thomas Richard
	<thomas.richard@bootlin.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>, <linux-gpio@vger.kernel.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <linux-omap@vger.kernel.org>,
        <thomas.petazzoni@bootlin.com>, <gregory.clement@bootlin.com>,
        <theo.lebrun@bootlin.com>, <u-kumar1@ti.com>
Subject: Re: (subset)[PATCH 0/3] pinctrl: pinctrl-single: fix suspend/resume on j7200
Date: Tue, 6 Feb 2024 10:13:03 +0530
Message-ID: <170719349987.2245010.13900750309896394285.b4-ty@ti.com>
In-Reply-To: <20231128-j7200-pinctrl-s2r-v1-0-704e7dc24460@bootlin.com>
References: <20231128-j7200-pinctrl-s2r-v1-0-704e7dc24460@bootlin.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Thomas Richard,

On Tue, 28 Nov 2023 16:34:58 +0100, Thomas Richard wrote:
> On j7200, during suspend to ram the SoC is powered-off. So the pinctrl
> contexts are lost.
> The flag PCS_CONTEXT_LOSS_OFF shall be set to restore the pinctrl
> contexts.
> 
> A new compatible (ti,j7200-padconf) was created to enable this flag only
> for j7200.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[3/3] arm64: dts: ti: k3-j7200: use ti,j7200-padconf compatible
      commit: 4eb42afed5d488c4707be5362e8e0f0771f5218e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh