Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 9 Feb 2022 07:24:13 -0600
From:   Nishanth Menon <nm@ti.com>
To:     Hari Nagalla <hnagalla@ti.com>
CC:     <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <vigneshr@ti.com>, <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64: Add ESM0 to device memory map
Message-ID: <20220209132413.u5staibdmxegrxul@outfit>
References: <20220208182119.24707-1-hnagalla@ti.com>
 <20220209003519.clokfvln7m2deewi@buddhism>
 <c29de523-021a-d139-17ca-3ba8884e50ce@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <c29de523-021a-d139-17ca-3ba8884e50ce@ti.com>
User-Agent: NeoMutt/20171215
Precedence: bulk

On 19:18-20220208, Hari Nagalla wrote:
> On 2/8/22 18:35, Nishanth Menon wrote:
> > > AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
> > > other in MCU voltage domain. The error output from Main ESM module can
> > > be routed to the MCU ESM module. The error output of MCU ESM can be
> > > configured to reset the device.
> > So what happens to the window for MCU ESM - Is that already open?
> > 
> Yes, the cbass mcu window already opens MCU ESM address space.

Please add that in the comments to making sure there is no confusion.

> 
> I will loop in LAKML as well..

Thanks.
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D