linux-kernel - Re: [PATCH] pinctrl-baytrail: add function mux checking in gpio pin request

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: <CACRpkdajaffBOmc9KeUyLkwZth6vNu-Z0Ln+Xf4ZV0gZ9Ytf_g@mail.gmail.com>
Date:	Tue, 11 Mar 2014 11:27:13 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Chew Chiau Ee <chiau.ee.chew@...el.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc:	Darren Hart <dvhart@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl-baytrail: add function mux checking in gpio pin request

On Thu, Mar 6, 2014 at 2:59 PM, Chew Chiau Ee <chiau.ee.chew@...el.com> wrote:

> From: Chew, Kean Ho <kean.ho.chew@...el.com>
>
> The requested gpio pin must has the func_pin_mux field set
> to GPIO function by BIOS/FW in advanced. Else, the gpio pin
> request would fail. This is to ensure that we do not expose
> any gpio pins which shall be used for alternate functions,
> for eg: wakeup pin, I/O interfaces for LPSS, etc.
>
> Signed-off-by: Chew, Kean Ho <kean.ho.chew@...el.com>
> Signed-off-by: Chew, Chiau Ee <chiau.ee.chew@...el.com>

Patch applied with Darren's ACK.

This confirms my suspicion that you will not be able to
hide the pin control interface side of this hardware forever. ;-)

Mika/Mathias: any comments?

Yours,
Linus Walleij
--
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/