From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758781AbbBGWmH (ORCPT ); Sat, 7 Feb 2015 17:42:07 -0500 Received: from mout.kundenserver.de ([212.227.17.10]:52392 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755747AbbBGWmE (ORCPT ); Sat, 7 Feb 2015 17:42:04 -0500 Date: Sat, 7 Feb 2015 23:41:24 +0100 (CET) From: "arnd@arndb.de" Reply-To: "arnd@arndb.de" To: Will Deacon , Robin Murphy , Laura Abbott Cc: Laurent Pinchart , linux-kernel@vger.kernel.org, Mitchel Humpherys , Marek Szyprowski , linux-arm-kernel@lists.infradead.org, iommu@lists.linux-foundation.org, devicetree@vger.kernel.org, Joreg Roedel , Grant Likely Message-ID: <2115835102.210232.1423348884955.JavaMail.open-xchange@oxbaltgw04.schlund.de> In-Reply-To: <1423182722-16646-1-git-send-email-lauraa@codeaurora.org> References: <1423182722-16646-1-git-send-email-lauraa@codeaurora.org> Subject: Re: [PATCH/RFC 0/4] Probe deferral for IOMMU DT integration MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.6.0-Rev36 X-Originating-Client: com.openexchange.ox.gui.dhtml X-Provags-ID: V03:K0:uQX+EIKQ87PKWA4jevpuq69HzroF9VamGrbcEKk0IQi/gYCY03m +5Lhefo5khGAAr/UQfVKM3Y2L2yQ/s3U6uZzAchMssq7rC9gRAO+DWjKHHf2B0iHB8nITwO bPVx7MzsaBM1et6IyvyM8UBpJ/bMFLuCOp4SpzXqJXRWKZLCBHe1+z18P7ZdFnZXTIU9GSP 11bf1thgNoRmAYKCYurZQ== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Laura Abbott hat am 6. Februar 2015 um 01:31 geschrieben: > > The requirement for this is based on a previous patch to add clock > support to the ARM SMMU driver[2]. Once we have clock support, it's > possible that the driver itself may need to be defered which breaks > a bunch of assumptions about how SMMU probing is supposed to work. Hi Laura, I was hoping that we would not need this, and instead treat the iommu in the same way as timers and SMP initialization, both of which need to be run early at boot time but may rely on clock controllers to be initialized first. Is there a specific requirement that makes this impossible here, or is your intention to solve the problem more nicely by allowing deferred probing over forcing the input clocks of the iommu to be early? Arnd