mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2026-01-01 06:18:29 +08:00
cc427ee77a
This patch adds firmware for Keystone QMSS Accumulator PDSP. This is required to support Accumulator queues. Accumulator queues are one of the queue types supported in drivers/soc/ti/knav_qmss_acc.c. This queue can be part of a channel that supports one queue or multiple queue per channel and are managed by the Accumulator PDSP. For more details on hardware, please refer http://www.ti.com/lit/ug/sprugr9h/sprugr9h.pdf and DT documentation below in linux kernel source tree Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt Signed-off-by: Murali Karicheri <m-karicheri2@ti.com> Signed-off-by: Kyle McMartin <kyle@kernel.org>
Linux firmware
==============
<http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
This repository contains all these firmware images which have been
extracted from older drivers, as well various new firmware images which
we were never permitted to include in a GPL'd work, but which we _have_
been permitted to redistribute under separate cover.
To submit firmware to this repository, please send either a git binary
diff or preferably a git pull request to:
linux-firmware@kernel.org
and also cc: to related mailing lists.
Your commit should include an update to the WHENCE file clearly
identifying the license under which the firmware is available, and
that it is redistributable. Being redistributable includes ensuring
the firmware license provided includes an implicit or explicit
patent grant to end users to ensure full functionality of device
operation with the firmware. If the license is long and involved, it's
permitted to include it in a separate file and refer to it from the
WHENCE file.
And if it were possible, a changelog of the firmware itself.
Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code).
WARNING:
=======
Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
request. Otherwise your firmware _will never be accepted_.
Maintainers are really busy, so don't expect a prompt reply.