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: Mon, 19 Sep 2016 15:46:37 +0800 From: Peter Chen <hzpeterchen@...il.com> To: Vaibhav Hiremath <vaibhav.hiremath@...aro.org> Cc: Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh+dt@...nel.org>, Peter Chen <peter.chen@....com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Alan Stern <stern@...land.harvard.edu>, Mark Brown <broonie@...nel.org>, Sebastian Reichel <sre@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Dmitry Eremin-Solenikov <dbaryshkov@...il.com>, dwmw3@...radead.org, Mark Rutland <mark.rutland@....com>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Krzysztof Kozłowski <k.kozlowski@...sung.com>, Linux USB List <linux-usb@...r.kernel.org>, oscar@...andei.net, Paweł Moll <pawel.moll@....com>, Arnd Bergmann <arnd@...db.de>, "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, Fabio Estevam <festevam@...il.com>, Sascha Hauer <s.hauer@...gutronix.de>, Stephen Boyd <stephen.boyd@...aro.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, troy.kisky@...ndarydevices.com, stillcompiling@...il.com, Philipp Zabel <p.zabel@...gutronix.de>, "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>, mka@...omium.org, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH v6 0/8] power: add power sequence library On Mon, Sep 19, 2016 at 01:09:10PM +0530, Vaibhav Hiremath wrote: > > > On Friday 09 September 2016 02:17 PM, Ulf Hansson wrote: > >[...] > > > >>>>>We had an agreement that keep mmc's pwrseq framework unchanging. > >>>>>Unless Ulf and rob both agree to change. > >>>>Why 2 separate approach for same problem ? > >>>>And I see this as possible duplication of code/functionality :) > >>>How the new kernel compatibles old dts? If we do not need to > >>>consider this problem, the mmc can try to use power sequence library > >>>too in future. > >> > >>I think we should attempt to get both MMC and USB power seq > >>come on one agreement, so that it can be reused. > >That would be nice. Although, to do that you would have to allow some > >DT bindings to be deprecated in the new generic power seq bindings, as > >otherwise you would break existing DTBs. > > > >I guess that is what Rob was objecting to!? > > yeah, thats right. > > So lets adopt similar implementation for USB as well instead of > library, but keeping MMC untouched as of now. > > What I am trying to propose here is, > > Lets have power-sequence framework (similar to V1 of this series), > with, > > pwrseq: Core framework for power sequence. > pwrseq_generic/simple: for all generic control, like reset and clock > pwrseq_emmc: probably duplication of existing code - the idea > here is, all future code should be using this new > binding, so that we can deprecate the > drivers/mmc/core/pwrseq > pwrseq_arche: The usecase which I am dealing with today, which is more > complex in nature. > > Then the respective drivers can add their drivers (if needed) based on > complexity. > > comments ?? The key point here is DT maintainer (Rob) doesn't agree with adding new node for power sequence at dts. -- Best Regards, Peter Chen
Powered by blists - more mailing lists