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: <13B9B4C6EF24D648824FF11BE89671620376DEB7A5@dlee02.ent.ti.com>
Date:	Wed, 28 Jan 2009 20:21:18 -0600
From:	"Woodruff, Richard" <r-woodruff2@...com>
To:	Paul Walmsley <paul@...an.com>,
	"linux-arm-kernel@...ts.arm.linux.org.uk" 
	<linux-arm-kernel@...ts.arm.linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	Tony Lindgren <tony@...mide.com>
Subject: RE: [PATCH B 06/10] OMAP3 pwrdm: add CORE SAR handling (for USBTLL
 module)

> 34xx TRM Delta G->H notes that the CORE powerdomain has a hardware
> save-and-restore (SAR) control bit for the USBTLL module, similar to
> the USBHOST powerdomain SAR bit.  Split the existing core_34xx struct
> powerdomain into two structs, one for ES1 and one for ES2, and add the
> PWRDM_HAS_HDWR_SAR flag to the ES2 powerdomain.
>
> Signed-off-by: Paul Walmsley <paul@...an.com>
> Signed-off-by: Tony Lindgren <tony@...mide.com>
> +
> +/* No wkdeps or sleepdeps for 34xx core apparently */
> +static struct powerdomain core_34xx_es2_pwrdm = {
> +     .name             = "core_pwrdm",
> +     .prcm_offs        = CORE_MOD,
> +     .omap_chip        = OMAP_CHIP_INIT(CHIP_IS_OMAP3430ES2),
>       .pwrsts           = PWRSTS_OFF_RET_ON,
>       .dep_bit          = OMAP3430_EN_CORE_SHIFT,
> +     .flags            = PWRDM_HAS_HDWR_SAR, /* for USBTLL only */
>       .banks            = 2,
>       .pwrsts_mem_ret   = {
>               [0] = PWRSTS_OFF_RET,    /* MEM1RETSTATE */

TLLSAR is not functional till ES3.1 (and beyound).  Is it possible to flag it this way?

If you try and use it your system will deadlock on 2nd OFF mode transition due to hardware bug.

Regards,
Richard W.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ