From: Mugunthan V N <mugunthanvnm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] dm: implement a DMA uclass
Date: Wed, 2 Dec 2015 14:41:09 +0530 [thread overview]
Message-ID: <565EB5AD.60603@ti.com> (raw)
In-Reply-To: <565EA920.9000405@ti.com>
On Wednesday 02 December 2015 01:47 PM, Mugunthan V N wrote:
>>> + DMA_TRANS_NONE,
>> >
>> > What does that mean?
> DMA driver will be having only one transfer api and to identify what
> kind of transfer that the user driver is expecting, these enums are used.
>
Oops, I was taking your comment for the whole enums. Thought of having
an error enum as DMA_TRANS_NONE, but it doesn't add value, will remove
it in next version.
Regards
Mugunthan V N
next prev parent reply other threads:[~2015-12-02 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 11:13 [U-Boot] [PATCH 0/6] add dma uclass implementation and adopt ti-edma3 to it Mugunthan V N
2015-12-01 11:13 ` [U-Boot] [PATCH 1/6] dm: implement a DMA uclass Mugunthan V N
2015-12-01 21:54 ` Simon Glass
2015-12-02 8:17 ` Mugunthan V N
2015-12-02 9:11 ` Mugunthan V N [this message]
2015-12-01 11:13 ` [U-Boot] [PATCH 2/6] dma: Kconfig: Add TI_EDMA3 entry Mugunthan V N
2015-12-01 21:54 ` Simon Glass
2015-12-01 11:13 ` [U-Boot] [PATCH 3/6] sf: sf_ops: use dma to copy data from mmap region if platform supports Mugunthan V N
2015-12-01 21:54 ` Simon Glass
2015-12-02 9:45 ` Mugunthan V N
2015-12-02 21:05 ` Simon Glass
2015-12-01 11:13 ` [U-Boot] [PATCH 4/6] spi: ti_qspi: compile out spi_flash_copy_mmap when DM_DMA is defined Mugunthan V N
2015-12-01 21:54 ` Simon Glass
2015-12-01 11:13 ` [U-Boot] [PATCH 5/6] drivers: dma: ti-edma3: convert driver to adopt driver model Mugunthan V N
2015-12-01 21:54 ` Simon Glass
2015-12-02 9:47 ` Mugunthan V N
2015-12-01 11:13 ` [U-Boot] [PATCH 6/6] defconfig: am437x_sk_evm: enable dma " Mugunthan V N
2015-12-01 21:54 ` Simon Glass
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=565EB5AD.60603@ti.com \
--to=mugunthanvnm@ti.com \
--cc=u-boot@lists.denx.de \
/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.