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 May 2014 23:16:20 +0200 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Viresh Kumar <viresh.kumar@...aro.org> Cc: linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org, arvind.chauhan@....com, inderpal.s@...sung.com, pavel@....cz, nm@...com, chander.kashyap@...aro.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Amit Daniel Kachhap <amit.daniel@...sung.com>, Kukjin Kim <kgene.kim@...sung.com>, Shawn Guo <shawn.guo@...aro.org>, Sudeep Holla <sudeep.holla@....com> Subject: Re: [PATCH Resend] driver/core: cpu: initialize opp table On Monday, May 19, 2014 11:13:24 PM Rafael J. Wysocki wrote: > On Monday, May 19, 2014 11:59:11 AM Viresh Kumar wrote: > > All drivers expecting CPU's OPPs from device tree initialize OPP table using > > of_init_opp_table() and there is nothing driver specific in that. They all do it > > in the same way adding to code redundancy. > > > > It would be better if we can get rid of code redundancy by initializing CPU OPPs > > from core code for all CPUs that have a "operating-points" property defined in > > their node. > > > > This patch initializes OPPs as soon as CPU device is registered in > > register_cpu(). > > > > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> > > Cc: Amit Daniel Kachhap <amit.daniel@...sung.com> > > Cc: Kukjin Kim <kgene.kim@...sung.com> > > Cc: Shawn Guo <shawn.guo@...aro.org> > > Cc: Sudeep Holla <sudeep.holla@....com> > > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org> Do patches [2-5/5] depend on this one BTW? -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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