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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0FFB8CA0EEB for ; Tue, 12 Sep 2023 14:46:37 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 25DF810E332; Tue, 12 Sep 2023 14:46:36 +0000 (UTC) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by gabe.freedesktop.org (Postfix) with ESMTPS id 9021E10E332 for ; Tue, 12 Sep 2023 14:46:34 +0000 (UTC) Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-402cc6b8bedso65043305e9.1 for ; Tue, 12 Sep 2023 07:46:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694529993; x=1695134793; darn=lists.freedesktop.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=K8sFu0+D3E77YJ4z9rbydrUcmzYi8cL1xr3GzlsZe4w=; b=LdcVQWL5kac7/MZ9n5GIChkkZ+rc+dCyPZ1SbnmcRVHtOXUUkpSLAhLcWcgdohBP0h z/tIhiwkWA7jRH0maAXjR1WgHM1bBPL8YC6E/cOuQmkyR5IAEA7J+V51bsnduY8ds3vL ttFVW+NdZaFJiYIQ86NEvQc2Td5euTGCoKqyqROonXayr/7gcFcHti2IlipFVfu+IXAF f0xqNbcZxcdQfCIRwF2Fxg7Ny6yVfpbgp3hXQkOASwuMIYlJ83EVZS4m81JFYkhBB6Jq CSmvwVGM5Y1dd0ggrslG8eP+3npkqwtWbSK663RDnkw8I3zwBnLVxLj3LDe38q6XEk6D BtMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694529993; x=1695134793; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=K8sFu0+D3E77YJ4z9rbydrUcmzYi8cL1xr3GzlsZe4w=; b=AR8XiR4+TrGxEV68JdLKMkDrmaANau7XXYvPSnFATxEYfE+dI5gnIlvClzTRrxPxGX /nRBUq9RSONoCWwj97A7kf6T9vp2t9rSTLRpFlkZOCbIgt5xUB3s466taG1xADR9GGhX Vq8UxkTpI43qRoaNfLsb6Qyvnnar43dt2kP73bWybG8Iw4CWBIpi0s54sPRtgINpYBic nQqD0+qvR66PpeT+RHSjwPfL1lQaf65MQlgJLSCNH45zzdvsKlSGE5AkMJ0FJm88AXz5 N2myz2MV6WaHJwo0U9rdoHfmsdI4JgwvCGXsf3vhL4Tw0tzqMD6+VkTxJMNb3saoijJB tiRg== X-Gm-Message-State: AOJu0Yymdj52bjBW1wxhhqVtdz+LNX2zUDKnjR++yr/4TOpVL32Yt/yl 5n9pX6zYcBRMBrdje11qecs= X-Google-Smtp-Source: AGHT+IGHXQb8saBAd6H+9uYnotfhWfZV5PqBMgupUePv5+BNFjR2MQXXacKt9iDypQAL5TYLBL9epA== X-Received: by 2002:a05:600c:3b1e:b0:402:f536:41c5 with SMTP id m30-20020a05600c3b1e00b00402f53641c5mr10911758wms.3.1694529992631; Tue, 12 Sep 2023 07:46:32 -0700 (PDT) Received: from [10.254.108.106] (munvpn.amd.com. [165.204.72.6]) by smtp.gmail.com with ESMTPSA id t15-20020a7bc3cf000000b00402be2666bcsm16448614wmj.6.2023.09.12.07.46.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Sep 2023 07:46:32 -0700 (PDT) Message-ID: <95797f3d-65bf-1bd9-9e19-6de42605cfe3@gmail.com> Date: Tue, 12 Sep 2023 16:46:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: [PATCH 3/9] dma-heap: Provide accessors so that in-kernel drivers can allocate dmabufs from specific heaps Content-Language: en-US To: =?UTF-8?B?WW9uZyBXdSAo5ZC05YuHKQ==?= , "jstultz@google.com" References: <20230911023038.30649-1-yong.wu@mediatek.com> <20230911023038.30649-4-yong.wu@mediatek.com> <803846bc-fd1d-d2ec-2855-456af22c82f8@amd.com> <23e71d1f-08c1-3834-5b1f-2b5714c7bfaa@gmail.com> <255ae6b9ac1b6bea9262069747824b8461475e70.camel@mediatek.com> From: =?UTF-8?Q?Christian_K=c3=b6nig?= In-Reply-To: <255ae6b9ac1b6bea9262069747824b8461475e70.camel@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "devicetree@vger.kernel.org" , "conor+dt@kernel.org" , "benjamin.gaignard@collabora.com" , =?UTF-8?B?S3VvaG9uZyBXYW5nICjnjovlnIvptLsp?= , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "linaro-mm-sig@lists.linaro.org" , "robh+dt@kernel.org" , "linux-mediatek@lists.infradead.org" , "linux-arm-kernel@lists.infradead.org" , "krzysztof.kozlowski+dt@linaro.org" , "matthias.bgg@gmail.com" , "tjmercier@google.com" , "angelogioacchino.delregno@collabora.com" , "sumit.semwal@linaro.org" , =?UTF-8?B?SmlhbmppYW8gWmVuZyAo5pu+5YGl5aejKQ==?= , "linux-media@vger.kernel.org" Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Am 12.09.23 um 10:52 schrieb Yong Wu (吴勇): > [SNIP] >> But what we should try to avoid is that newly merged drivers provide >> both a driver specific UAPI and DMA-heaps. The justification that >> this >> makes it easier to transit userspace to the new UAPI doesn't really >> count. >> >> That would be adding UAPI already with a plan to deprecate it and >> that >> is most likely not helpful considering that UAPI must be supported >> forever as soon as it is upstream. > Sorry, I didn't understand this. I think we have not change the UAPI. > Which code are you referring to? Well, what do you need this for if not a new UAPI? My assumption here is that you need to export the DMA-heap allocation function so that you can server an UAPI in your new driver. Or what else is that good for? As far as I understand you try to upstream your new vcodec driver. So while this change here seems to be a good idea to clean up existing drivers it doesn't look like a good idea for a newly created driver. Regards, Christian. >>> So I think this patch is a little confusing in this series, as I >> don't >>> see much of it actually being used here (though forgive me if I'm >>> missing it). >>> >>> Instead, It seems it get used in a separate patch series here: >>> >> https://lore.kernel.org/all/20230911125936.10648-1-yunfei.dong@mediatek.com/ >> >> Please try to avoid stuff like that it is really confusing and eats >> reviewers time. > My fault, I thought dma-buf and media belonged to the different tree, > so I send them separately. The cover letter just said "The consumers of > the new heap and new interface are our codecs and DRM, which will be > sent upstream soon", and there was no vcodec link at that time. > > In the next version, we will put the first three patches into the > vcodec patchset. > > Thanks. >