From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Stone Subject: Re: [RFC PATCH 0/4] Add ACPI support for pinctrl configuration Date: Tue, 5 Apr 2016 17:48:42 -0600 Message-ID: <57044EDA.90004@redhat.com> References: <1459424685-26965-1-git-send-email-irina.tirdea@intel.com> <20160404225200.GA1615@svinekod> <20160405165935.GA5456@sirena.org.uk> Reply-To: ahs3@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org To: Octavian Purdila , Mark Brown Cc: Linus Walleij , Mark Rutland , Irina Tirdea , "Rafael J. Wysocki" , Len Brown , Mika Westerberg , "linux-gpio@vger.kernel.org" , ACPI Devel Maling List , Rob Herring , Heikki Krogerus , Andy Shevchenko , Cristina Ciocan , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Charles Garcia-Tobin List-Id: devicetree@vger.kernel.org On 04/05/2016 01:37 PM, Octavian Purdila wrote: > On Tue, Apr 5, 2016 at 7:59 PM, Mark Brown wrote: >> On Tue, Apr 05, 2016 at 10:43:11AM +0200, Linus Walleij wrote: >>[snip...] > > I know that there are some discussions for pinmux configuration in the > ASWG, but it does not match the Linux pinctrl model. So we will end up > with a pinctrl driver that offers groups, functions and pin names and > a totally different ACPI description that we can't map to the pinctrl > driver. Um, as a member of the ASWG, this is the first I've heard of this discussion. And I do attend the meetings very regularly. Please send me an issue number off-line because I'm not finding it in the current issue list. Secondly, if this is being discussed within the ASWG, please refer to the UEFI member agreements about disclosing information prior to it being approved by the forum; there are limits to such disclosures, and a public mailing list may be well past those limits. -- ciao, al ----------------------------------- Al Stone Software Engineer Red Hat, Inc. ahs3@redhat.com -----------------------------------