From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A7246C28CC5 for ; Wed, 5 Jun 2019 12:57:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7D1D020684 for ; Wed, 5 Jun 2019 12:57:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="MQwC6cZR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727995AbfFEM5d (ORCPT ); Wed, 5 Jun 2019 08:57:33 -0400 Received: from mail-ed1-f65.google.com ([209.85.208.65]:39145 "EHLO mail-ed1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727769AbfFEM5c (ORCPT ); Wed, 5 Jun 2019 08:57:32 -0400 Received: by mail-ed1-f65.google.com with SMTP id m10so5661074edv.6; Wed, 05 Jun 2019 05:57:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mNwmQAhzOwQjP+3QJ9Qyx716sV+MvZek24hV7EIWuEc=; b=MQwC6cZRlpJp8S8gEeUy0yt/YY6pRXiNx3qhhdxZz9mLO9tFistVEu7HCQyTCKskfV QpilpgNDrSsy0SJeh+jsSnNea/tjgHTWFNws8h4ueQKU5kh1xYGg9Q1gyK3vv6zxAnHw sU97TDHpfGjxnf2hgH7zC8Dfg2zLXJcMhil+tT/laN5pH5eVwjNqHpydN74VC65OcIlw L9iWQeysiJXDLU7R9xRH0J9WW7JcL5/NzkTplwLoLIL+Gsgnwi27Fh8B4Fb74VRhZPAc I5l9I4aOJVWnaQQ8y39Ju17r1ll91KBxJFYq3FZblaRbSz0Nr10NIb77Pp/mAXG0FHCq 9YUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mNwmQAhzOwQjP+3QJ9Qyx716sV+MvZek24hV7EIWuEc=; b=r/J9CKrdWOqN1ykRMM8Fm/4RbD4ma+Epaf6pu9o44ILGCqYcsBbDKdAMvIgw7z3Xzr pjSwdfVqe8clVZ9iOfpft5aIdRQV5yscPnrGsN0ofDcB9IyaQzjSZVRcaus1zVjgWzcr Gdlw8ZIxE19b+LyZXdjcdxti6O33+jIC2YCi6+nQwBdEJpS9eHbgY8gFRvunDJIthJ5i 7Ln5qgwaAVAwH6mbxYJcdal4jJsg94sIHBVqNhqRZps0Hs3aaZIgcjizDCU9BsuKCLU2 2htTvMcEdwP3MSfMZ4uqSZbBI8b48irggHsi9kNGU64ZXRV3aZn0pOwJI6iteydbIdzF +r5Q== X-Gm-Message-State: APjAAAXQiQvHFzVyKyjgybVOVj/k1iVDfVG1H+YW+ECx4f1BauUXRb5t 1EJwymW/eNxQ3Xc2aE8/0aa7ekMRxA/sZUnK9gg= X-Google-Smtp-Source: APXvYqz1vxq2jyAjvwPKAI30zCoOlIgNefzBtyYxFxTl0wx0mcMOz/q43eVDTS2eLaVvoero3Qx6Gl/7d2TUyTJ/Pns= X-Received: by 2002:a17:906:85d4:: with SMTP id i20mr20270754ejy.256.1559739450124; Wed, 05 Jun 2019 05:57:30 -0700 (PDT) MIME-Version: 1.0 References: <20181201165348.24140-1-robdclark@gmail.com> In-Reply-To: From: Rob Clark Date: Wed, 5 Jun 2019 05:57:16 -0700 Message-ID: Subject: Re: [Freedreno] [PATCH] of/device: add blacklist for iommu dma_ops To: Tomasz Figa Cc: freedreno , Daniel Vetter , Frank Rowand , devicetree@vger.kernel.org, David Airlie , linux-arm-msm , Will Deacon , Doug Anderson , dri-devel , "linux-kernel@vger.kernel.org" , Linux IOMMU , Rob Herring , Sean Paul , Vivek Gautam , Robin Murphy , Christoph Hellwig , Marek Szyprowski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 4, 2019 at 11:58 PM Tomasz Figa wrote: > > But first of all, I remember Marek already submitted some patches long > ago that extended struct driver with some flag that means that the > driver doesn't want the IOMMU to be attached before probe. Why > wouldn't that work? Sounds like a perfect opt-out solution. Actually, yeah.. we should do that. That is the simplest solution. BR, -R