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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160125114903.GE1790@lahna.fi.intel.com>
Date:	Mon, 25 Jan 2016 13:49:03 +0200
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	Antoine Tenart <antoine.tenart@...e-electrons.com>
Cc:	ptyser@...-inc.com, lee.jones@...aro.org, linus.walleij@...aro.org,
	gnurou@...il.com, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Mathias Nyman <mathias.nyman@...ux.intel.com>
Subject: Re: [PATCH 0/3] gpio: Intel Baytrail support

On Sat, Jan 23, 2016 at 05:32:06PM +0100, Antoine Tenart wrote:
> This series introduces the GPIO Intel Baytrail support, using both the
> lpc ich and the gpio ich drivers.
> 
> Antoine Tenart (3):
>   gpio: gpio-ich: add support for Intel Baytrail

Intel Baytrail support has been in mainline kernel for quite some time
already. The driver is drivers/pintctrl/intel/pinctrl-baytrail.c.

Also the ICH GPIO block is not compatible to Baytrail which is why there
is a separate driver in the first place. Have you tested this series on
Baytrail?

>   mfd: lpc_ich: use a correct mask for the GPIO base address
>   mfd: lpc_ich: add GPIO support for Baytrail

All Baytrails I've seen expose the GPIO device via ACPI namespace so
there should be no need for the above two patches.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ