From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] DMA: Fix allocation size for PL330 data buffer depth.
Date: Wed, 12 Nov 2014 15:09:52 +0530 [thread overview]
Message-ID: <20141112093952.GD24582@intel.com> (raw)
In-Reply-To: <1415294412-13818-1-git-send-email-Liviu.Dudau@arm.com>
On Thu, Nov 06, 2014 at 05:20:12PM +0000, Liviu Dudau wrote:
> The datasheet for PL330 says that the data buffer value in the CRD
> register is 10bits wide. However, the value stored is "minus one",
> which the driver corrects for. Maximum value that the data buffer
> depth can have is 1024 lines, which requires 11 bits for storage.
>
> While making updates I found printing the peripheral ID as a hex
> value to be more useful as the datasheet shows the values that way.
Applied, thanks
Please snure you use the right subsytem name
--
~Vinod
next prev parent reply other threads:[~2014-11-12 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 17:20 [PATCH] DMA: Fix allocation size for PL330 data buffer depth Liviu Dudau
2014-11-12 9:39 ` Vinod Koul [this message]
2014-11-14 12:33 ` Liviu Dudau
2014-12-05 17:40 ` 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=20141112093952.GD24582@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).