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=-4.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 EEA9CC433E0 for ; Fri, 31 Jul 2020 19:38:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CD68622B3F for ; Fri, 31 Jul 2020 19:38:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="hRQTBt28" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729614AbgGaTiU (ORCPT ); Fri, 31 Jul 2020 15:38:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41688 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729209AbgGaTiU (ORCPT ); Fri, 31 Jul 2020 15:38:20 -0400 Received: from mail-oi1-x242.google.com (mail-oi1-x242.google.com [IPv6:2607:f8b0:4864:20::242]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD814C061574 for ; Fri, 31 Jul 2020 12:38:19 -0700 (PDT) Received: by mail-oi1-x242.google.com with SMTP id l84so15139645oig.10 for ; Fri, 31 Jul 2020 12:38:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cp3GygB7F0b136lUhJrRkyNW4lR2kBcOJ00svd2oGS0=; b=hRQTBt285hvDUY6CCaz910g2/xt+HvaTmkAFVvlGGkdmkHiPE1mWrZ6J9b98CS3oFF 4rerhbQBqnGLLScHR+8hvSGAJGGP7HVCGfBf5URhTql94iKw/HXcIx853Ij74GkbeYQu z72JXvTJ0rU8caEPLxCkBL4MRokdEX1NcN2rLbiWAK6JWMBWavJM9B38gI1PeAnyws1H gt651BF1uJrsSvrDpQlZU+1dw83n7w3F0xuRWk1v5cWG4C7mhK2LPwtt5jkz94BhBR3d L5Rbx5xMULzWXTOBpbK36qGb/u4/6bb7abBJrfUfRNub9BusEMQLIXoFn0BNqa57XgUE OCdw== 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=cp3GygB7F0b136lUhJrRkyNW4lR2kBcOJ00svd2oGS0=; b=hUP915MMCfXsI1KDhgdhqy74EgYMvB/C6z69m7mdE3d27M9xMJOMmovqN8gZmu2Ftb eXMSktrfX6Z31nBTecWlV0bGktRm/95+2QHNef8kHG6y5WzRZoJxuvCpN5f1F0nDeXlC DBqhd8ICtBX68fPiPBXs+p0ktZXnfzpbILn0HAtTb4Kxt4GTZ6krwYTPJ3VvIDhvW9ZP 9Wqs0uryr7UD1l/TClC6CtWY1B0BngWGOLf2qg/RGFn4e+9UaiYxI2IPFSP294u+4L3H wXzWmuzpxU66QpEYcE+TTfbGJ392lec8Uh3FfLPUkCQMrs9JuPvgbHzdne6wibLpKQhe b/Iw== X-Gm-Message-State: AOAM531A4yi7w1TvGr6bbW9a6MMEGhVN5gMdcyBi4AHVIsinmekLaoin r+nqls7V3Umpgm/tfQHrdzAAClsR70F/gYxilkNn4CLv X-Google-Smtp-Source: ABdhPJxRdmWM2JVXS+XJYjkXLwgmye2vV//B6mH9jWnOac/U12I6qldoTC6vypuWGHyySsNeb29bO+jhRX9xVpW97f0= X-Received: by 2002:aca:b5c3:: with SMTP id e186mr4344099oif.10.1596224299067; Fri, 31 Jul 2020 12:38:19 -0700 (PDT) MIME-Version: 1.0 References: <1594948208-4739-1-git-send-email-hayashi.kunihiko@socionext.com> In-Reply-To: From: John Stultz Date: Fri, 31 Jul 2020 12:38:07 -0700 Message-ID: Subject: Re: [PATCH] dma-buf: heaps: Introduce dma_heap_add_cma() for non-default CMA heap To: Kunihiko Hayashi Cc: Sumit Semwal , "Andrew F . Davis" , Benjamin Gaignard , Liam Mark , Laura Abbott , Brian Starkey , Christian Koenig , linux-media@vger.kernel.org, dri-devel , "moderated list:DMA BUFFER SHARING FRAMEWORK" , lkml Content-Type: text/plain; charset="UTF-8" Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org On Fri, Jul 31, 2020 at 2:32 AM Kunihiko Hayashi wrote: > On 2020/07/29 4:17, John Stultz wrote: > > Do you have a upstream driver that you plan to make use this new call? > > Unfortunately I don't have an upstream driver using this call. > > This call is called from dma-buf heaps "importer" or "customer", > and I only made an example (do nothing) importer driver > to test the call. > > > We want to have in-tree users of code added. > > I think this is a generic way to use non-default CMA heaps, however, > we need in-tree "importer" drivers to want to use non-default CMA heaps. > I don't find it from now. > Yea, I and again, I do agree this is functionality that will be needed. But we'll need to wait for a user (camera driver, etc which would utilize the reserved cma region) before we can merge it upstream. :( Do let me know if you have an out of tree driver that would make use of it, and we can see what can be done to help upstream things. thanks -john