Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752972AbbF2Tz5 (ORCPT ); Mon, 29 Jun 2015 15:55:57 -0400 Received: from gloria.sntech.de ([95.129.55.99]:60870 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752821AbbF2Tzu convert rfc822-to-8bit (ORCPT ); Mon, 29 Jun 2015 15:55:50 -0400 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Joerg Roedel Cc: djkurtz@chromium.org, Tomasz Figa , iommu@lists.linux-foundation.org, Will Deacon , Kukjin Kim , David Woodhouse , Hiroshi Doyu , Thierry Reding , Alex Williamson , Robin Murphy , Laurent Pinchart , Oded Gabbay , jroedel@suse.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH 03/22] iommu: Propagate error in add_iommu_group Date: Mon, 29 Jun 2015 21:55:28 +0200 Message-ID: <119636597.cTShkBsF28@diego> User-Agent: KMail/4.14.1 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; ) In-Reply-To: <20150629140637.GK18569@8bytes.org> References: <1432831305-11126-1-git-send-email-joro@8bytes.org> <7180470.n5cCZefX9d@diego> <20150629140637.GK18569@8bytes.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1414 Lines: 33 Hi Joerg, Am Montag, 29. Juni 2015, 16:06:37 schrieb Joerg Roedel: > On Mon, Jun 29, 2015 at 11:28:40AM +0200, Heiko St?bner wrote: > > The Rockchip iommu uses bus_set_ops to set its iommu-ops for the platform > > bus and currently returns -ENODEV if it encounters a platform_devices that > > does not have an iommu. As add_iommu_group ignored these returns > > till now this worked, but of course starts to fail now. > > > > All two invocations of the add_device callback ignored (or still ignore) > > the return value so I've come with the following small patch to fix the > > breakage that now exists in the 4.2 tree. > > > > There is probably a better solution possible in the longer term, likely > > similar to what Samsung does, but I'm not sure yet how this would work > > with our drm device that needs an iommu mapping without having an > > iommu (the iommus being attached to the crtc-components). > > Btw, if you want to test the fix too, here is the link: > > http://lists.linuxfoundation.org/pipermail/iommu/2015-June/013508.html yep, works like a charm and fixes the issue. So if helpful: Tested-by: Heiko Stuebner Thanks Heiko -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/