linux-kernel - Re: [PATCH 00/36] AArch64 Linux kernel port

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: <20120709140222.GA30838@srcf.ucam.org>
Date:	Mon, 9 Jul 2012 15:02:22 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	grant.likely@...retlab.ca
Subject: Re: [PATCH 00/36] AArch64 Linux kernel port

On Mon, Jul 09, 2012 at 02:56:26PM +0100, Mark Brown wrote:
> On Mon, Jul 09, 2012 at 02:06:29PM +0100, Matthew Garrett wrote:
> 
> > There's ongoing discussion about unifying ACPI and ftd representation, 
> > and once that's done this isn't a problem, but right now there's no 
> 
> Where is this discussion?

My part of it has pretty much been in-person discussion with Grant 
Likely, but there was some on ksummit-discuss last month.

> > terribly straightforward way to do this without a lot of basically 
> > boilerplate code. The biggest issue is that ACPI has a very different 
> > idea about event delivery and we'd need some way to abstract that.
> 
> Right, but there's lots of bolierplate code with this stuff anyway and
> it's not fundamentally hard.  Last time I looked at ACPI it had a rather
> different model for how all this stuff would work than DT did which
> isn't terribly helpful here.

ACPI 5 lets devices expose their GPIO resources directly, so in some 
cases a driver will just be able to request that and handle things as it 
would in ftd. But the more traditional ACPI method is to use ACPI 
notifications, and those happen in process context. It seems unlikely 
that everyone's going to get it right unless there's existing in-kernel 
infrastructure for handling this.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/