From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver
Date: Fri, 11 Mar 2016 16:49:50 -0500 [thread overview]
Message-ID: <1457732994-11175-1-git-send-email-okaya@codeaurora.org> (raw)
dma: add Qualcomm Technologies HIDMA driver
The Qualcomm Technologies HIDMA device has been designed
to support virtualization technology. The driver has been
divided into two to follow the hardware design.
1. HIDMA Management driver
2. HIDMA Channel driver
Each HIDMA HW consists of multiple channels. These channels
share some set of common parameters. These parameters are
initialized by the management driver during power up.
Same management driver is used for monitoring the execution
of the channels. Management driver can change the performance
behavior dynamically such as bandwidth allocation and
prioritization in the future.
The management driver is executed in host context and
is the main management entity for all channels provided by
the device.
------------------------
What's new
------------------------
- Coding style corrections.
- Correct OF node lookup.
------------------------
Git repos
------------------------
QEMU Support
https://www.codeaurora.org/cgit/quic/qemu/qemu/log/?h=v2.5.0-sriov
------------------------
History of Changes
------------------------
dma: qcom_hidma: add support for object hierarchy
Changes from V14: (https://lkml.org/lkml/2016/2/4/1089)
* use correct node (child) to read dma attribute.
dma: qcom_hidma: implement lower level hardware interface
Changes from V14: (https://lkml.org/lkml/2016/2/4/1086)
* renamed constants as HIDMA_xyz
dma: qcom_hidma: add support for object hierarchy
Changes from V14: (https://lkml.org/lkml/2016/2/4/1089)
* renamed constants as HIDMA_xyz
Sinan Kaya (4):
dma: qcom_hidma: implement lower level hardware interface
dma: qcom_hidma: add debugfs hooks
dma: qcom_hidma: add support for object hierarchy
dma: qcom_hidma: read the channel id from HW
Documentation/ABI/testing/sysfs-platform-hidma | 9 +
.../devicetree/bindings/dma/qcom_hidma_mgmt.txt | 3 -
drivers/dma/qcom/*Backtrace* | 4 +
drivers/dma/qcom/Makefile | 2 +
drivers/dma/qcom/hidma.c | 81 +-
drivers/dma/qcom/hidma.h | 20 +-
drivers/dma/qcom/hidma_dbg.c | 219 +++++
drivers/dma/qcom/hidma_ll.c | 918 +++++++++++++++++++++
drivers/dma/qcom/hidma_mgmt.c | 111 ++-
9 files changed, 1313 insertions(+), 54 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma
create mode 100644 drivers/dma/qcom/*Backtrace*
create mode 100644 drivers/dma/qcom/hidma_dbg.c
create mode 100644 drivers/dma/qcom/hidma_ll.c
--
1.8.2.1
next reply other threads:[~2016-03-11 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 21:49 Sinan Kaya [this message]
2016-03-11 21:49 ` [PATCH V15 1/4] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 2/4] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 3/4] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-03-11 21:49 ` [PATCH 4/4] dma: qcom_hidma: read the channel id from HW Sinan Kaya
2016-03-18 20:06 ` Rob Herring
2016-03-20 9:39 ` [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver Vinod Koul
2016-03-20 13:30 ` okaya at codeaurora.org
2016-03-27 13:11 ` okaya at codeaurora.org
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=1457732994-11175-1-git-send-email-okaya@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).