| 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: <1441973658-26234-6-git-send-email-ckeepax@opensource.wolfsonmicro.com> Date: Fri, 11 Sep 2015 13:14:17 +0100 From: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com> To: <cw00.choi@...sung.com>, <lee.jones@...aro.org> CC: <myungjoo.ham@...sung.com>, <sameo@...ux.intel.com>, <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <patches@...nsource.wolfsonmicro.com> Subject: [PATCH v2 5/6] extcon: arizona: Add device binding for second jack detect pin on GPIO5 Some Arizona devices have the option to use the GPIO5 pin as a second jack detection pin. This patch adds device bindings to specify to the driver that it should use this pin. Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com> Acked-by: Chanwoo Choi <cw00.choi@...sung.com> --- Changes since v1: - Added more description in the commit message drivers/extcon/extcon-arizona.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/extcon/extcon-arizona.c b/drivers/extcon/extcon-arizona.c index 34b5a3b..5fbe893 100644 --- a/drivers/extcon/extcon-arizona.c +++ b/drivers/extcon/extcon-arizona.c @@ -1233,6 +1233,11 @@ static int arizona_extcon_device_get_pdata(struct arizona *arizona) device_property_read_u32(arizona->dev, "wlf,gpsw", &pdata->gpsw); + pdata->jd_gpio5 = device_property_read_bool(arizona->dev, + "wlf,use-jd-gpio"); + pdata->jd_gpio5_nopull = device_property_read_bool(arizona->dev, + "wlf,use-jd-gpio-nopull"); + return 0; } -- 1.7.2.5 -- 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/
Powered by blists - more mailing lists