From: viresh kumar <viresh.kumar2@arm.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: viresh kumar <viresh.kumar@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
spear-devel <spear-devel@list.st.com>
Subject: Re: [PATCH 3/3] dw_dmac: set default alignment
Date: Fri, 13 Jul 2012 09:56:19 +0100 [thread overview]
Message-ID: <4FFFE2B3.3040306@arm.com> (raw)
In-Reply-To: <CAHp75VfiyLJKdSogHRDqU1TC-3icKAhCXa0hWbfnWEcNmJosTQ@mail.gmail.com>
On 13/07/12 09:45, Andy Shevchenko wrote:
>> > To understand it more, what does this mean? We will not support
>> > transfers with unaligned
>> > addresses/length to word size?
> The dmatest module uses those constants to get source, destination
> addresses and length of the test data aligned. On the other hand we
> can't use unaligned address in LLI because of the hardware restriction
> (2 bits are used for choosing AHB master).
To be clear, we can't use unaligned address of an LLI struct, but src/dest
address inside LLI can be unaligned.
I wanted to ask, will normal memcpy for anybody will work with unaligned addresses
with this patch? I believe they will.
--
Viresh
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2012-07-13 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 8:09 [PATCH 1/3] dw_dmac: mark dwc_dump_lli inline Andy Shevchenko
2012-07-13 8:09 ` [PATCH 2/3] dw_dmac: use 'u32' for LLI structure members, not dma_addr_t Andy Shevchenko
2012-07-13 8:27 ` viresh kumar
2012-07-13 8:09 ` [PATCH 3/3] dw_dmac: set default alignment Andy Shevchenko
2012-07-13 8:26 ` viresh kumar
2012-07-13 8:45 ` Andy Shevchenko
2012-07-13 8:56 ` viresh kumar [this message]
2012-07-13 10:04 ` Andy Shevchenko
2012-07-13 10:30 ` viresh kumar
2012-07-13 10:34 ` Andy Shevchenko
2012-07-13 8:27 ` [PATCH 1/3] dw_dmac: mark dwc_dump_lli inline viresh kumar
2012-07-16 6:34 ` Vinod Koul
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=4FFFE2B3.3040306@arm.com \
--to=viresh.kumar2@arm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.kumar@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