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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 16 Sep 2014 17:54:00 +0200 From: Heiko Stuebner <heiko@...ech.de> To: broonie@...nel.org Cc: linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org, robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com, ijc+devicetree@...lion.org.uk, galak@...eaurora.org, Heiko Stuebner <heiko@...ech.de> Subject: [PATCH v2 0/4] regulator: add support for syr82x to fan53555 Silergy SYR827 and SYR828 regulators use the completely same i2c interface as the fan53555 regulators - only with different voltage ranges. They are used in a some Rockchip rk3288 board designs around an act8846. Therefore first add devicetree support for the fan53555 in general and then support for the Silgery variants. Tested on a rk3288 based Netxeon R89 board as cpu voltage regulator. changes since v1: - drop already applied vin-supply patch - drop wrong regulator-naming patch - add patch to generalize ramp_delay handling Heiko Stuebner (4): regulator: fan53555: use set_ramp_delay to set the ramp up slew rate dt-bindings: add devicetree bindings for Fairchild FAN53555 regulators regulator: fan53555: add devicetree support regulator: fan53555: add support for Silergy SYR82x regulators .../devicetree/bindings/regulator/fan53555.txt | 23 +++ .../devicetree/bindings/vendor-prefixes.txt | 2 + drivers/regulator/fan53555.c | 191 ++++++++++++++++++--- 3 files changed, 193 insertions(+), 23 deletions(-) create mode 100644 Documentation/devicetree/bindings/regulator/fan53555.txt -- 2.0.1 -- 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