From: Robin Murphy <robin.murphy@arm.com>
To: Scott Branden <scott.branden@broadcom.com>,
Mark Rutland <mark.rutland@arm.com>,
Srinath Mannam <srinath.mannam@broadcom.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Bjorn Helgaas <bhelgaas@google.com>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [RFC PATCH 1/2] dt-bindings: pci: Add drop mask property for MSI and IOMMU
Date: Fri, 7 Jul 2017 16:42:48 +0100 [thread overview]
Message-ID: <d3a32adc-609f-d7d1-5b5e-7dfb236414ea@arm.com> (raw)
In-Reply-To: <a66fac9a-b8f7-489e-a32a-ab2100c89653@broadcom.com>
On 07/07/17 16:22, Scott Branden wrote:
> Hi Robin,
>
> On 17-07-07 07:55 AM, Robin Murphy wrote:
>> On 07/07/17 14:30, Mark Rutland wrote:
[...]
>>> Your mapping can be expressed today using a number of msi-map entries,
>>> which you can easily generate programmatically with a trivial perl
>>> script, without requiring a new binding or any new kernel code.
>>>
>>> Please do that instead.
>> Indeed. The systems I'm aware of which need to express non-trivial RID
>> to SID mappings tend to have the bootloader probe PCI and dynamically
>> generate map entries per discovered RID, but even if you wanted to
>> statically generate the whole lot for the worst-case bus range that's
>> still only 512 entries, which is not unmanageable. Notably, it's also
>> what would have to be done (in equivalent) for IORT, although I assume
>> this is an embedded platform for which nobody cares about ACPI.
> Actually we will care about ACPI and need to add it (doesn't need to be
> in this patchet unless easy to do so...)
Ah, OK, that's an even stronger argument for not adding anything new
then - DT "iommu-map" is already marginally more expressive than IORT ID
mappings can be, so there doesn't seem to be much justification for
diverging them further.
Robin.
next prev parent reply other threads:[~2017-07-07 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 7:09 [RFC PATCH 0/2] Add sideband data extraction Srinath Mannam
2017-07-07 7:09 ` [RFC PATCH 1/2] dt-bindings: pci: Add drop mask property for MSI and IOMMU Srinath Mannam
2017-07-07 13:30 ` Mark Rutland
2017-07-07 14:55 ` Robin Murphy
2017-07-07 15:22 ` Scott Branden
2017-07-07 15:42 ` Robin Murphy [this message]
2017-07-07 15:47 ` Mark Rutland
2017-07-07 7:09 ` [RFC PATCH 2/2] pcie: sideband data by dropping RID bits Srinath Mannam
2017-07-07 13:33 ` Mark Rutland
2017-07-07 13:21 ` [RFC PATCH 0/2] Add sideband data extraction Mark Rutland
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=d3a32adc-609f-d7d1-5b5e-7dfb236414ea@arm.com \
--to=robin.murphy@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=srinath.mannam@broadcom.com \
/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
all inboxes | Powered by JetHome®