[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <545A9DD2.7050602@codeaurora.org>
Date: Wed, 05 Nov 2014 15:59:46 -0600
From: Timur Tabi <timur@...eaurora.org>
To: Grant Likely <grant.likely@...retlab.ca>
CC: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Alexandre Courbot <gnurou@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Ning Li <ning.li@...el.com>, Alan Cox <alan@...ux.intel.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
On 11/05/2014 03:46 PM, Grant Likely wrote:
>
> 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.
Fair enough. For GPIO, using the Linux GPIO driver as a back-end for
the ASL means that we don't have to duplicate the Linux GPIO driver in
firmware, and it also allows a high degree of flexibility. That sounds
like highly desirable features for any device support, including pin
control.
I don't really understand ACPI/ASL enough to really have much insight in
this area, but I've been waiting over six months for someone ... anyone
... to do someone on this area. So I'm kinda stuck -- I have a vested
interested in this area, and yet I'm not in a position to contribute much.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
--
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/
Powered by blists - more mailing lists