linux-kernel - [PATCH] usb: phy-generic, phy-ulpi patch set

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-next>] [day] [month] [year] [list]

Message-Id: <1385967919-13258-1-git-send-email-chris.ruehl@gtsys.com.hk>
Date:	Mon,  2 Dec 2013 15:05:16 +0800
From:	Chris Ruehl <chris.ruehl@...ys.com.hk>
To:	balbi@...com, gregkh@...uxfoundation.org
Cc:	linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Chris Ruehl <chris.ruehl@...ys.com.hk>
Subject: [PATCH] usb: phy-generic, phy-ulpi patch set 

This patch set add support 
* GPIO ChipSelect
* ULPI support to set VBUS flags for EXTVBUSIND,CHRGVBUS
* ULPI support to set VBUS flags from DT

[PATCH 1/3] usb: phy-generic: Add GPIO based ChipSelect
	The ULPI ISP1504 uses the CHIP_SELECT_N (low active) pin to active the
	chip. This patch add support for GPIO based ChipSelect almost the same
	way implemented for the Reset feature.

[PATCH 2/3] usb: phy-ulpi: Add EXTVBUSIND,CHRGVBUS flag support
	ULPI like ISP1504 support external vbus power indication
	used in combination with vbus switches mic2075.

[PATCH 3/3] usb: phy-generic: Add ULPI VBUS support
	Some platforms need to set the VBUS parameters of the ULPI
	like ISP1504 which interact with overcurrent protection and
	power switch MIC2575. Therefore it requires to set
	* DRVVBUS
	* DRVVBUS_EXT
	* EXTVBUSIND
	* CHRGVBUS
	of the ULPI.

Signed-off-by: Chris Ruehl <chris.ruehl@...ys.com.hk>
---
--
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/