linux-kernel - Re: [PATCH] soc: ti: pm33xx: Enable DS0 for the platforms on which it is functional

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: <20180822142220.GG7523@atomide.com>
Date:   Wed, 22 Aug 2018 07:22:20 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     "J, KEERTHY" <j-keerthy@...com>
Cc:     Johan Hovold <johan@...nel.org>, d-gerlach@...com,
        linux-kernel@...r.kernel.org, t-kristo@...com, ssantosh@...nel.org,
        linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] soc: ti: pm33xx: Enable DS0 for the platforms on which
 it is functional

* J, KEERTHY <j-keerthy@...com> [180822 11:11]:
> On 8/22/2018 2:13 PM, Johan Hovold wrote:
> > Yes, and a blacklist would make much more sense for something like this
> > if where talking about specific boards.
>
> Black list is easier here?

After thinking about this a bit more I think the boards supporting
deep sleep should add a PM related dts property to enable deep sleep.

The board maintainers need to test and verify deep sleep for each
board, it's not something that just works for the SoC in general.
Some boards may use different powering for things like DDR where
it's power might be controlled by a GPIO regulator. And in some
cases deeper idle states may depend also on the PMIC being used.

Maybe we already have some dts property we can use to describe
the idle states the board hardware supports?

Regards,

Tony