linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <stephen.boyd@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Brown <broonie@kernel.org>,
	Ming Lei <ming.lei@canonical.com>,
	Vikram Mulukutla <markivx@codeaurora.org>
Subject: [RESEND/PATCHv4 v4 0/3] request_firmware() into pre-allocated buffers
Date: Tue,  7 Jun 2016 09:47:38 -0700	[thread overview]
Message-ID: <20160607164741.31849-1-stephen.boyd@linaro.org> (raw)

Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can lead to a situation
where we map the firmware twice, once to load the firmware into
kernel memory and once to copy the firmware into the final
resting place.

This design creates needless memory pressure and delays loading
because we have to copy from kernel memory to somewhere else.
This patch sets adds support to the request firmware API to load the
firmware directly into a pre-allocated buffer, skipping the intermediate
copying step and alleviating memory pressure during firmware loading.
The drawback is that we can't use the firmware caching feature because
the memory for the firmware cache is not managed by the firmware
layer.

Patches based on v4.7-rc1.

Changes since v3:
 * Rebased onto v4.7-rc1
 * Renamed enum per Mimi's comment

Changes since v2:
 * Dropped DMA API changes and moved to dma coherent APIs per Catalin's
   suggestions
 * Reworked to request firmware directly into any pre-allocated buffer
 * Split off cleanup patch into patch #1 to ease review
 * Added file reading enum for reading firmware directly into buffer

Changes since v1:
 * Rebased onto v4.6-rc1 (large conflicts due to movement of code from Mimi)
 * Added some CONFIG_HAS_DMA ifdefs around code that's using DMA ops

Stephen Boyd (2):
  firmware: Consolidate kmap/read/write logic
  firmware: Support loading into a pre-allocated buffer

Vikram Mulukutla (1):
  firmware: Provide infrastructure to make fw caching optional

 drivers/base/firmware_class.c | 183 +++++++++++++++++++++++++++++-------------
 fs/exec.c                     |   9 ++-
 include/linux/firmware.h      |   8 ++
 include/linux/fs.h            |   1 +
 4 files changed, 142 insertions(+), 59 deletions(-)

-- 
2.9.0-rc1

             reply	other threads:[~2016-06-07 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 16:47 Stephen Boyd [this message]
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 1/3] firmware: Consolidate kmap/read/write logic Stephen Boyd
2016-06-07 20:21   ` Andrew Morton
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 2/3] firmware: Provide infrastructure to make fw caching optional Stephen Boyd
2016-06-14  1:53   ` Luis R. Rodriguez
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 3/3] firmware: Support loading into a pre-allocated buffer Stephen Boyd
2016-06-12  9:28   ` kbuild test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160607164741.31849-1-stephen.boyd@linaro.org \
    --to=stephen.boyd@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markivx@codeaurora.org \
    --cc=ming.lei@canonical.com \
    --cc=zohar@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).