From: Nishanth Menon <nm@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<a-nandan@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<eblanc@baylibre.com>, <jneanne@baylibre.com>,
<aseketeli@baylibre.com>, <jpanis@baylibre.com>,
<u-kumar1@ti.com>, <j-luthra@ti.com>, <vaishnav.a@ti.com>,
<hnagalla@ti.com>, <devarsht@ti.com>
Subject: Re: [PATCH v7 0/4] Add TPS6594 PMIC support on several boards
Date: Thu, 23 Nov 2023 01:24:02 -0600 [thread overview]
Message-ID: <20231123072402.2pscgotxhc6mffe2@carnivore> (raw)
In-Reply-To: <20231122104513.2335757-1-n-francis@ti.com>
On 16:15-20231122, Neha Malcom Francis wrote:
> TPS6594 is a Power Management IC which provides regulators and others
> features like GPIOs, RTC, watchdog, ESMs (Error Signal Monitor), and
> PFSM (Pre-configurable Finite State Machine). The SoC and the PMIC can
> communicate through the I2C or SPI interfaces.
> TPS6594 is the super-set device while TPS6593 and LP8764 are derivatives.
>
> This series adds device tree nodes for TI TPS6594 PMICs found in the
> following boards:
> - J721EXSOMXEVM:
> Link: https://www.ti.com/tool/J721EXSOMXEVM
> - J721S2XSOMXEVM:
> Link: https://www.ti.com/tool/J721S2XSOMXEVM
> - J7200XSOMXEVM:
> Link: https://www.ti.com/tool/J7200XSOMXEVM
> - J784S4XEVM
> Link: https://www.ti.com/tool/J784S4XEVM
>
> Boot Logs:
> https://gist.github.com/nehamalcom/384cf594e37739a34f8a08664830e37a
>
> ---
> Changes from v6:
> https://lore.kernel.org/all/20230810-tps6594-v6-0-2b2e2399e2ef@ti.com/
> - Modify patch series to include only patches not merged (J7)
> - Add boot logs for all affected boards
So what changed for j721s2?
https://lore.kernel.org/all/20230810024700.4qhgygd6mma4sw2u@kobold/
And, there is no defconfig patch? Then how did the test work? if you
have done local .config changes, that should have been defconfig patch.
Also did you audit the SKs to make sure they don't need this?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-23 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 10:45 [PATCH v7 0/4] Add TPS6594 PMIC support on several boards Neha Malcom Francis
2023-11-22 10:45 ` [PATCH v7 1/4] arm64: dts: ti: k3-j7200-som-p0: Add TP6594 family PMICs Neha Malcom Francis
2023-11-22 10:45 ` [PATCH v7 2/4] arm64: dts: ti: k3-j721s2-som-p0: " Neha Malcom Francis
2023-11-22 10:45 ` [PATCH v7 3/4] arm64: dts: ti: k3-j721e-som-p0: " Neha Malcom Francis
2023-11-22 10:45 ` [PATCH v7 4/4] arm64: dts: ti: k3-j784s4-evm: Add support for TPS6594 PMIC Neha Malcom Francis
2023-11-23 7:24 ` Nishanth Menon [this message]
2023-11-23 7:29 ` [PATCH v7 0/4] Add TPS6594 PMIC support on several boards Neha Malcom Francis
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=20231123072402.2pscgotxhc6mffe2@carnivore \
--to=nm@ti.com \
--cc=a-nandan@ti.com \
--cc=aseketeli@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=eblanc@baylibre.com \
--cc=hnagalla@ti.com \
--cc=j-luthra@ti.com \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@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