linux-kernel - Re: [PATCH v9 1/6] x86/platform/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

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: <alpine.DEB.2.20.1611081753370.3501@nanos>
Date:   Tue, 8 Nov 2016 17:55:20 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Tan Jui Nee <jui.nee.tan@...el.com>
cc:     mika.westerberg@...ux.intel.com, heikki.krogerus@...ux.intel.com,
        andriy.shevchenko@...ux.intel.com, mingo@...hat.com,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        ptyser@...-inc.com, lee.jones@...aro.org, linus.walleij@...aro.org,
        linux-gpio@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        jonathan.yong@...el.com, ong.hock.yu@...el.com,
        Tony Luck <tony.luck@...el.com>,
        wan.ahmad.zainie.wan.mohamad@...el.com, yunying.sun@...el.com,
        Darren Hart <dvhart@...radead.org>
Subject: Re: [PATCH v9 1/6] x86/platform/p2sb: New Primary to Sideband bridge
 support driver for Intel SOC's

On Tue, 8 Nov 2016, Tan Jui Nee wrote:
> There is already one and at least one more user coming which
> require an access to Primary to Sideband bridge (P2SB) in order
> to get IO or MMIO bar hidden by BIOS.
> Create a driver to access P2SB for x86 devices.
> 
>  arch/x86/Kconfig                 |  4 ++
>  arch/x86/include/asm/p2sb.h      | 27 +++++++++++
>  arch/x86/platform/intel/Makefile |  1 +
>  arch/x86/platform/intel/p2sb.c   | 98 ++++++++++++++++++++++++++++++++++++++++

This really has nothing to do with architecture. It's a platform enablement
driver and therefor should go into drivers/platform/x86

Cc'ed Darren who is responsible for this.

Thanks,

	tglx