mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Stephen Boyd <stephen.boyd@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Laura Abbott <labbott@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Vikram Mulukutla <markivx@codeaurora.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [RFC/PATCH 4/4] firmware: Support requesting firmware directly into DMA memory
Date: Wed, 9 Mar 2016 09:29:15 +0700	[thread overview]
Message-ID: <20160309022915.GB3898@sirena.org.uk> (raw)
In-Reply-To: <CACVXFVNgYo6Az1GtH+buuT16inG0+8DQAETTTDwBeQ3DkmMt_w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

On Tue, Mar 08, 2016 at 09:42:17PM +0800, Ming Lei wrote:
> On Tue, Mar 8, 2016 at 5:22 PM, Stephen Boyd <stephen.boyd@linaro.org> wrote:

> > This design creates needless memory pressure and delays loading
> > because we have to copy from kernel memory to somewhere else.

> Given firmware request can't be a frequent operation, I don't think it is
> a big deal about the so called memory pressure and delay.

Boot time is a very important metric for some embedded product classes
and is obviously one of the most common times when we need to load lots
of firmware.  Some mobile platforms have some individual firmwares that
are getting on for 100M in size, holding a copy of one of them in RAM is
a substantial proportion of the available memory in a system with 1-2G
total especially when the system is also busy with other things.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-03-09  2:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  9:22 [RFC/PATCH 0/4] request_firmware() on memory constrained devices Stephen Boyd
2016-03-08  9:22 ` [PATCH 1/4] ARM64: dma: Add support for NO_KERNEL_MAPPING attribute Stephen Boyd
2016-03-08 13:58   ` Robin Murphy
2016-03-08  9:22 ` [RFC/PATCH 2/4] dma-mapping: Add dma_remap() APIs Stephen Boyd
2016-03-08  9:22 ` [RFC/PATCH 3/4] firmware_class: Provide infrastructure to make fw caching optional Stephen Boyd
2016-03-08  9:22 ` [RFC/PATCH 4/4] firmware: Support requesting firmware directly into DMA memory Stephen Boyd
2016-03-08 11:58   ` Mimi Zohar
     [not found]     ` <20160412172708.28213.21206@sboyd-linaro>
2016-04-12 23:04       ` Mimi Zohar
2016-03-08 13:42   ` Ming Lei
2016-03-09  2:29     ` Mark Brown [this message]
2016-03-08  9:32 ` [RFC/PATCH 0/4] request_firmware() on memory constrained devices Alexander Stein
2016-03-08 10:07   ` Stephen Boyd

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=20160309022915.GB3898@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=labbott@redhat.com \
    --cc=linux-arm@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=markivx@codeaurora.org \
    --cc=robin.murphy@arm.com \
    --cc=stephen.boyd@linaro.org \
    --cc=tom.leiming@gmail.com \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®