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] [day] [month] [year] [list]
Message-ID: <20220209132413.u5staibdmxegrxul@outfit>
Date:   Wed, 9 Feb 2022 07:24:13 -0600
From:   Nishanth Menon <nm@...com>
To:     Hari Nagalla <hnagalla@...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 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ