| 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
| ||
|
Message-ID: <20160628081917.GF1711@lahna.fi.intel.com>
Date: Tue, 28 Jun 2016 11:19:17 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Tan Jui Nee <jui.nee.tan@...el.com>
Cc: heikki.krogerus@...ux.intel.com, andriy.shevchenko@...ux.intel.com,
tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
x86@...nel.org, ptyser@...-inc.com, lee.jones@...aro.org,
linus.walleij@...aro.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, jonathan.yong@...el.com,
ong.hock.yu@...el.com, weifeng.voon@...el.com,
wan.ahmad.zainie.wan.mohamad@...el.com
Subject: Re: [PATCH v5 3/3] mfd: lpc_ich: Add support for Intel Apollo Lake
GPIO pinctrl in non-ACPI system
On Tue, Jun 28, 2016 at 03:56:48PM +0800, Tan Jui Nee wrote:
> +config X86_INTEL_APL
> + bool "Non-ACPI support for Intel Apollo Lake platforms"
> + select PINCTRL
> + ---help---
> + Select this option to enable MMIO BAR access over the P2SB for
> + non-ACPI Intel Apollo Lake SoC platforms. This driver uses the P2SB
> + hide/unhide mechanism cooperatively to pass the PCI BAR address to
> + the platform driver, currently GPIO.
> +
Sorry but IMHO this still does not explain the option clearly enough.
You are using this in some automotive IVI system with specialized
bootloader, correct? Why not use that here instead?
Something along the lines of
config X86_INTEL_IVI
bool "Intel in-vehicle infotainment (IVI) systems used in cars"
Powered by blists - more mailing lists