From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Master-aware devices and sideband ID data
Date: Fri, 5 Jun 2015 10:05:34 +0100 [thread overview]
Message-ID: <20150605090534.GC1198@arm.com> (raw)
In-Reply-To: <158EFC9F-FCAF-44D3-AD40-804EDFE0CE25@caviumnetworks.com>
On Thu, Jun 04, 2015 at 11:19:30PM +0100, Chalamarla, Tirumalesh wrote:
> > On Jun 1, 2015, at 3:22 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> > It's possible to specify that the paths exist. I expect that software
> > would select which to use at runtime.
> >
> My worry is how to define any priorities/preferences between masters.
> in general the proposal looks reasonable.
I agree that the proposal looks reasonable (in terms of the ability to
describe the sort of topologies that we will face) but I still don't
understand what I need to do in e.g. my IOMMU driver to support this
binding whilst continuing to support the existing iommus binding, which
is relied upon to configure dma-mapping.
Mark: how do you see this co-existing/merging with the current bindings?
I don't think it's practical to throw away what we have and move over to
something totally different all in one go, but there clearly *is* benefit
in your proposal over the existing scheme.
Will
next prev parent reply other threads:[~2015-06-05 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 15:50 Master-aware devices and sideband ID data Mark Rutland
2015-05-07 17:49 ` Stuart Yoder
2015-05-08 15:49 ` Will Deacon
2015-05-08 19:30 ` Stuart Yoder
2015-05-11 9:52 ` Will Deacon
2015-05-26 22:20 ` Chalamarla, Tirumalesh
2015-05-27 17:39 ` Mark Rutland
2015-05-29 17:46 ` Chalamarla, Tirumalesh
2015-06-01 10:22 ` Mark Rutland
2015-06-04 22:19 ` Chalamarla, Tirumalesh
2015-06-05 9:05 ` Will Deacon [this message]
2015-06-09 10:17 ` Mark Rutland
2015-06-10 8:11 ` Will Deacon
2015-07-08 13:30 ` Mark Rutland
2015-07-08 16:02 ` Will Deacon
2015-07-16 13:34 ` Mark Rutland
2015-07-17 10:36 ` Will Deacon
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=20150605090534.GC1198@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).