On 10/30/2015 1:07 PM, Peter Maydell wrote: > On 30 October 2015 at 18:28, Rob Herring <robh+dt@xxxxxxxxxx> wrote: >> On Thu, Oct 29, 2015 at 9:01 AM, Peter Maydell <peter.maydell@xxxxxxxxxx> wrote: >>> +Valid Secure world properties: >>> + >>> +- secure-status : specifies whether the device is present and usable >>> + in the secure world. The combination of this with "status" allows >>> + the various possible combinations of device visibility to be >>> + specified: >>> + status = "okay"; // visible in S and NS >> >> I assume neither property present or both okay also mean the same. >> >> status = "okay"; secure-status = "okay"; >> >> We should be explicit. > > Yes; status defaults to "okay" (presumably this is listed in > the overal DT binding spec somewhere), Valid values for the "status" property do not seem to be well documented for Linux. The code, __of_device_is_available(), implements: value of "okay" returns true value of "ok" returns true status property does not exist returns true (thus defaults to true) anything else returns false. Eight individual bindings define the status property (I'll put them on my todo list to remove since they should be inherited). The status property should be in a top level binding, which should be created as part of the bindings documentation cleanup. I'll watch for it to get created or do it myself. (Lots of bindings show examples of using the status property in their examples -- that is fine.) ePAPR v1.1, section "2.3.4 status" does not list "ok", but does list: "okay" "disabled" "fail" "fail-sss" < snip > -Frank -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
