From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: More than 16 stream ids
Date: Thu, 31 Jul 2014 18:41:25 +0100 [thread overview]
Message-ID: <20140731174125.GH26853@arm.com> (raw)
In-Reply-To: <53DA7E9E.7000501@amd.com>
[Adding the other Rob ;)]
On Thu, Jul 31, 2014 at 06:36:30PM +0100, Joel Schopp wrote:
> I recently ran into a situation where I needed more than 16 stream ids for
> an smmu, but we are currently limited to 16 by:
>
> #define MAX_MASTER_STREAMIDS MAX_PHANDLE_ARGS
> #define MAX_PHANDLE_ARGS 16
>
> I changed that 16 to 32 and everything worked for me. I am wondering if
> this is the preferred way to fix the limitation? If so I'd be happy to
> send out the 1 line patch.
This seems fine to me. Last time it was brought up, the objection from RobH
was that there wasn't any upstream activity for the AMD board, so this
change could wait:
http://lists.linuxfoundation.org/pipermail/iommu/2014-January/007556.html
Will
prev parent reply other threads:[~2014-07-31 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 17:36 arm64: More than 16 stream ids Joel Schopp
2014-07-31 17:41 ` Will Deacon [this message]
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=20140731174125.GH26853@arm.com \
--to=will.deacon@arm.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).