| 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: <1397689950-1568-1-git-send-email-dianders@chromium.org> Date: Wed, 16 Apr 2014 16:12:24 -0700 From: Doug Anderson <dianders@...omium.org> To: Anton Vorontsov <anton@...msg.org> Cc: Olof Johansson <olof@...om.net>, Sachin Kamat <sachin.kamat@...aro.org>, ajaykumar.rs@...sung.com, linux-samsung-soc@...r.kernel.org, Doug Anderson <dianders@...omium.org>, devicetree@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>, Mark Brown <broonie@...nel.org>, Simon Glass <sjg@...omium.org>, linux-doc@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>, Samuel Ortiz <sameo@...ux.intel.com>, linux-kernel@...r.kernel.org, Kumar Gala <galak@...eaurora.org>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Dmitry Eremin-Solenikov <dbaryshkov@...il.com>, Rob Herring <robh+dt@...nel.org>, David Woodhouse <dwmw2@...radead.org>, Pawel Moll <pawel.moll@....com>, Lee Jones <lee.jones@...aro.org>, Mark Rutland <mark.rutland@....com>, Sean Paul <seanpaul@...omium.org>, Michael Spang <spang@...omium.org> Subject: [PATCH v3 0/5] Fixes for tps65090 for Samsung ARM Chromebook These five patches bring tps65090 up to speed with what's currently in the Chromium OS kernel 3.8 tree and running on the Samsung ARM Chromebook. Changes were tested atop the current linux tree (v3.15-rc1). FET retries were tested on a machine with a known flaky tps65090. Since display isn't working on pure upstream, I augmented the code to turn FET1 (vcd_led) on/off 500 times at bootup. When testing I included <https://patchwork.kernel.org/patch/3980731/> to make sure tps65090 was in exynos5250-snow's device tree. Dependencies: - Patch #1 (mfd no irq) has no dependencies, though patch #2 won't work without it. - Patch #2 (charger polling) can be applied without patch #1 but won't actually make charger polling work without it. - Patch #3 (caching) can be applied before retries patch but not after. - Patch #4 (overcurrent wait time) can be applied before retries patch but not after (just due to merge conflicts, no other reason). - Patch #5 (retries) absolutely requires patch #3 (caching). Changes in v3: - Fixed kernel-doc notation for return Changes in v2: - Split noirq (polling mode) changes into MFD and charger - Leave cache on for the registers that can be cached. - Move register offsets to mfd header file. - Separated the overcurrent and retries changes into two patches. - Now set overcurrent at probe time since it doesn't change. - Separated the overcurrent and retries changes into two patches. - No longer open code fet_is_enabled(). - Fixed tps6090 typo. - For loop => "while true". - Removed a set of braces. Doug Anderson (5): mfd: tps65090: Don't tell child devices we have an IRQ if we don't charger: tps65090: Allow charger module to be used when no irq mfd: tps65090: Stop caching most registers regulator: tps65090: Allow setting the overcurrent wait time regulator: tps65090: Make FETs more reliable by adding retries .../devicetree/bindings/regulator/tps65090.txt | 4 + drivers/mfd/tps65090.c | 41 ++-- drivers/power/tps65090-charger.c | 87 ++++++--- drivers/regulator/tps65090-regulator.c | 211 +++++++++++++++++++-- include/linux/mfd/tps65090.h | 19 ++ 5 files changed, 303 insertions(+), 59 deletions(-) -- 1.9.1.423.g4596e3a -- 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