From: yi1.li@linux.intel.com
To: mcgrof@kernel.org, atull@kernel.org, gregkh@linuxfoundation.org,
wagi@monom.org, dwmw2@infradead.org, rafal@milecki.pl,
arend.vanspriel@broadcom.com, rjw@rjwysocki.net,
moritz.fischer@ettus.com, pmladek@suse.com,
johannes.berg@intel.com, emmanuel.grumbach@intel.com,
luciano.coelho@intel.com, kvalo@codeaurora.org, luto@kernel.org,
takahiro.akashi@linaro.org, dhowells@redhat.com,
pjones@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
Yi Li <yi1.li@linux.intel.com>
Subject: [PATCHv2 0/2] Enable pre-allocated buffer support for driver_data
Date: Sat, 20 May 2017 01:48:04 -0500 [thread overview]
Message-ID: <1495262886-1045-1-git-send-email-yi1.li@linux.intel.com> (raw)
From: Yi Li <yi1.li@linux.intel.com>
This series enables the equivalent pre-allocated buffer feature in
request_firmware_into_buf to driver_data API, so caller can allocate
firmware data buffer and pass to driver_data. This will be used for
streaming support of driver_data, which allow caller to manage the size
and buffer of firmware streaming.
Changes in v2:
- Rebase to Luis R. Rodriguez's 20170501-driver-data-try2
branch
- Move alloc_buf and alloc_buf_size to public driver_data_req_params
structure.
- Add self test cases.
Yi Li (2):
firmware: Enable pre-allocated buffer support in driver_data
test: add pre-allocated buffer to driver_data tester
drivers/base/firmware_class.c | 21 +++-----
include/linux/driver_data.h | 5 ++
lib/test_driver_data.c | 68 ++++++++++++++++++++++++-
tools/testing/selftests/firmware/driver_data.sh | 36 +++++++++++++
4 files changed, 116 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-20 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 6:48 yi1.li [this message]
2017-05-20 6:48 ` [PATCHv2 1/2] firmware: Enable pre-allocated buffer support in driver_data yi1.li
2017-05-20 6:48 ` [PATCHv2 2/2] test: add pre-allocated buffer to driver_data tester yi1.li
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=1495262886-1045-1-git-send-email-yi1.li@linux.intel.com \
--to=yi1.li@linux.intel.com \
--cc=arend.vanspriel@broadcom.com \
--cc=atull@kernel.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=luto@kernel.org \
--cc=mcgrof@kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=pjones@redhat.com \
--cc=pmladek@suse.com \
--cc=rafal@milecki.pl \
--cc=rjw@rjwysocki.net \
--cc=takahiro.akashi@linaro.org \
--cc=wagi@monom.org \
/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
Powered by JetHome