02 Nov, 2017
1 commit
-
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.By default all files without license information are under the default
license of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if
Reviewed-by: Philippe Ombredanne
Reviewed-by: Thomas Gleixner
Signed-off-by: Greg Kroah-Hartman
21 Aug, 2017
1 commit
-
knav_pool_create is an exported function. In the event of a call
before knav_queue_probe, we encounter a NULL pointer dereference
in the following line. Hence return -EPROBE_DEFER to the caller till
the kdev pointer is non-NULL.Signed-off-by: Keerthy
Acked-by: Santosh Shilimkar
Signed-off-by: Arnd Bergmann
18 Aug, 2017
1 commit
-
Commit b6a1d093f96b ("PM / Domains: Extend generic power domain
debugfs") now creates a debugfs directory for each genpd based on the
name of the genpd. Currently no name is given to the genpd created by
ti_sci_pm_domains driver so because of this we see a NULL pointer
dereferences when it is accessed on boot when the debugfs entry creation
is attempted.Give the genpd a name before registering it to avoid this.
Fixes: 52835d59fc6c ("soc: ti: Add ti_sci_pm_domains driver")
Signed-off-by: Dave Gerlach
Signed-off-by: Santosh Shilimkar
Signed-off-by: Arnd Bergmann
12 May, 2017
1 commit
-
Fix error path while dma open channel issue. Also, no need to check output
on NULL if it's never returned.Signed-off-by: Ivan Khoronzhuk
Signed-off-by: David S. Miller
25 Apr, 2017
1 commit
-
Signed-off-by: Santosh Shilimkar
04 Apr, 2017
1 commit
-
Introduce a ti_sci_pm_domains driver to act as a generic pm domain
provider to allow each device to attach and associate it's ti-sci-id so
that it can be controlled through the TI SCI protocol.This driver implements a simple genpd where each device node has a
phandle to the power domain node and also must provide an index which
represents the ID to be passed with TI SCI representing the device using
a single phandle cell. The driver manually parses the phandle to get the
cell value. Through this interface the genpd dev_ops start and stop
hooks will use TI SCI to turn on and off each device as determined by
pm_runtime usage.Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Reviewed-by: Ulf Hansson
Signed-off-by: Keerthy
Signed-off-by: Nishanth Menon
Signed-off-by: Dave Gerlach
Signed-off-by: Santosh Shilimkar
24 Feb, 2017
1 commit
-
Pull ARM SoC driver updates from Arnd Bergmann:
"Driver updates for ARM SoCs.A handful of driver changes this time around. The larger changes are:
- Reset drivers for hi3660 and zx2967
- AHCI driver for Davinci, acked by Tejun and brought in here due to
platform dependencies- Cleanups of atmel-ebi (External Bus Interface)
- Tweaks for Rockchip GRF (General Register File) usage (kitchensink
misc register range on the SoCs)- PM domains changes for support of two new ZTE SoCs (zx296718 and
zx2967)"* tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (53 commits)
soc: samsung: pmu: Add register defines for pad retention control
reset: make zx2967 explicitly non-modular
reset: core: fix reset_control_put
soc: samsung: pm_domains: Read domain name from the new label property
soc: samsung: pm_domains: Remove message about failed memory allocation
soc: samsung: pm_domains: Remove unused name field
soc: samsung: pm_domains: Use full names in subdomains registration log
sata: ahci-da850: un-hardcode the MPY bits
sata: ahci-da850: add a workaround for controller instability
sata: ahci: export ahci_do_hardreset() locally
sata: ahci-da850: implement a workaround for the softreset quirk
sata: ahci-da850: add device tree match table
sata: ahci-da850: get the sata clock using a connection id
soc: samsung: pmu: Remove duplicated define for ARM_L2_OPTION register
memory: atmel-ebi: Enable the SMC clock if specified
soc: samsung: pmu: Remove unused and duplicated defines
memory: atmel-ebi: Properly handle multiple reference to the same CS
memory: atmel-ebi: Fix the test to enable generic SMC logic
soc: samsung: pm_domains: Add new Exynos5433 compatible
soc: samsung: pmu: Add dummy support for Exynos5433 SoC
...
30 Jan, 2017
1 commit
-
…kernel/git/tmlind/linux-omap into next/drivers
Just a single wkup_m3_ipc clean-up for v4.11 merge window.
We don't currently have anything else for drivers/soc to
merge, but I'd expect that to change as soon as we can start
moving PM code into drivers with the recently posted SRAM
changes. Anyways, sent as a separate pull request to make
it easy to group the ARM SoC pull requests.* tag 'omap-for-v4.11/drivers-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
soc: ti: wkup_m3_ipc: Drop wait from wkup_m3_rproc_boot_threadSigned-off-by: Olof Johansson <olof@lixom.net>
13 Jan, 2017
1 commit
-
Fix to return a negative error code from the kthread_run() error
handling case instead of 0, as done elsewhere in this function.Fixes: cdd5de500b2c ("soc: ti: Add wkup_m3_ipc driver")
Signed-off-by: Wei Yongjun
Signed-off-by: Tony Lindgren
07 Jan, 2017
3 commits
-
This patch cleanup the code to remove unnecessary header files and
also sort the header files.Signed-off-by: Murali Karicheri
Signed-off-by: WingMan Kwok
Signed-off-by: Sekhar Nori
Signed-off-by: Santosh Shilimkar -
This patch fixes some typos in the trace message
Signed-off-by: Murali Karicheri
Signed-off-by: Sekhar Nori
Signed-off-by: Santosh Shilimkar -
The function wkup_m3_rproc_boot_thread waits for asynchronous
firmware loading to parse the resource table before calling
rproc_boot(). However, as the resource table parsing has been
moved to rproc_boot(), there's no need to wait for the
asynchronous firmware loading completion. So, drop this.CC: Dave Gerlach
CC: Bjorn Andersson
Tested-by: Suman Anna
Signed-off-by: Sarangdhar Joshi
Signed-off-by: Tony Lindgren
01 Dec, 2016
1 commit
-
The irq_set_affinity_hint() will always fail when !SMP and
Networking will fail on Keystone 2 devices in this case.
Hence, fix by ignoring IRQ affinity settings when !SMP.Signed-off-by: Grygorii Strashko
Acked-by: Santosh Shilimkar
Signed-off-by: Arnd Bergmann
27 Feb, 2016
1 commit
-
The knav_qmss driver is currently broken when CONFIG_LPAE is
set, which is a bit surprising because I'd expect that any serious
users of this platforms would have more than 2GB of RAM and require
LPAE.The compiler clearly warns about an incorrect use of dma_addr_t
in the debug kernel messages:ti/knav_qmss_queue.c: In function 'knav_queue_setup_region':
ti/knav_qmss_queue.c:1025:117: warning: format '%x' expects argument of type 'unsigned int', but argument 9 has type 'dma_addr_t {aka long long unsigned int}' [-Wformat=]
ti/knav_qmss_queue.c:1025:117: warning: format '%x' expects argument of type 'unsigned int', but argument 10 has type 'dma_addr_t {aka long long unsigned int}' [-Wformat=]
ti/knav_qmss_queue.c: In function 'knav_queue_setup_link_ram':
ti/knav_qmss_queue.c:1175:118: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'dma_addr_t {aka long long unsigned int}' [-Wformat=]This patch changes all the debugging output to use the correct
%pad format string that works with both 32-bit and 64-bit dma_addr_t.
As the variable naming is somewhat confusing here, I also change
all *_phys names to *_dma when they refer to bus addresses that
are used for DMA rather than a physical memory address as seen from
the CPU. This is particularly important on keystone, because the
two things are not the same there.Signed-off-by: Arnd Bergmann
21 Jan, 2016
1 commit
-
Pull ARM SoC driver updates from Olof Johansson:
"Driver updates for ARM SoCs. Some for SoC-family code under
drivers/soc, but also some other driver updates that don't belong
anywhere else. We also bring in the drivers/reset code through
arm-soc.Some of the larger updates:
- Qualcomm support for SMEM, SMSM, SMP2P. All used to communicate
with other parts of the chip/board on these platforms, all
proprietary protocols that don't fit into other subsystems and live
in drivers/soc for now.- System bus driver for UniPhier
- Driver for the TI Wakeup M3 IPC device
- Power management for Raspberry PI
+ Again a bunch of other smaller updates and patches"
* tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (38 commits)
bus: uniphier: allow only built-in driver
ARM: bcm2835: clarify RASPBERRYPI_FIRMWARE dependency
MAINTAINERS: Drop Kumar Gala from QCOM
bus: uniphier-system-bus: add UniPhier System Bus driver
ARM: bcm2835: add rpi power domain driver
dt-bindings: add rpi power domain driver bindings
ARM: bcm2835: Define two new packets from the latest firmware.
drivers/soc: make mediatek/mtk-scpsys.c explicitly non-modular
soc: mediatek: SCPSYS: Add regulator support
MAINTAINERS: Change QCOM entries
soc: qcom: smd-rpm: Add existing platform support
memory/tegra: Add number of TLB lines for Tegra124
reset: hi6220: fix modular build
soc: qcom: Introduce WCNSS_CTRL SMD client
ARM: qcom: select ARM_CPU_SUSPEND for power management
MAINTAINERS: Add rules for Qualcomm dts files
soc: qcom: enable smsm/smp2p modular build
serial: msm_serial: Make config tristate
soc: qcom: smp2p: Qualcomm Shared Memory Point to Point
soc: qcom: smsm: Add driver for Qualcomm SMSM
...
15 Jan, 2016
1 commit
-
Pull trivial tree updates from Jiri Kosina.
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial:
floppy: make local variable non-static
exynos: fixes an incorrect header guard
dt-bindings: fixes some incorrect header guards
cpufreq-dt: correct dead link in documentation
cpufreq: ARM big LITTLE: correct dead link in documentation
treewide: Fix typos in printk
Documentation: filesystem: Fix typo in fs/eventfd.c
fs/super.c: use && instead of & for warn_on condition
Documentation: fix sysfs-ptp
lib: scatterlist: fix Kconfig description
23 Dec, 2015
1 commit
-
…/git/tmlind/linux-omap into next/drivers
TI wakeup M3 IPC device driver for v4.5 merge window. This driver will
eventually allow am33xx and am437x to support PM with their Cortex-M3
power management processor.This driver has been waiting to get merged for quite a while but has
had dependencies to the remoteproc that are now out of the way.* tag 'omap-for-v4.5/wakeup-m3' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
soc: ti: Add wkup_m3_ipc driver
Documentation: dt: add bindings for TI Wakeup M3 IPC deviceSigned-off-by: Olof Johansson <olof@lixom.net>
08 Dec, 2015
1 commit
-
This patch fix multiple spelling typos found in
various part of kernel.Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Signed-off-by: Jiri Kosina
03 Dec, 2015
1 commit
-
Introduce a wkup_m3_ipc driver to handle communication between the MPU
and Cortex M3 wkup_m3 present on am335x.This driver is responsible for actually booting the wkup_m3_rproc and
also handling all IPC which is done using the IPC registers in the control
module, a mailbox, and a separate interrupt back from the wkup_m3. A small
API is exposed for executing specific power commands, which include
configuring for low power mode, request a transition to a low power mode,
and status info on a previous transition.Signed-off-by: Dave Gerlach
Signed-off-by: Tony Lindgren
24 Nov, 2015
2 commits
-
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
Signed-off-by: Santosh Shilimkar -
When firmware image for PDSP firmware is absent in the file system
the kernel boot with ramfs/nfs is stuck for 60 seconds being the
the default timeout. request_firmware_direct() is to take care of
such optional firmware loading and hence replace the call in the
driver with this API.Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar
11 Nov, 2015
1 commit
-
Pull ARM SoC platform updates from Olof Johansson:
"New and/or improved SoC support for this release:Marvell Berlin:
- Enable standard DT-based cpufreq
- Add CPU hotplug supportFreescale:
- Ethernet init for i.MX7D
- Suspend/resume support for i.MX6ULAllwinner:
- Support for R8 chipset (used on NTC's $9 C.H.I.P board)Mediatek:
- SMP support for some platformsUniphier:
- L2 support
- Cleaned up SMP support, etc.plus a handful of other patches around above functionality, and a few
other smaller changes"* tag 'armsoc-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (42 commits)
ARM: uniphier: rework SMP operations to use trampoline code
ARM: uniphier: add outer cache support
Documentation: EXYNOS: Update bootloader interface on exynos542x
ARM: mvebu: add broken-idle option
ARM: orion5x: use mac_pton() helper
ARM: at91: pm: at91_pm_suspend_in_sram() must be 8-byte aligned
ARM: sunxi: Add R8 support
ARM: digicolor: select pinctrl/gpio driver
arm: berlin: add CPU hotplug support
arm: berlin: use non-self-cleared reset register to reset cpu
ARM: mediatek: add smp bringup code
ARM: mediatek: enable gpt6 on boot up to make arch timer working
soc: mediatek: Fix random hang up issue while kernel init
soc: ti: qmss: make acc queue support optional in the driver
soc: ti: add firmware file name as part of the driver
Documentation: dt: soc: Add description for knav qmss driver
ARM: S3C64XX: Use PWM lookup table for mach-smartq
ARM: S3C64XX: Use PWM lookup table for mach-hmt
ARM: S3C64XX: Use PWM lookup table for mach-crag6410
ARM: S3C64XX: Use PWM lookup table for smdk6410
...
14 Oct, 2015
2 commits
-
acc channels are available only if accumulator PDSP is loaded and
running in the SoC. As this requires firmware and user may not have
firmware in the file system, make the accumulator queue support
available in qmss driver optional. To use accumulator queus user needs
to add firmware to the file system and boot up kernel.Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar -
Currently firmware file name is included in the DTS. This is not scalable
as user has to change the DTS if they need upgrade to a new firmware.
Instead, add the firmware file name in the driver itself. As long as there
is no API change, new firmware upgrade is easy and require no driver
change. User is expected to copy the firmware image to the file system
and add a sym link to the new firmware for doing an upgrade. Driver add
a array of firmware file names to search for the available firmware blobs.
This scheme also prepare the driver for future changes to API if ever
happens. In such case it is assumed that driver needs to change to
accommodate the new firmware and new firmware file name will get added to
the array.Also update the DT document to remove the firmware attribute and add
description about firmware in the driver documentation.Signed-off-by: Murali Karicheri
Acked-by: Arnd Bergmann
Signed-off-by: Santosh Shilimkar
09 Oct, 2015
1 commit
-
When using accumulator queue for rx side for network driver, following
warning is seen when doing a reboot command from Linux console. This
is because, affinity value is not reset before calling free_irq(). This
patch fixes this.Deconfiguring network interfaces...
------------[ cut here ]-----------
WARNING: CPU: 0 PID: 2081 at kernel/irq/manage.c:1370
__free_irq+0x208/0x214
Modules linked in:
CPU: 0 PID: 2081 Comm: ifconfig Not tainted 4.1.5-00908-g1049e206-dirty #1
Hardware name: Keystone
Backtrace:
[] (dump_backtrace) from [] (show_stack+0x18/0x1c)
r7:c005d0a8 r6:c06e2184 r5:c06e2184 r4:00000000
[] (show_stack) from [] (dump_stack+0x8c/0xcc)
[] (dump_stack) from [] (warn_slowpath_common+0x88/0xb8)
r7:c005d0a8 r6:0000055a r5:00000009 r4:0000000
[] (warn_slowpath_common) from [] (warn_slowpath_null+0x
24/0x2c)
r8:0000006c r7:ee513f60 r6:ee513f00 r5:ee611010 r4:cc873a00
(warn_slowpath_null) from [] (__free_irq+0x208/0x214)
[] (__free_irq) from [] (free_irq+0x54/0xac)
r10:00000002 r9:00000000 r8:00000000 r7:ee611010
r6:0000006c r5:00000000
r4:ee513f00 r3:00000000
[] (free_irq) from [] (knav_range_setup_acc_irq+0xb0/0x1
28)
r7:00000001 r6:0000006c r5:ee611010 r4:00000001
[] (knav_range_setup_acc_irq) from [] (knav_acc_close_qu
eue+0x20/0x24)
r8:edd1a4c8 r7:00001000 r6:eed89980 r5:ee616650 r4:edf9d990
[] (knav_acc_close_queue) from [] (knav_queue_close+0xb4
/0xb8)
[] (knav_queue_close) from [] (netcp_free_navigator_reso
urces+0x1d4/0x2c0)
r5:edd1a480 r4:00000400
[] (netcp_free_navigator_resources) from
[] (netcp_ndo_stop+0x220/0x230)
r10:00008914 r9:edf34400 r8:00000000 r7:edd1a5d8 r6:edd1a480 r5:00000400
r4:edd1a000
[] (netcp_ndo_stop) from [ (__dev_close_many+0x90/0xd8)
r7:00001003 r6:00001042 r5:edb0de20 r4:edd1a000
[] (__dev_close_many) from [] (__dev_close+0x30/0x48)
r5:00000001 r4:edd1a000
[] (__dev_close) from [] (__dev_change_flags+0x9c/0x14c)
[] (__dev_change_flags) from [] (dev_change_flags+0x20/0r9:edf34400 r8:00000000 r7:00000000 r6:00001003 r5:edd1a138 r4:edd1a000
[] (dev_change_flags) from [] (devinet_ioctl+0x680/0x754r9:edf34400 r8:bef6af3c r7:00000000 r6:bef6ac64 r5:edf3440c r4:00000000
[] (devinet_ioctl) from [] (inet_ioctl+0x1a8/0x1d0)
r10:00000000 r9:edb0c000 r8:bef6ac64 r7:00000003 r6:bef6ac64 r5:bef6ac64
r4:00008914
[] (inet_ioctl) from [] (sock_ioctl+0x1d0/0x2a8)
[] (sock_ioctl) from [] (do_vfs_ioctl+0x414/0x604)
r7:00000003 r6:ed8b60c0 r5:bef6ac64 r4:ccc88f20
[] (do_vfs_ioctl) from [] (SyS_ioctl+0x3c/0x64)
r9:edb0c000 r8:bef6ac64 r7:00008914 r6:ed8b60c0 r5:00000003 r4:ed8b60c0
[] (SyS_ioctl) from [] (ret_fast_syscall+0x0/0x3c)
r9:edb0c000 r8:c000f924 r7:00000036 r6:0007e77c r5:bef6ac64 r4:0007e7d0
---[ end trace f565594c905af0b4 ]---Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar
Signed-off-by: Arnd Bergmann
30 Jan, 2015
3 commits
-
knav_range_setup_acc_irq() is used only within the file and should
be defined as static.Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar -
Currently configuring qmss and dma as dynamic module creates three .ko
files. knav_qmss_acc.ko and knav_qmss_queue.ko both can't be insmod
because of circular dependency. So combine these two into one module
by changing the makefile.Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar -
Currently only few of the API calls are exported. This creates problem
when the knav* modules are built as modules and another user module
such as netcp_core try to use these API calls and they are also built
as module. This patch export these APIs to address the issue.This is needed to support allmodconfig for ARM
Signed-off-by: Murali Karicheri
Signed-off-by: Santosh Shilimkar
15 Dec, 2014
1 commit
-
Pull driver core update from Greg KH:
"Here's the set of driver core patches for 3.19-rc1.They are dominated by the removal of the .owner field in platform
drivers. They touch a lot of files, but they are "simple" changes,
just removing a line in a structure.Other than that, a few minor driver core and debugfs changes. There
are some ath9k patches coming in through this tree that have been
acked by the wireless maintainers as they relied on the debugfs
changes.Everything has been in linux-next for a while"
* tag 'driver-core-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (324 commits)
Revert "ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries"
fs: debugfs: add forward declaration for struct device type
firmware class: Deletion of an unnecessary check before the function call "vunmap"
firmware loader: fix hung task warning dump
devcoredump: provide a one-way disable function
device: Add dev__once variants
ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries
ath: use seq_file api for ath9k debugfs files
debugfs: add helper function to create device related seq_file
drivers/base: cacheinfo: remove noisy error boot message
Revert "core: platform: add warning if driver has no owner"
drivers: base: support cpu cache information interface to userspace via sysfs
drivers: base: add cpu_device_create to support per-cpu devices
topology: replace custom attribute macros with standard DEVICE_ATTR*
cpumask: factor out show_cpumap into separate helper function
driver core: Fix unbalanced device reference in drivers_probe
driver core: fix race with userland in device_add()
sysfs/kernfs: make read requests on pre-alloc files use the buffer.
sysfs/kernfs: allow attributes to request write buffer be pre-allocated.
fs: sysfs: return EGBIG on write if offset is larger than file size
...
04 Nov, 2014
1 commit
-
list_for_each_entry_safe() is necessary if list objects are deleted from
the list while traversing it.Signed-off-by: Axel Lin
Signed-off-by: Santosh Shilimkar
28 Oct, 2014
3 commits
-
Return -ENOMEM if devm_kzalloc fails.
Signed-off-by: Axel Lin
Signed-off-by: Santosh Shilimkar -
Don't call mutex_unlock() in the error patch if the mutex_lock() is not called.
Signed-off-by: Axel Lin
Signed-off-by: Santosh Shilimkar -
Use list_first_entry_or_null() for first_region() and first_queue_range().
list_first_entry() expects the list is not empty, so first_region() and
first_queue_range() never return NULL.
Thus use list_first_entry_or_null() instead.Signed-off-by: Axel Lin
Signed-off-by: Santosh Shilimkar
20 Oct, 2014
1 commit
-
A platform_driver does not need to set an owner, it will be populated by the
driver core.Signed-off-by: Wolfram Sang
24 Sep, 2014
2 commits
-
The Keystone Navigator DMA driver sets up the dma channels and flows for
the QMSS(Queue Manager SubSystem) who triggers the actual data movements
across clients using destination queues. Every client modules like
NETCP(Network Coprocessor), SRIO(Serial Rapid IO) and CRYPTO
Engines has its own instance of packet dma hardware. QMSS has also
an internal packet DMA module which is used as an infrastructure
DMA with zero copy.Initially this driver was proposed as DMA engine driver but since the
hardware is not typical DMA engine and hence doesn't comply with typical
DMA engine driver needs, that approach was naked. Link to that
discussion -
https://lkml.org/lkml/2014/3/18/340As aligned, now we pair the Navigator DMA with its companion Navigator
QMSS subsystem driver.Cc: Greg Kroah-Hartman
Cc: Kumar Gala
Cc: Olof Johansson
Cc: Arnd Bergmann
Cc: Grant Likely
Cc: Rob Herring
Cc: Mark Rutland
Signed-off-by: Sandeep Nair
Signed-off-by: Santosh Shilimkar -
The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
the main hardware sub system which forms the backbone of the Keystone
Multi-core Navigator. QMSS consist of queue managers, packed-data structure
processors(PDSP), linking RAM, descriptor pools and infrastructure
Packet DMA.The Queue Manager is a hardware module that is responsible for accelerating
management of the packet queues. Packets are queued/de-queued by writing or
reading descriptor address to a particular memory mapped location. The PDSPs
perform QMSS related functions like accumulation, QoS, or event management.
Linking RAM registers are used to link the descriptors which are stored in
descriptor RAM. Descriptor RAM is configurable as internal or external memory.The QMSS driver manages the PDSP setups, linking RAM regions,
queue pool management (allocation, push, pop and notify) and descriptor
pool management. The specifics on the device tree bindings for
QMSS can be found in:
Documentation/devicetree/bindings/soc/keystone-navigator-qmss.txtCc: Greg Kroah-Hartman
Cc: Kumar Gala
Cc: Olof Johansson
Cc: Arnd Bergmann
Cc: Grant Likely
Cc: Rob Herring
Cc: Mark Rutland
Signed-off-by: Sandeep Nair
Signed-off-by: Santosh Shilimkar
