[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140616153832.GC31771@8bytes.org>
Date: Mon, 16 Jun 2014 17:38:32 +0200
From: Joerg Roedel <joro@...tes.org>
To: Will Deacon <will.deacon@....com>
Cc: Christoffer Dall <christoffer.dall@...aro.org>,
Antonios Motakis <a.motakis@...tualopensystems.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"tech@...tualopensystems.com" <tech@...tualopensystems.com>,
"a.rigo@...tualopensystems.com" <a.rigo@...tualopensystems.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"kim.phillips@...escale.com" <kim.phillips@...escale.com>,
"stuart.yoder@...escale.com" <stuart.yoder@...escale.com>,
"eric.auger@...aro.org" <eric.auger@...aro.org>,
"moderated list:ARM SMMU DRIVER"
<linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v6 04/20] iommu/arm-smmu: add capability
IOMMU_CAP_INTR_REMAP
On Mon, Jun 16, 2014 at 04:25:26PM +0100, Will Deacon wrote:
> Ok, thanks. In which case, I think this is really a combined property of
> the SMMU and the interrupt controller, so we might need some extra code
> so that the SMMU can check that the interrupt controller for the device
> is also capable of interrupt remapping.
Right, that this is part of IOMMU code has more or less historic reasons
on x86. Interrupt remapping is purely implemented in the IOMMU there, so
on ARM some clue-code between interrupt controler and smmu is needed.
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists