Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <c29de523-021a-d139-17ca-3ba8884e50ce@ti.com>
Date:   Tue, 8 Feb 2022 19:18:54 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: [PATCH] arm64: dts: ti: k3-am64: Add ESM0 to device memory map
Content-Language: en-US
To:     Nishanth Menon <nm@ti.com>
CC:     <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <vigneshr@ti.com>, <robh+dt@kernel.org>
References: <20220208182119.24707-1-hnagalla@ti.com>
 <20220209003519.clokfvln7m2deewi@buddhism>
From:   Hari Nagalla <hnagalla@ti.com>
In-Reply-To: <20220209003519.clokfvln7m2deewi@buddhism>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.

I will loop in LAKML as well..

Thanks