From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: Marvell 88NV9143 in mini-PCIe not working with intel_iommu=on Date: Tue, 26 Mar 2013 16:14:37 +0100 Message-ID: <20130326151436.GE2727@8bytes.org> References: <874ngpj3d9.fsf@meteor.durcheinandertal.bofh> <87zjyfy325.fsf@meteor.durcheinandertal.bofh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Andrew Cooks Cc: jyli-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org, "open list:INTEL IOMMU (VT-d)" , open list , Gaudenz Steinlin , Shun Fu , David Woodhouse List-Id: iommu@lists.linux-foundation.org On Fri, Mar 08, 2013 at 10:53:16AM +0800, Andrew Cooks wrote: > I'm hoping one of the veteran developers would give some guidance for > the best approach to enable more devices in future. In cases like this where a device just uses the request-id of another device you can make use of the existing quirk-code in drivers/pci/quirks.c. Look at the function pci_get_dma_source() and add your device there. This should also make it work with VT-d and AMD-Vi. Joerg From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934625Ab3CZPOn (ORCPT ); Tue, 26 Mar 2013 11:14:43 -0400 Received: from 8bytes.org ([85.214.48.195]:45357 "EHLO mail.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934485Ab3CZPOm (ORCPT ); Tue, 26 Mar 2013 11:14:42 -0400 Date: Tue, 26 Mar 2013 16:14:37 +0100 From: Joerg Roedel To: Andrew Cooks Cc: Gaudenz Steinlin , jyli@marvell.com, "open list:INTEL IOMMU (VT-d)" , open list , Shun Fu , Alex Williamson , David Woodhouse Subject: Re: Marvell 88NV9143 in mini-PCIe not working with intel_iommu=on Message-ID: <20130326151436.GE2727@8bytes.org> References: <874ngpj3d9.fsf@meteor.durcheinandertal.bofh> <87zjyfy325.fsf@meteor.durcheinandertal.bofh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Mar 26 16:14:40 2013 X-DSPAM-Confidence: 0.9980 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 5151bb6023671848696469 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 08, 2013 at 10:53:16AM +0800, Andrew Cooks wrote: > I'm hoping one of the veteran developers would give some guidance for > the best approach to enable more devices in future. In cases like this where a device just uses the request-id of another device you can make use of the existing quirk-code in drivers/pci/quirks.c. Look at the function pci_get_dma_source() and add your device there. This should also make it work with VT-d and AMD-Vi. Joerg