| 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
| ||
|
Date: Wed, 22 Jan 2014 14:48:05 -0600 From: Nishanth Menon <nm@...com> To: Mark Brown <broonie@...nel.org> CC: <devicetree@...r.kernel.org>, <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] regulator: ti-abb: Add support for interleaved LDO registers On 01/22/2014 02:19 PM, Mark Brown wrote: > On Tue, Jan 21, 2014 at 04:32:12PM -0600, Nishanth Menon wrote: > >> The other alternative will be to use reg-names and map individual >> registers (there are just setup and control registers to deal with per >> abb instance). That will coexist with other pinctrl, bandgap and other >> drivers which are not based off syscon. > > Yes, I suspect that's going to be a lot easier to deploy given that > there are existing drivers using the current non-syscon setup. I'm > totally fine with that approach. > ok - thanks for confirming - this also means that existing compatible flags will have to change - but they were present solely to encode the offset of setup and control from each other. Considering that we never had any dtsi in upstream (since they were all pending clock dts support for TI platforms), I will go with the assumption of not needing to maintain backward compatible for dtbs that could never have been generated in upstream kernel. -- Regards, Nishanth Menon -- 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