From: Sinan Kaya <okaya@codeaurora.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
arnd@arndb.de, Marc Zyngier <marc.zyngier@arm.com>,
jcm@redhat.com, timur@codeaurora.org,
linux-kernel@vger.kernel.org, vinod.koul@intel.com,
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: Wed, 20 Jan 2016 17:18:29 -0500 [thread overview]
Message-ID: <56A007B5.9070502@codeaurora.org> (raw)
In-Reply-To: <569917C7.9000804@codeaurora.org>
Mark,
On 1/15/2016 11:01 AM, Sinan Kaya wrote:
>> I'm concerned with how this is safe, and with the userspace interface.
>> > e.g. if the user wants to up the QoS for a VM, how to they find the
>> > right channel in sysfs to alter?
> The HW supports changing the QoS values on the flight. In order to locate the
> object, I'm exporting a
>
> I tried to address your concern on v10 last series. Here is brief summary.
>
> Each channel device has a sysfs entry named chid.
> What: /sys/devices/platform/hidma-*/chid
> + /sys/devices/platform/QCOM8061:*/chid
>
>
> Each management object has one priority and weight file per channel.
> +What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
> + /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
>
> Suppose you want to change the priority of a channel you assigned to guess,
> the userspace application goes and reads the chid value of the channel.
>
> Then goes to chanops/chan<chid>/ directory and can change priority and weight
> parameters here.
>
> Here is how the directory looks like. QCOM8060:00 is a management object.
> QCOM8061:0x are the channel objects.
>
> /sys/devices/platform/QCOM8060:00# ls
> QCOM8061:00
> QCOM8061:01
> QCOM8061:02
> QCOM8061:03
> QCOM8061:04
> QCOM8061:05
> chanops
> <other common attributes>
>
>
>
>
Did this answer your question?
I'm capturing all the questions and answers as FAQ into the cover letter as I keep
repeating myself for every single reviewer.
Besides from the "lack of documentation", is there any code related change you'd like to
discuss in the series.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver
Date: Wed, 20 Jan 2016 17:18:29 -0500 [thread overview]
Message-ID: <56A007B5.9070502@codeaurora.org> (raw)
In-Reply-To: <569917C7.9000804@codeaurora.org>
Mark,
On 1/15/2016 11:01 AM, Sinan Kaya wrote:
>> I'm concerned with how this is safe, and with the userspace interface.
>> > e.g. if the user wants to up the QoS for a VM, how to they find the
>> > right channel in sysfs to alter?
> The HW supports changing the QoS values on the flight. In order to locate the
> object, I'm exporting a
>
> I tried to address your concern on v10 last series. Here is brief summary.
>
> Each channel device has a sysfs entry named chid.
> What: /sys/devices/platform/hidma-*/chid
> + /sys/devices/platform/QCOM8061:*/chid
>
>
> Each management object has one priority and weight file per channel.
> +What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
> + /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
>
> Suppose you want to change the priority of a channel you assigned to guess,
> the userspace application goes and reads the chid value of the channel.
>
> Then goes to chanops/chan<chid>/ directory and can change priority and weight
> parameters here.
>
> Here is how the directory looks like. QCOM8060:00 is a management object.
> QCOM8061:0x are the channel objects.
>
> /sys/devices/platform/QCOM8060:00# ls
> QCOM8061:00
> QCOM8061:01
> QCOM8061:02
> QCOM8061:03
> QCOM8061:04
> QCOM8061:05
> chanops
> <other common attributes>
>
>
>
>
Did this answer your question?
I'm capturing all the questions and answers as FAQ into the cover letter as I keep
repeating myself for every single reviewer.
Besides from the "lack of documentation", is there any code related change you'd like to
discuss in the series.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
dmaengine@vger.kernel.org, timur@codeaurora.org,
devicetree@vger.kernel.org, cov@codeaurora.org,
vinod.koul@intel.com, jcm@redhat.com, agross@codeaurora.org,
arnd@arndb.de, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
christoffer.dall@linaro.org
Subject: Re: [PATCH V12 3/7] dma: add Qualcomm Technologies HIDMA management driver
Date: Wed, 20 Jan 2016 17:18:29 -0500 [thread overview]
Message-ID: <56A007B5.9070502@codeaurora.org> (raw)
In-Reply-To: <569917C7.9000804@codeaurora.org>
Mark,
On 1/15/2016 11:01 AM, Sinan Kaya wrote:
>> I'm concerned with how this is safe, and with the userspace interface.
>> > e.g. if the user wants to up the QoS for a VM, how to they find the
>> > right channel in sysfs to alter?
> The HW supports changing the QoS values on the flight. In order to locate the
> object, I'm exporting a
>
> I tried to address your concern on v10 last series. Here is brief summary.
>
> Each channel device has a sysfs entry named chid.
> What: /sys/devices/platform/hidma-*/chid
> + /sys/devices/platform/QCOM8061:*/chid
>
>
> Each management object has one priority and weight file per channel.
> +What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
> + /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
>
> Suppose you want to change the priority of a channel you assigned to guess,
> the userspace application goes and reads the chid value of the channel.
>
> Then goes to chanops/chan<chid>/ directory and can change priority and weight
> parameters here.
>
> Here is how the directory looks like. QCOM8060:00 is a management object.
> QCOM8061:0x are the channel objects.
>
> /sys/devices/platform/QCOM8060:00# ls
> QCOM8061:00
> QCOM8061:01
> QCOM8061:02
> QCOM8061:03
> QCOM8061:04
> QCOM8061:05
> chanops
> <other common attributes>
>
>
>
>
Did this answer your question?
I'm capturing all the questions and answers as FAQ into the cover letter as I keep
repeating myself for every single reviewer.
Besides from the "lack of documentation", is there any code related change you'd like to
discuss in the series.
--
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
next prev parent reply other threads:[~2016-01-20 22:14 UTC|newest]
Thread overview: 77+ 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 ` 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 ` Sinan Kaya
2016-01-11 14:45 ` Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 2/7] dma: hidma: Add Device Tree support Sinan Kaya
2016-01-11 14:45 ` Sinan Kaya
2016-01-11 14:45 ` Sinan Kaya
2016-01-15 15:16 ` Mark Rutland
2016-01-15 15:16 ` Mark Rutland
2016-01-15 15:30 ` Mark Rutland
2016-01-15 15:30 ` Mark Rutland
2016-01-15 17:05 ` Sinan Kaya
2016-01-15 17:05 ` Sinan Kaya
2016-01-18 11:39 ` Mark Rutland
2016-01-18 11:39 ` Mark Rutland
2016-01-15 16:49 ` Sinan Kaya
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 11:49 ` Mark Rutland
2016-01-18 11:49 ` Mark Rutland
2016-01-18 14:04 ` Sinan Kaya
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-11 14:45 ` Sinan Kaya
2016-01-15 14:56 ` Mark Rutland
2016-01-15 14:56 ` Mark Rutland
2016-01-15 14:56 ` Mark Rutland
2016-01-15 15:12 ` Sinan Kaya
2016-01-15 15:12 ` Sinan Kaya
2016-01-15 15:12 ` Sinan Kaya
2016-01-15 15:22 ` Mark Rutland
2016-01-15 15:22 ` Mark Rutland
2016-01-15 15:22 ` Mark Rutland
2016-01-15 17:16 ` Sinan Kaya
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 17:32 ` Marc Zyngier
2016-01-15 17:32 ` Marc Zyngier
2016-01-15 22:47 ` Sinan Kaya
2016-01-15 22:47 ` Sinan Kaya
2016-01-15 22:47 ` Sinan Kaya
2016-01-18 9:06 ` Marc Zyngier
2016-01-18 9:06 ` Marc Zyngier
2016-01-18 9:06 ` Marc Zyngier
2016-01-22 18:38 ` Sinan Kaya
2016-01-22 18:38 ` Sinan Kaya
2016-01-22 18:38 ` Sinan Kaya
2016-01-15 15:14 ` Marc Zyngier
2016-01-15 15:14 ` Marc Zyngier
2016-01-15 15:14 ` Marc Zyngier
2016-01-15 15:36 ` Mark Rutland
2016-01-15 15:36 ` Mark Rutland
2016-01-15 16:01 ` Sinan Kaya
2016-01-15 16:01 ` Sinan Kaya
2016-01-15 16:01 ` Sinan Kaya
2016-01-20 22:18 ` Sinan Kaya [this message]
2016-01-20 22:18 ` Sinan Kaya
2016-01-20 22:18 ` Sinan Kaya
2016-01-15 15:40 ` Sinan Kaya
2016-01-15 15:40 ` 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:28 ` Marc Zyngier
2016-01-15 17:28 ` Marc Zyngier
2016-01-15 17:44 ` Sinan Kaya
2016-01-15 17:44 ` Sinan Kaya
2016-01-15 18:08 ` Marc Zyngier
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 ` 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 ` Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 6/7] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-01-11 14:45 ` Sinan Kaya
2016-01-11 14:45 ` [PATCH V12 7/7] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-01-11 14:45 ` 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=56A007B5.9070502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.