From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id B18698B4 for ; Tue, 6 May 2014 05:02:16 +0000 (UTC) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 29CB32019B for ; Tue, 6 May 2014 05:02:15 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id a108so2252515qge.39 for ; Mon, 05 May 2014 22:02:15 -0700 (PDT) MIME-Version: 1.0 Sender: darren@apps.dvhart.com In-Reply-To: References: Date: Mon, 5 May 2014 22:02:15 -0700 Message-ID: From: Darren Hart To: Linus Walleij Content-Type: text/plain; charset=UTF-8 Cc: Greg Kroah-Hartman , "dvhart@dvhart.com" , "Rafael J. Wysocki" , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] Driver model/resources, ACPI, DT, etc (sigh) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, May 5, 2014 at 9:58 AM, Linus Walleij wrote: > On this topic I need to add: > > how are the ACPI HW descriptions really happening? > > I as subsystem maintainer have no real contact with these people, > I can only get a *vague* feeling that sometimes, they live in an ancient > world of assumptions that do not hold. > > Specifically I am worried when seeing some ACPI stuff that their idea > of pin control is "some sort of fancy GPIO-bolt on" and I fear they will > attempt to model and implement this with an ugly interface that we > will have to account for later, instead of reading say > Documentation/pinctrl.txt and learn something about how software > engineers go about handling such hardware. I was talking with someone just last week about how this might be done. I'll see if I can get the person looking into it to reach out to you. > Where is the communication entry port for a driver subsystem > maintainer that want to bring a message to the ACPI HW bindings > people? Rafael and I would be a good start. He and I, along with others, have been spending some time lately in the ACPI Specification Working Group and have some idea of how this stuff works. Matthew Garrett is another good contact for how to get involved. -- Darren Hart