From: Vinod Koul <vkoul@kernel.org>
To: Amit Singh Tomar <amittomer25@gmail.com>
Cc: andre.przywara@arm.com, afaerber@suse.de,
manivannan.sadhasivam@linaro.org, dan.j.williams@intel.com,
cristian.ciocaltea@gmail.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org
Subject: Re: [PATCH v7 02/10] dmaengine: Actions: get rid of bit fields from dma descriptor
Date: Mon, 27 Jul 2020 14:44:01 +0530 [thread overview]
Message-ID: <20200727091401.GQ12965@vkoul-mobl> (raw)
In-Reply-To: <1595180527-11320-3-git-send-email-amittomer25@gmail.com>
On 19-07-20, 23:11, Amit Singh Tomar wrote:
> At the moment, Driver uses bit fields to describe registers of the DMA
> descriptor structure that makes it less portable and maintainable, and
> Andre suugested(and even sketched important bits for it) to make use of
> array to describe this DMA descriptors instead. It gives the flexibility
> while extending support for other platform such as Actions S700.
>
> This commit removes the "owl_dma_lli_hw" (that includes bit-fields) and
> uses array to describe DMA descriptor.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2020-07-27 9:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 17:41 [PATCH v7 00/10] Add MMC and DMA support for Actions S700 Amit Singh Tomar
2020-07-19 17:41 ` [PATCH v7 01/10] dt-bindings: dmaengine: convert Actions Semi Owl SoCs bindings to yaml Amit Singh Tomar
2020-07-20 19:16 ` Rob Herring
2020-07-27 9:13 ` Vinod Koul
2020-07-19 17:41 ` [PATCH v7 02/10] dmaengine: Actions: get rid of bit fields from dma descriptor Amit Singh Tomar
2020-07-27 9:14 ` Vinod Koul [this message]
2020-07-19 17:42 ` [PATCH v7 03/10] dmaengine: Actions: Add support for S700 DMA engine Amit Singh Tomar
2020-07-27 9:14 ` Vinod Koul
2020-07-19 17:42 ` [PATCH v7 04/10] clk: actions: Add MMC clock-register reset bits Amit Singh Tomar
2020-08-28 11:54 ` Manivannan Sadhasivam
2020-08-28 12:00 ` Manivannan Sadhasivam
2020-07-19 17:42 ` [PATCH v7 05/10] arm64: dts: actions: limit address range for pinctrl node Amit Singh Tomar
2020-09-22 6:58 ` Manivannan Sadhasivam
2020-07-19 17:42 ` [PATCH v7 06/10] arm64: dts: actions: Add DMA Controller for S700 Amit Singh Tomar
2020-09-22 7:00 ` Manivannan Sadhasivam
2020-07-19 17:42 ` [PATCH v7 07/10] dt-bindings: reset: s700: Add binding constants for mmc Amit Singh Tomar
2020-08-28 11:57 ` Manivannan Sadhasivam
2020-09-11 5:29 ` Amit Singh Tomar
2020-12-15 14:12 ` Amit Tomer
2020-07-19 17:42 ` [PATCH v7 08/10] dt-bindings: mmc: owl: add compatible string actions,s700-mmc Amit Singh Tomar
2020-08-28 11:59 ` Manivannan Sadhasivam
2020-09-11 5:24 ` Amit Singh Tomar
2020-09-24 12:49 ` Ulf Hansson
2020-07-19 17:42 ` [PATCH v7 09/10] arm64: dts: actions: Add MMC controller support for S700 Amit Singh Tomar
2020-09-22 7:03 ` Manivannan Sadhasivam
2020-07-19 17:42 ` [PATCH v7 10/10] arm64: dts: actions: Add uSD support for Cubieboard7 Amit Singh Tomar
2020-07-20 5:36 ` Manivannan Sadhasivam
2020-09-22 7:03 ` Manivannan Sadhasivam
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=20200727091401.GQ12965@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=afaerber@suse.de \
--cc=amittomer25@gmail.com \
--cc=andre.przywara@arm.com \
--cc=cristian.ciocaltea@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/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).