devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: Marc Zyngier <marc.zyngier@arm.com>, Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	arnd@arndb.de, vinod.koul@intel.com, jcm@redhat.com,
	timur@codeaurora.org, linux-kernel@vger.kernel.org,
	agross@codeaurora.org, dmaengine@vger.kernel.org,
	kvmarm@lists.cs.columbia.edu, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver
Date: Fri, 15 Jan 2016 17:47:52 -0500	[thread overview]
Message-ID: <56997718.70707@codeaurora.org> (raw)
In-Reply-To: <56992D16.6070800@arm.com>

On 1/15/2016 12:32 PM, Marc Zyngier wrote:
>>> Do you have a link to that? Seeing it would help to ease my concerns.
>> > 
>> > The QEMU driver has not been posted yet. As far as I know, it just discovers the memory
>> > resources on the platform object and creates mappings for the guest machine only. 
>> > 
>> > Shanker Donthineni and Vikram Sethi will post the QEMU patch later.
> Then may I suggest you both synchronize your submissions? I'd really
> like to hear from the QEMU maintainers that they are satisfied with that
> side of the story as well.

The HIDMA QEMU driver is also based on VFIO platform driver in QEMU. It is not a new concept
or new framework. All tried and tested solutions. 

The driver below is already using this feature. HIDMA is no exception. 
I have verified functionality of HIDMA linux driver with HIDMA QEMU driver already.

https://lxr.missinglinkelectronics.com/qemu/hw/arm/sysbus-fdt.c#L67
https://lxr.missinglinkelectronics.com/qemu/hw/vfio/calxeda-xgmac.c#L18
https://lxr.missinglinkelectronics.com/qemu/include/hw/vfio/vfio-calxeda-xgmac.h 



-- 
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

  reply	other threads:[~2016-01-15 22:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 14:45 [PATCH v12 0/7] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 1/7] dma: qcom_bam_dma: move to qcom directory Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 2/7] dma: hidma: Add Device Tree support Sinan Kaya
2016-01-15 15:16   ` Mark Rutland
2016-01-15 15:30     ` Mark Rutland
2016-01-15 17:05       ` Sinan Kaya
2016-01-18 11:39         ` Mark Rutland
2016-01-15 16:49     ` Sinan Kaya
     [not found]       ` <5699232E.60809-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-18 11:49         ` Mark Rutland
2016-01-18 14:04           ` Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver Sinan Kaya
2016-01-15 14:56   ` Mark Rutland
2016-01-15 15:12     ` Sinan Kaya
2016-01-15 15:22       ` Mark Rutland
2016-01-15 17:16         ` Sinan Kaya
     [not found]           ` <56992987.5080603-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-15 17:32             ` Marc Zyngier
2016-01-15 22:47               ` Sinan Kaya [this message]
2016-01-18  9:06                 ` Marc Zyngier
2016-01-22 18:38         ` Sinan Kaya
2016-01-15 15:14     ` Marc Zyngier
2016-01-15 15:36       ` Mark Rutland
2016-01-15 16:01         ` Sinan Kaya
2016-01-20 22:18           ` Sinan Kaya
2016-01-15 15:40       ` Sinan Kaya
     [not found]         ` <569912F3.9040507-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-15 17:28           ` Marc Zyngier
2016-01-15 17:44             ` Sinan Kaya
2016-01-15 18:08               ` Marc Zyngier
2016-01-11 14:45 ` [PATCH V12 4/7] dma: add Qualcomm Technologies HIDMA channel driver Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 5/7] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 6/7] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 7/7] dma: qcom_hidma: add support for object hierarchy Sinan Kaya

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=56997718.70707@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=agross@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=jcm@redhat.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=timur@codeaurora.org \
    --cc=vinod.koul@intel.com \
    /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).