lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c29de523-021a-d139-17ca-3ba8884e50ce@ti.com>
Date:   Tue, 8 Feb 2022 19:18:54 -0600
From:   Hari Nagalla <hnagalla@...com>
To:     Nishanth Menon <nm@...com>
CC:     <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <vigneshr@...com>, <robh+dt@...nel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64: Add ESM0 to device memory map

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ