Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751757AbaKEVyl (ORCPT ); Wed, 5 Nov 2014 16:54:41 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:62215 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751333AbaKEVyk (ORCPT ); Wed, 5 Nov 2014 16:54:40 -0500 From: "Rafael J. Wysocki" To: Grant Likely Cc: Timur Tabi , Mika Westerberg , Linus Walleij , Alexandre Courbot , Heikki Krogerus , Mathias Nyman , Ning Li , Alan Cox , lkml Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Date: Wed, 05 Nov 2014 23:15:26 +0100 Message-ID: <1632312.tiWezf5I7W@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <1415012493-134561-1-git-send-email-mika.westerberg@linux.intel.com> <545912D2.5090708@codeaurora.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, November 05, 2014 09:46:14 PM Grant Likely wrote: > On Tue, Nov 4, 2014 at 5:54 PM, Timur Tabi wrote: > > On 11/04/2014 02:20 AM, Mika Westerberg wrote: > >> > >> There is nothing like that yet in ACPI world but with the ACPI _DSD > >> patches we are getting properties similar to DT which means that we can > >> provide pinctrl bindings from ACPI systems as well. > > > > > > Do you know if anyone has signed up to actually do the work of defining how > > pinctrl will look in ACPI? I'm guessing the simplest approach would be to: > > Actually, for the most part we /don't/ want to try and put pinctrl > into an ACPI binding. The assumption is that on an ACPI platform it > would be the combination of ACPI and firmware responsible for the pin > mappings, not the operating system. > > Before even attempting to put pinctrl mappings into your driver, there > should instead be a conversation at the ACPI spec level about whether > or not it makes sense and what such a binding should look like. We may need to support pinctrl on ACPI platforms in the meantime, though, for reasons that Mika mentioned at one point (there are systems where the firmware mangles things etc., which quite frankly is to be expected). So while I'm all for discussing this in the ASWG, what's the interim approach we should be using, in your opinion? -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/