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: <AM0PR04MB4211F835E34473C57C1B7C8480C80@AM0PR04MB4211.eurprd04.prod.outlook.com>
Date:   Thu, 18 Jul 2019 11:56:39 +0000
From:   Aisheng Dong <aisheng.dong@....com>
To:     Daniel Baluta <daniel.baluta@....com>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>
CC:     "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
        "=kernel@...gutronix.de" <=kernel@...gutronix.de>,
        "festevam@...il.com" <festevam@...il.com>,
        dl-linux-imx <linux-imx@....com>,
        "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "S.j. Wang" <shengjiu.wang@....com>,
        Paul Olaru <paul.olaru@....com>,
        Daniel Baluta <daniel.baluta@....com>
Subject: RE: [PATCH v2 2/3] firmware: imx: scu-pd: Add mu13 b side PD range

> From: Daniel Baluta <daniel.baluta@....com>
> Sent: Thursday, July 18, 2019 6:25 PM
> 
> LSIO subsystem contains 14 MU instances.
> 
> 5 MUs to communicate between AP <-> SCU
>   - side-A PD range managed by AP
>   - side-B PD range managed by SCU
> 
> 9 MUs to communicate between all cores (AP/M4/DSP).
>   - side-A PD range managed by core-A (AP/M4/DSP)
>   - side-B PD range managed by core-B (AP/M4/DSP).
> 
> Communication between AP <-> DSP is done through the assigned MU number
> 13.
> 
> So, we power up side-A by the AP and we decide to power up side-B also from
> AP. This is because powering it up from DSP would be painful.
> 
> Powering up side B from DSP would require the DSP to communicate with SCU
> and to keep things simple we don't want that now.
> 
> Signed-off-by: Daniel Baluta <daniel.baluta@....com>

Reviewed-by: Dong Aisheng <aisheng.dong@....com>

Regards
Aisheng

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ