linux-kernel - Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

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]

Date:   Fri, 9 Sep 2016 10:10:55 -0400
From:   Tom Rini <trini@...sulko.com>
To:     Rob Herring <robh+dt@...nel.org>
Cc:     Frank Rowand <frowand.list@...il.com>,
        Tony Lindgren <tony@...mide.com>,
        Grant Likely <grant.likely@...aro.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-omap <linux-omap@...r.kernel.org>,
        Nishanth Menon <nm@...com>, Tero Kristo <t-kristo@...com>
Subject: Re: [PATCHv2] of: Add generic handling for ePAPR 1.1 fail-sss states

On Thu, Sep 08, 2016 at 09:43:03PM -0500, Rob Herring wrote:
> On Thu, Sep 8, 2016 at 2:05 PM, Frank Rowand <frowand.list@...il.com> wrote:
> > On 09/08/16 06:38, Rob Herring wrote:
> >> On Wed, Aug 31, 2016 at 4:41 PM, Tony Lindgren <tony@...mide.com> wrote:
> >>> * Frank Rowand <frowand.list@...il.com> [160831 13:51]:
[snip]
> >>>> Why not just create a new property that describes the hardware?
> >>>> Perhaps something like:
> >>>>
> >>>>    incomplete = "pins_output", "buggy_dma";
> >>>
> >>> New property for incomplete works for me. Rob, got any comments here?
> >>
> >> Pins not muxed out or connected on the board has to be the #1 reason
> >> for disabled status. I don't think we need or want another way to
> >> express that.
> >
> > How is that expressed now?
> 
> status = "disabled";

It might be worth repeating that the problem that needs to be solved is
that we have an IP block that exists in some sense but needs to be shut
down (or some similar case the driver can handle) rather than ignored
like today.  This is not the same as having 5 UARTs available from the
SoC but only one is actually in some useful physical state, so list all
5 in the dtsi, status disabled, and then in the board dts file enable
the exposed ones.

-- 
Tom