From: Tony Lindgren <tony@atomide.com>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Dave Gerlach <d-gerlach@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation
Date: Tue, 26 Apr 2022 09:45:13 +0300 [thread overview]
Message-ID: <YmeU+aSxQdixAESi@atomide.com> (raw)
In-Reply-To: <YmI4rjkpX9krZAGn@x1>
* Drew Fustini <dfustini@baylibre.com> [220422 05:06]:
> Do you know what revision of the am437x-gp-evm that you have?
Not sure, it seems to be some early revision the last time I looked.
> The AM437X_GP_EVM_3K0006_SCHEMATIC_REV1_5B schematic [1] for the
> AM437x-GP-EVM shows that the EN pin on the TPS51200 is connected to SoC
> ball N25 which is GPIO5_7.
OK
> Unfortunately, the only AM437x board that I have is the AM437x IDK [2]
> which unfortunately does not have the TSP51200 EN pin connected to the
> the SoC. In addition, the am437x-gp-evm is the only board that is
> allowed to enable off mode due to am43xx_check_off_mode_enable() in
> arch/arm/mach-omap2/pm33xx-core.c
OK
Thanks,
Tony
> [1] https://www.ti.com/lit/zip/tidrc79
> [2] https://www.ti.com/lit/zip/sprr396
next prev parent reply other threads:[~2022-04-26 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 19:27 [PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation Drew Fustini
2022-04-14 19:27 ` [PATCH v3 1/2] dt-bindings: wkup-m3-ipc: Add ti,set-io-isolation property Drew Fustini
2022-04-14 19:44 ` Drew Fustini
2022-04-19 13:04 ` Rob Herring
2022-04-14 19:27 ` [PATCH v3 2/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation Drew Fustini
2022-04-21 6:56 ` [PATCH v3 0/2] " Tony Lindgren
2022-04-22 5:10 ` Drew Fustini
2022-04-26 6:45 ` Tony Lindgren [this message]
2022-05-03 13:08 ` (subset) " Nishanth Menon
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=YmeU+aSxQdixAESi@atomide.com \
--to=tony@atomide.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).