From: Viresh Kumar <viresh.kumar@linaro.org> To: vinod.koul@intel.com Cc: linux-kernel@vger.kernel.org, spear-devel@list.st.com, andriy.shevchenko@linux.intel.com, linux-arm-kernel@lists.infradead.org, devicetree-discuss@lists.ozlabs.org, Viresh Kumar <viresh.kumar@linaro.org> Subject: [PATCH V2 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Date: Fri, 12 Oct 2012 20:01:41 +0530 [thread overview] Message-ID: <142ef9170a2c69657d8a05ac127a9970d7b04965.1350051925.git.viresh.kumar@linaro.org> (raw) Documentation style comments were missing for few fields in struct dw_dma_platform_data. Add these. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- include/linux/dw_dmac.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/dw_dmac.h b/include/linux/dw_dmac.h index e1c8c9e..62a6190 100644 --- a/include/linux/dw_dmac.h +++ b/include/linux/dw_dmac.h @@ -19,6 +19,8 @@ * @nr_channels: Number of channels supported by hardware (max 8) * @is_private: The device channels should be marked as private and not for * by the general purpose DMA channel allocator. + * @chan_allocation_order: Allocate channels starting from 0 or 7 + * @chan_priority: Set channel priority increasing from 0 to 7 or 7 to 0. * @block_size: Maximum block size supported by the controller * @nr_masters: Number of AHB masters supported by the controller * @data_width: Maximum data width supported by hardware per AHB master -- 1.7.12.rc2.18.g61b472e
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V2 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Date: Fri, 12 Oct 2012 20:01:41 +0530 [thread overview] Message-ID: <142ef9170a2c69657d8a05ac127a9970d7b04965.1350051925.git.viresh.kumar@linaro.org> (raw) Documentation style comments were missing for few fields in struct dw_dma_platform_data. Add these. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- include/linux/dw_dmac.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/dw_dmac.h b/include/linux/dw_dmac.h index e1c8c9e..62a6190 100644 --- a/include/linux/dw_dmac.h +++ b/include/linux/dw_dmac.h @@ -19,6 +19,8 @@ * @nr_channels: Number of channels supported by hardware (max 8) * @is_private: The device channels should be marked as private and not for * by the general purpose DMA channel allocator. + * @chan_allocation_order: Allocate channels starting from 0 or 7 + * @chan_priority: Set channel priority increasing from 0 to 7 or 7 to 0. * @block_size: Maximum block size supported by the controller * @nr_masters: Number of AHB masters supported by the controller * @data_width: Maximum data width supported by hardware per AHB master -- 1.7.12.rc2.18.g61b472e
next reply other threads:[~2012-10-12 14:32 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-12 14:31 Viresh Kumar [this message] 2012-10-12 14:31 ` [PATCH V2 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Viresh Kumar 2012-10-12 14:31 ` [PATCH V2 2/3] dmaengine: dw_dmac: Enhance device tree support Viresh Kumar 2012-10-12 14:31 ` Viresh Kumar 2012-10-12 14:50 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 14:50 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 14:55 ` Viresh Kumar 2012-10-12 14:55 ` Viresh Kumar 2012-10-12 16:20 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 16:20 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 17:14 ` Viresh Kumar 2012-10-12 17:14 ` Viresh Kumar 2012-10-12 14:58 ` Andy Shevchenko 2012-10-12 14:58 ` Andy Shevchenko 2012-10-12 15:18 ` Viresh Kumar 2012-10-12 15:18 ` Viresh Kumar 2012-10-12 15:53 ` Andy Shevchenko 2012-10-12 15:53 ` Andy Shevchenko 2012-10-12 15:55 ` Viresh Kumar 2012-10-12 15:55 ` Viresh Kumar 2012-10-15 3:29 ` Viresh Kumar 2012-10-15 3:29 ` Viresh Kumar 2012-10-15 7:35 ` Andy Shevchenko 2012-10-15 7:35 ` Andy Shevchenko 2012-10-12 14:31 ` [PATCH V2 3/3] ARM: SPEAr13xx: Pass DW DMAC platform data from DT Viresh Kumar 2012-10-12 14:31 ` Viresh Kumar 2012-10-12 14:48 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 14:48 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 14:48 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 14:52 ` Viresh Kumar 2012-10-12 14:52 ` Viresh Kumar 2012-10-12 16:21 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 16:21 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-12 17:12 ` Viresh Kumar 2012-10-12 17:12 ` Viresh Kumar 2012-10-13 6:44 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-13 6:44 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-13 8:48 ` Viresh Kumar 2012-10-13 8:48 ` Viresh Kumar 2012-10-13 12:22 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-13 12:22 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-13 12:22 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-13 14:08 ` Viresh Kumar 2012-10-13 14:08 ` Viresh Kumar 2012-10-13 14:10 ` Viresh Kumar 2012-10-13 14:10 ` Viresh Kumar 2012-10-14 10:01 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-14 10:01 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-14 10:01 ` Jean-Christophe PLAGNIOL-VILLARD 2012-10-15 3:21 ` Viresh Kumar 2012-10-15 3:21 ` Viresh Kumar
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=142ef9170a2c69657d8a05ac127a9970d7b04965.1350051925.git.viresh.kumar@linaro.org \ --to=viresh.kumar@linaro.org \ --cc=andriy.shevchenko@linux.intel.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=spear-devel@list.st.com \ --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: linkBe 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.