* arm64: More than 16 stream ids
@ 2014-07-31 17:36 Joel Schopp
2014-07-31 17:41 ` Will Deacon
0 siblings, 1 reply; 2+ messages in thread
From: Joel Schopp @ 2014-07-31 17:36 UTC (permalink / raw)
To: linux-arm-kernel
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.
-Joel
^ permalink raw reply [flat|nested] 2+ messages in thread
* arm64: More than 16 stream ids
2014-07-31 17:36 arm64: More than 16 stream ids Joel Schopp
@ 2014-07-31 17:41 ` Will Deacon
0 siblings, 0 replies; 2+ messages in thread
From: Will Deacon @ 2014-07-31 17:41 UTC (permalink / raw)
To: linux-arm-kernel
[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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-07-31 17:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-31 17:36 arm64: More than 16 stream ids Joel Schopp
2014-07-31 17:41 ` Will Deacon
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).