linux-kernel - Re: [PATCH v8 21/21] arm64: ACPI: additions of ACPI documentation for arm64

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:	Wed, 4 Feb 2015 18:12:29 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Al Stone <al.stone@...aro.org>
Cc:	Hanjun Guo <hanjun.guo@...aro.org>,
	Catalin Marinas <catalin.marinas@....com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	Mark Rutland <mark.rutland@....com>,
	Grant Likely <grant.likely@...aro.org>,
	Will Deacon <will.deacon@....com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	Graeme Gregory <graeme.gregory@...aro.org>,
	Sudeep Holla <Sudeep.Holla@....com>,
	Jon Masters <jcm@...hat.com>,
	Jason Cooper <jason@...edaemon.net>,
	Marc Zyngier <marc.zyngier@....com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Rob Herring <robh@...nel.org>,
	Robert Richter <rric@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Charles.Garcia-Tobin@....com, phoenix.liyi@...wei.com,
	Timur Tabi <timur@...eaurora.org>,
	Ashwin Chaugule <ashwinc@...eaurora.org>,
	suravee.suthikulpanit@....com,
	Mark Langsdorf <mlangsdo@...hat.com>, wangyijing@...wei.com,
	linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linaro-acpi@...ts.linaro.org
Subject: Re: [PATCH v8 21/21] arm64: ACPI: additions of ACPI documentation
 for arm64

On Tue, Feb 03, 2015 at 05:40:20PM -0700, Al Stone wrote:
> Much removed to cut down the size on this and to highlight a couple of specific
> sections pertinent to the ACPI on ARMv8 TODO List.....

This is of course good practice when replying to anything!

> > +_DSD	6.2.5		To be used with caution.  If this object is used, try
> > +			to use it within the constraints already defined by the
> > +			Device Properties UUID.  Only in rare circumstances
> > +			should it be necessary to create a new _DSD UUID.
> > +
> > +			In either case, submit the _DSD definition along with
> > +			any driver patches for discussion, especially when
> > +			device properties are used.  A driver will not be 
> > +			considered complete without a corresponding _DSD
> > +			description.  Once approved by kernel maintainers,
> > +			the UUID or device properties must then be registered
> > +			with the UEFI Forum; this may cause some iteration as
> > +			more than one OS will be registering entries.

> [snip...]

> So, this is my attempt to encapsulate what I think people want to have happen
> around the use of _DSD; I just want to make sure I point it out so it doesn't
> inadvertently get lost somehow.

> Is this far too little?  Is it sufficient?  If it only addresses part of the
> concerns, what did I miss?

This does take us back to the issue of how exactly one is supposed to
register/approve _DSD bindings and what format they're written in which
I don't think we ever fully got to the bottom of it (there's some stuff
on the UEFI website but it's definitely looking a bit placeholderish).

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)