remarkable-linux/drivers/soc/ti
Michal Morawiec f7f2bccd1f soc: ti: knav_qmss_queue: Fix linking RAM setup for queue managers
Configure linking RAM for both queue managers also in case
when only linking RAM 0 is specified in device tree.

Currently hwqueue driver configures linking RAM(s) to be used
cooperatively by the QMs (shared mode). Therefore if both
queue managers are used then both must be configured with
exactly the same linking RAM info (base address and size)
independent of the number of linking RAM(s) specified in the
device tree.
For proper operation only one linking RAM is required and in most
cases this can be internal one as long as it is able to handle
the number of descriptors used in the system.
Current driver code however skips configuration of second
queue manager if second linking RAM is not specified.
If the configuration for the QM2 is missing there will be
a crash when it tries to push/pop descriptors from its queues.

Signed-off-by: Michal Morawiec <michal.1.morawiec.ext@nokia.com>
Signed-off-by: Santosh Shilimkar <ssantosh@kernel.org>
2015-11-23 10:36:27 -08:00
..
Kconfig soc: ti: add Keystone Navigator DMA support 2014-09-24 09:49:15 -04:00
knav_dma.c soc: ti: drop owner assignment from platform_drivers 2014-10-20 16:21:35 +02:00
knav_qmss.h soc: ti: qmss: make acc queue support optional in the driver 2015-10-13 13:49:04 -07:00
knav_qmss_acc.c ARM: SoC platform updates for v4.4 2015-11-10 14:56:23 -08:00
knav_qmss_queue.c soc: ti: knav_qmss_queue: Fix linking RAM setup for queue managers 2015-11-23 10:36:27 -08:00
Makefile soc: ti: knav_qmss_queue: makefile tweak to build as dynamic module 2015-01-29 13:23:51 -08:00