Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
On 1/3/2016 10:36 PM, Vinod Koul wrote: > On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote: >> Hi Vinod, >> >>> >> >> Can I have your ACK on your series if you are OK? > > Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on > DT patches first :) > You are right about merge. I was interested in to see if you had any outstanding questions. I know I addressed your tx_status question. Mark, Arnd; Can I have your ack for the series if you are OK? I think we have beaten the patches enough. Sinan -- Sinan Kaya Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote: > Hi Vinod, > > > > > Can I have your ACK on your series if you are OK? Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on DT patches first :) -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
Hi Vinod,
On 1/3/2016 7:06 PM, Sinan Kaya wrote:
> 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 hypervisor context and
> is the main management entity for all channels provided by
> the device.
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/454)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/448)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/449)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/451)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/452)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/453)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/450)
> * Clean up style issues
> * make depend on CONFIG_OF_IRQ too as SPARC arch doesn't seem to define
> CONFIG_OF_IRQ but it defines CONFIG_OF.
>
> Sinan Kaya (7):
> dma: qcom_bam_dma: move to qcom directory
> dma: hidma: Add Device Tree support
> dma: add Qualcomm Technologies HIDMA management driver
> dma: add Qualcomm Technologies HIDMA channel driver
> dma: qcom_hidma: implement lower level hardware interface
> dma: qcom_hidma: add debugfs hooks
> dma: qcom_hidma: add support for object hierarchy
>
> Documentation/ABI/testing/sysfs-platform-hidma | 9 +
> .../ABI/testing/sysfs-platform-hidma-mgmt | 97 +++
> .../devicetree/bindings/dma/qcom_hidma_mgmt.txt| 79 ++
> drivers/dma/Kconfig| 11 +-
> drivers/dma/Makefile | 2 +-
> drivers/dma/qcom/Kconfig | 29 +
> drivers/dma/qcom/Makefile | 5 +
> drivers/dma/{qcom_bam_dma.c => qcom/bam_dma.c} | 4 +-
> drivers/dma/qcom/hidma.c | 784 +
> drivers/dma/qcom/hidma.h | 162
> drivers/dma/qcom/hidma_dbg.c | 219 +
> drivers/dma/qcom/hidma_ll.c| 927
> +
> drivers/dma/qcom/hidma_mgmt.c | 400 +
> drivers/dma/qcom/hidma_mgmt.h | 39 +
> drivers/dma/qcom/hidma_mgmt_sys.c | 295 +++
> 15 files changed, 3050 insertions(+), 12 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma
> create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma-mgmt
> create mode 100644 Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt
> create mode 100644 drivers/dma/qcom/Kconfig
> create mode 100644 drivers/dma/qcom/Makefile
> rename drivers/dma/{qcom_bam_dma.c => qcom/bam_dma.c} (99%)
> create mode 100644 drivers/dma/qcom/hidma.c
> create mode 100644 drivers/dma/qcom/hidma.h
> create mode 100644 drivers/dma/qcom/hidma_dbg.c
> create mode 100644 drivers/dma/qcom/hidma_ll.c
> create mode 100644 drivers/dma/qcom/hidma_mgmt.c
> create mode 100644 drivers/dma/qcom/hidma_mgmt.h
> create mode 100644 drivers/dma/qcom/hidma_mgmt_sys.c
>
Can I have your ACK on your series if you are OK?
Sinan
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
Hi Vinod,
On 1/3/2016 7:06 PM, Sinan Kaya wrote:
> 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 hypervisor context and
> is the main management entity for all channels provided by
> the device.
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/454)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/448)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/449)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/451)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/452)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/453)
> * none
>
> Changes from V10: (https://lkml.org/lkml/2015/12/17/450)
> * Clean up style issues
> * make depend on CONFIG_OF_IRQ too as SPARC arch doesn't seem to define
> CONFIG_OF_IRQ but it defines CONFIG_OF.
>
> Sinan Kaya (7):
> dma: qcom_bam_dma: move to qcom directory
> dma: hidma: Add Device Tree support
> dma: add Qualcomm Technologies HIDMA management driver
> dma: add Qualcomm Technologies HIDMA channel driver
> dma: qcom_hidma: implement lower level hardware interface
> dma: qcom_hidma: add debugfs hooks
> dma: qcom_hidma: add support for object hierarchy
>
> Documentation/ABI/testing/sysfs-platform-hidma | 9 +
> .../ABI/testing/sysfs-platform-hidma-mgmt | 97 +++
> .../devicetree/bindings/dma/qcom_hidma_mgmt.txt| 79 ++
> drivers/dma/Kconfig| 11 +-
> drivers/dma/Makefile | 2 +-
> drivers/dma/qcom/Kconfig | 29 +
> drivers/dma/qcom/Makefile | 5 +
> drivers/dma/{qcom_bam_dma.c => qcom/bam_dma.c} | 4 +-
> drivers/dma/qcom/hidma.c | 784 +
> drivers/dma/qcom/hidma.h | 162
> drivers/dma/qcom/hidma_dbg.c | 219 +
> drivers/dma/qcom/hidma_ll.c| 927
> +
> drivers/dma/qcom/hidma_mgmt.c | 400 +
> drivers/dma/qcom/hidma_mgmt.h | 39 +
> drivers/dma/qcom/hidma_mgmt_sys.c | 295 +++
> 15 files changed, 3050 insertions(+), 12 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma
> create mode 100644 Documentation/ABI/testing/sysfs-platform-hidma-mgmt
> create mode 100644 Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt
> create mode 100644 drivers/dma/qcom/Kconfig
> create mode 100644 drivers/dma/qcom/Makefile
> rename drivers/dma/{qcom_bam_dma.c => qcom/bam_dma.c} (99%)
> create mode 100644 drivers/dma/qcom/hidma.c
> create mode 100644 drivers/dma/qcom/hidma.h
> create mode 100644 drivers/dma/qcom/hidma_dbg.c
> create mode 100644 drivers/dma/qcom/hidma_ll.c
> create mode 100644 drivers/dma/qcom/hidma_mgmt.c
> create mode 100644 drivers/dma/qcom/hidma_mgmt.h
> create mode 100644 drivers/dma/qcom/hidma_mgmt_sys.c
>
Can I have your ACK on your series if you are OK?
Sinan
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
On 1/3/2016 10:36 PM, Vinod Koul wrote: > On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote: >> Hi Vinod, >> >>> >> >> Can I have your ACK on your series if you are OK? > > Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on > DT patches first :) > You are right about merge. I was interested in to see if you had any outstanding questions. I know I addressed your tx_status question. Mark, Arnd; Can I have your ack for the series if you are OK? I think we have beaten the patches enough. Sinan -- Sinan Kaya Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH V11 0/7] dma: add Qualcomm Technologies HIDMA driver
On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote: > Hi Vinod, > > > > > Can I have your ACK on your series if you are OK? Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on DT patches first :) -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
