linux-kernel - Re: [PATCH V3 1/8] drivers: Add boot constraints core

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: <20170904091522.GA2816@ubuntu>
Date:   Mon, 4 Sep 2017 11:15:47 +0200
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Vincent Guittot <vincent.guittot@...aro.org>,
        Mark Brown <broonie@...nel.org>,
        Stephen Boyd <sboyd@...eaurora.org>,
        Rajendra Nayak <rnayak@...eaurora.org>,
        Shiraz Hashim <shashim@...eaurora.org>,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        robdclark@...il.com
Subject: Re: [PATCH V3 1/8] drivers: Add boot constraints core

On 29-08-17, 14:03, Greg Kroah-Hartman wrote:
> Who couldn't reach an agreement?

Rob Herring (DT Maintainer) didn't like the first set of bindings and wasn't
convinced that we need any new bindings for this purpose to begin with.

> So you gave up and decided to make a
> whole bunch of kernel code instead of just using new DT entries?  That's
> crazy...

Its not a lot really. Most of the code is anyways required, the only extra part
is the platform specific drivers, which are replacing what the DT would have
done. So, it shouldn't be that big of a deal I suppose.

> Let's see a working system or two first here please.

Sure, I will get as many converted as possible.

> But you are implying that existing handheld devices need this problem
> solved, how do they do it today without this code as obviously they are
> shipping working solutions.

So yeah, LCD is a common usecase but the configurations aren't always shared. It
may not be an issue with private clock/regulator resources, but with shared
ones.

Though even with the private resources, we may want the clock/domains/regulators
to stay powered on and I assume that the platforms would be doing hacky stuff to
get that all working right now.

-- 
viresh