| 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: <6C806F24-FF45-4BF6-ACB0-1EE10AC584BD@opensource.wolfsonmicro.com> Date: Sun, 28 Nov 2010 18:25:39 +0000 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Laurent Pinchart <laurent.pinchart@...asonboard.com> Cc: Sakari Ailus <sakari.ailus@...well.research.nokia.com>, linux-media@...r.kernel.org, linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org, lrg@...mlogic.co.uk, lennart@...ttering.net Subject: Re: [RFC/PATCH v6 05/12] media: Reference count and power handling On 28 Nov 2010, at 12:33, Laurent Pinchart wrote: > Throwing an idea here, what about making power management modular ? The MC > core would then call back to drivers to handle use count changes. The > media_entity_use_change() function would be exported (and renamed), so that > drivers could use it if they want graph-based power management. ALSA would > have its own use count handler. We need more than just the count handler - we need a complete list of everything that has been changed in the whole system. The graph walk itself is fine but we need to be able to do postprocessing of the delta that is generated. Like I said pre- and post- callbacks may well cover it. Note that this is specifically for ASoC, not ALSA in general.-- 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