linux-kernel - Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 04 Nov 2014 14:31:41 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:	Timur Tabi <timur@...eaurora.org>,
	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>,
	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 Tuesday, November 04, 2014 11:39:07 AM Mika Westerberg wrote:
> On Tue, Nov 04, 2014 at 10:20:56AM +0200, Mika Westerberg wrote:
> > On Mon, Nov 03, 2014 at 05:24:55PM -0600, Timur Tabi wrote:
> > > On Mon, Nov 3, 2014 at 5:01 AM, Mika Westerberg
> > > <mika.westerberg@...ux.intel.com> wrote:
> > > > Hi,
> > > >
> > > > This is second version of the patch series adding pinctrl/GPIO support
> > > > for Intel Braswell and Cherrryview. The previous version can be found here:
> > > >
> > > > https://lkml.org/lkml/2014/10/27/118
> > > >
> > > > I've dropped patches [2/4] and [3/4] as they are already applied to the
> > > > pinctrl tree.
> > > 
> > > Mika,
> > > 
> > > I am also trying to add ACPI enablement to my pinctrl driver (not yet
> > > submitted), but I'm new to ACPI and pin control drivers, so I have a
> > > lot of catching up to do.
> > > 
> > > In reviewing this patchset, it appears to me that pinctrl-cherryview.c
> > > is a normal pinctrl driver that has an acpi_match_table entry, and
> > > nothing more.
> > 
> > Indeed, it just a normal platform driver that can be enumerated from
> > ACPI using the .acpi_match_table entry.
> > 
> > > Assuming that this driver is booting on an ACPI system, what is the
> > > mechanism that calls into the driver to configure the pins?  Is there
> > > a definition for pin control in ASL that provides similar
> > > functionality as the pinctrl nodes in a device tree?
> > 
> > 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. Typically it has
> > been the BIOS that configures things but it cannot get everything 100%
> > right.
> > 
> > Currently I've been testing the muxing functionality so that I have a
> > small board file that sets mappings and the driver core handles
> > everything from there. For example I have development board where SPI
> > pins are muxed as GPIOs by the BIOS and with the mappings when the SPI
> > device appears the core will mux SPI out of those pins.
> 
> For reference the latest ACPI _DSD patches can be found here
> 
> https://lkml.org/lkml/2014/10/21/762

Actually, it's better to pull the device-properties branch:

git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git device-properties

because that contains the lastest changes.  It will be rebased in the future,
though, so don't merge it into your "immutable" branches.

-- 
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/