public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod <vkoul@kernel.org>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
	dan.j.williams@intel.com, xuwei5@hisilicon.com,
	catalin.marinas@arm.com, will.deacon@arm.com,
	liyu65@hisilicon.com, suzhuangluan@hisilicon.com,
	xuhongtao8@hisilicon.com, zhongkaihua@huawei.com,
	xuezhiliang@hisilicon.com, xupeng7@huawei.com,
	sunliang10@huawei.com, fengbaopeng@hisilicon.com,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: k3dma: add optional property hisilicon,dma-min-chan
Date: Mon, 9 Jul 2018 16:04:38 +0530	[thread overview]
Message-ID: <20180709103438.GC22377@vkoul-mobl> (raw)
In-Reply-To: <20180706035521.13736-2-guodong.xu@linaro.org>

On 06-07-18, 11:55, Guodong Xu wrote:
> From: Li Yu <liyu65@hisilicon.com>
> 
> Add optional property hisilicon,dma-min-chan for k3dma.
> 
> Signed-off-by: Li Yu <liyu65@hisilicon.com>
> Signed-off-by: Guodong Xu <guodong.xu@linaro.org>
> ---
>  Documentation/devicetree/bindings/dma/k3dma.txt | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/dma/k3dma.txt b/Documentation/devicetree/bindings/dma/k3dma.txt
> index 4945aeac4dc4..f34202a80f3c 100644
> --- a/Documentation/devicetree/bindings/dma/k3dma.txt
> +++ b/Documentation/devicetree/bindings/dma/k3dma.txt
> @@ -12,6 +12,11 @@ Required properties:
>  		have specific request line
>  - clocks: clock required
>  
> +Optional properties:
> +- hisilicon,dma-min-chan: the minimum DMA channel number which is usable
> +		Default value is 0, but in some platform it is
> +		configured 1, like in hi3660 platform
> +
>  Example:
>  
>  Controller:
> @@ -21,6 +26,7 @@ Controller:
>  			#dma-cells = <1>;
>  			dma-channels = <16>;
>  			dma-requests = <27>;
> +			hisilicon,dma-min-chan = <1>;

Am still expecting this to be a mask

-- 
~Vinod

  reply	other threads:[~2018-07-09 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06  3:55 [PATCH v2 0/4] k3dma: add support to reserved channels Guodong Xu
2018-07-06  3:55 ` [PATCH v2 1/4] dt-bindings: k3dma: add optional property hisilicon,dma-min-chan Guodong Xu
2018-07-09 10:34   ` Vinod [this message]
2018-07-11 16:09     ` Rob Herring
2018-07-06  3:55 ` [PATCH v2 2/4] k3dma: add support to reserved minimum channels Guodong Xu
2018-07-06  3:55 ` [PATCH v2 3/4] arm64: dts: hi3660: update property name hisilicon,dma-min-chan Guodong Xu
2018-07-06  3:55 ` [PATCH v2 4/4] k3dma: delete axi_config Guodong Xu

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=20180709103438.GC22377@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fengbaopeng@hisilicon.com \
    --cc=guodong.xu@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liyu65@hisilicon.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sunliang10@huawei.com \
    --cc=suzhuangluan@hisilicon.com \
    --cc=will.deacon@arm.com \
    --cc=xuezhiliang@hisilicon.com \
    --cc=xuhongtao8@hisilicon.com \
    --cc=xupeng7@huawei.com \
    --cc=xuwei5@hisilicon.com \
    --cc=zhongkaihua@huawei.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