Re: [PATCH v2 8/8] p54: convert to sysdata API

From	Mark Brown <broonie@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v2 8/8] p54: convert to sysdata API
Date	2016-08-10 21:20 +0200
Message-ID	<s4HcL-NR-47@gated-at.bofh.it> (permalink)
References	(3 earlier) <rKQVj-8e5-1@gated-at.bofh.it> <rKSkp-Vx-1@gated-at.bofh.it> <rL6Qq-1D6-11@gated-at.bofh.it> <s4H36-I0-119@gated-at.bofh.it> <s4H36-I0-117@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Aug 10, 2016 at 09:04:38PM +0200, Arend Van Spriel wrote:

> So why would drivers want the devm solution anyway. Once firmware is
> loaded in the device it can be freed or do you expect device drivers to
> keep the firmware/sysdata for suspend/resume scenario as some do because
> of firmware cache behaviour. Does the "rootfs ready" event cover
> suspend/resume?

There are classes of devices that spend a large proportion of their time
powered off and are only powered up and have firmware loaded when they
are actively in use.  DSPs used in audio systems are one example of
this, I'd not be surprised to learn that similar things are done with
video.  It's too expensive to keep the device powered up and you may be
swapping between firmwares depending on use case anyway for a lot of
these devices.

Thread

Re: [PATCH v2 8/8] p54: convert to sysdata API Arend Van Spriel <arend.vanspriel@broadcom.com> - 2016-08-10 21:10 +0200
  Re: [PATCH v2 8/8] p54: convert to sysdata API Mark Brown <broonie@kernel.org> - 2016-08-10 21:20 +0200
    Re: [PATCH v2 8/8] p54: convert to sysdata API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2016-08-10 21:50 +0200
  Re: [PATCH v2 8/8] p54: convert to sysdata API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2016-08-10 21:40 +0200

csiph-web