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=-5.7 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 8B85CC4338F for ; Sun, 22 Aug 2021 16:50:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6C6A46127B for ; Sun, 22 Aug 2021 16:50:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234164AbhHVQvR (ORCPT ); Sun, 22 Aug 2021 12:51:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229586AbhHVQvQ (ORCPT ); Sun, 22 Aug 2021 12:51:16 -0400 Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 50E1DC061575 for ; Sun, 22 Aug 2021 09:50:35 -0700 (PDT) Received: by mail-ot1-x335.google.com with SMTP id a20-20020a0568300b9400b0051b8ca82dfcso8552611otv.3 for ; Sun, 22 Aug 2021 09:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=KUQ1Wd1A9uHMPtRYx40LKABn7voa02Y4leoq1TyTTpx+BBE1w/r1SsSTOIUgCT4xfr oGJeHu5D3NKbu0d+8lZPwpu82/jyg8bA5oOOPJc+3h3eqD/tm+u+bfsB0MVHDBtL1LXy QLAGHfOtjkqC9xyeHfDXqtqW8CfEM4VOleO7k= 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=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=aPLvboB7w6QYKj/tFIuCRFwB7A4AbR2Ugaoknd04wWq3Aa65gZswkgEtyscevAKsle DD0ZA555BJl8Wh9WVdkmBrDZYdeAADg1r/elVEXpgktxcZAS8k83KzXjoTaudzONp25A 2evtCFWaWbK/WQlG+lV1plaoGZGDGrjiO+ZK5VWL3e1eOanWrLmfNhl+0DlYINa/6HVD YqhCNntaVxTWBKDdt+F6msx8IbYTZsaq1Ucr+zF0F7JK4hgoNwmagODAT0cZEvUnue1d qhLXVAsv04jQEd8j8y0Ax1W+5SYx332k7R1yhKBOA9hbiXTP0ubJKoCdGzOlhAcz9xKb /Clw== X-Gm-Message-State: AOAM531xwYvqM87tyAX+b0lmCMgm+c1maDTPk6XoTywb7N5hz3q91RrV vMp9wt1bIfPc1gEP0SZLG4srFulX7Yw3OK0AsWyE2g== X-Google-Smtp-Source: ABdhPJzsqYUkGnoKx6cZL/MZd0xVLARgQAiHA36o4mNFCThs4ItbOa2X5Lm6FYKo4igPkf8VSlPht+LiVtxMvPa5diM= X-Received: by 2002:a05:6808:1449:: with SMTP id x9mr9094210oiv.14.1629651034674; Sun, 22 Aug 2021 09:50:34 -0700 (PDT) MIME-Version: 1.0 References: <20210811025801.21597-1-yunfei.dong@mediatek.com> In-Reply-To: From: Daniel Vetter Date: Sun, 22 Aug 2021 18:50:23 +0200 Message-ID: Subject: Re: [PATCH v5, 00/15] Using component framework to support multi hardware decode To: Ezequiel Garcia Cc: Yunfei Dong , dri-devel , Alexandre Courbot , Hans Verkuil , Tzung-Bi Shih , Tiffany Lin , Andrew-CT Chen , Mauro Carvalho Chehab , Rob Herring , Matthias Brugger , Tomasz Figa , Hsin-Yi Wang , Fritz Koenig , Irui Wang , linux-media , devicetree , Linux Kernel Mailing List , linux-arm-kernel , srv_heupstream , "moderated list:ARM/Mediatek SoC support" , Project_Global_Chrome_Upstream_Group@mediatek.com, George Sun Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 18, 2021 at 4:12 PM Ezequiel Garcia wrote: > > +danvet > > Hi, > > On Tue, 10 Aug 2021 at 23:58, Yunfei Dong wrote: > > > > This series adds support for multi hardware decode into mtk-vcodec, by first > > adding component framework to manage each hardware information: interrupt, > > clock, register bases and power. Secondly add core thread to deal with core > > hardware message, at the same time, add msg queue for different hardware > > share messages. Lastly, the architecture of different specs are not the same, > > using specs type to separate them. > > > > I don't think it's a good idea to introduce the component API in the > media subsystem. It doesn't seem to be maintained, IRC there's not even > a maintainer for it, and it has some issues that were never addressed. Defacto dri-devel folks are maintainer component.c, but also I'm not aware of anything missing there? There has been discussions that in various drm subsystems like drm_bridge or drm_panel a few things are missing, which prevent drivers from moving _away_ from component.c to the more specific solutions for panel/bridges. But nothing that's preventing them from using component.c itself. I'm happy to merge a MAINTAINERS patch to clarify the situation if that's needed. -Daniel > It would be really important to avoid it. Is it really needed in the > first place? > > Thanks, > Ezequiel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch 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.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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 79C45C4338F for ; Sun, 22 Aug 2021 16:50:57 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CAC0761184 for ; Sun, 22 Aug 2021 16:50:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org CAC0761184 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=6YAsr/d9vLAkuJJstSQp+cBXcXAl0jYHvBe7lIBzzfI=; b=3oYeF8btL3fWN8 yToFvPP6YkXkwh5hprngKe2IEu3AkF1FTSAiFd146eTaENoGLazqvmbhkafGWhy0QXopOy6UR9z3+ yrH7nm4pIRU5DCBuWA7D6CY2vdIvcBNCuR0vUS88cnvNcfIkIIDhRRn5QU1LauNRnEpw7IewXLaSi 463mjG+CtT2dATDZc0FDOd8pvI354EVHPHLmwu/HTXdDz3mRascQg7xLesTyA+ts+x0BeL9x3W+ZX 8Pfa2t6hP650MMho0w9MgbSCWUw5TS55DTm4YzQ9dpiMGI5ALtGqzlQX+kAOI+SSjmzyh9jdhdx1c Ef9KNkSsT5BG+KPESKXw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mHqgE-00EMgQ-4t; Sun, 22 Aug 2021 16:50:42 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mHqg8-00EMeO-Iz for linux-mediatek@lists.infradead.org; Sun, 22 Aug 2021 16:50:40 +0000 Received: by mail-ot1-x332.google.com with SMTP id i8-20020a056830402800b0051afc3e373aso18217014ots.5 for ; Sun, 22 Aug 2021 09:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=KUQ1Wd1A9uHMPtRYx40LKABn7voa02Y4leoq1TyTTpx+BBE1w/r1SsSTOIUgCT4xfr oGJeHu5D3NKbu0d+8lZPwpu82/jyg8bA5oOOPJc+3h3eqD/tm+u+bfsB0MVHDBtL1LXy QLAGHfOtjkqC9xyeHfDXqtqW8CfEM4VOleO7k= 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=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=IyoH17XOwWf4137MkcgzHMPCjZxqPEl+CHotw1Vzi//CGY/bWV3LPdDHj7AS4f9gVQ OzurwhA1f1WJ/in4E8qT6SzCZDif9tTSz66SkCjymYcbPh9X2j7Aggw2PvzyF1i9jAvn JxMSkDs23ApvQlaoDTYV1kNDk0o9Ken+iEKgJ2S2N3bE7TKRu2OtQOsuKG7ZkoUcA54z mi/fSMdWI5ezj9zOvnjicK5JWmY7ksvQ0mQ5aSb6vrpes3SeBX+te9eWNFJ+yAd0X04K 5dqTJzmcLRczdke8xFad3nZZ0/RaI4SEf5bdsQozftIQ7o2cv+WT8z0oHpvnnxjuQiCG BpRw== X-Gm-Message-State: AOAM530+2bYtYzAJyOGzMo+mx/PcOIJcRej2C84eaXQ38UAz40wOiN/n jo6jIvL7Q582OUZlsCZ26bNk7IcGAZQoqwuWqJ5Dyg== X-Google-Smtp-Source: ABdhPJzsqYUkGnoKx6cZL/MZd0xVLARgQAiHA36o4mNFCThs4ItbOa2X5Lm6FYKo4igPkf8VSlPht+LiVtxMvPa5diM= X-Received: by 2002:a05:6808:1449:: with SMTP id x9mr9094210oiv.14.1629651034674; Sun, 22 Aug 2021 09:50:34 -0700 (PDT) MIME-Version: 1.0 References: <20210811025801.21597-1-yunfei.dong@mediatek.com> In-Reply-To: From: Daniel Vetter Date: Sun, 22 Aug 2021 18:50:23 +0200 Message-ID: Subject: Re: [PATCH v5, 00/15] Using component framework to support multi hardware decode To: Ezequiel Garcia Cc: Yunfei Dong , dri-devel , Alexandre Courbot , Hans Verkuil , Tzung-Bi Shih , Tiffany Lin , Andrew-CT Chen , Mauro Carvalho Chehab , Rob Herring , Matthias Brugger , Tomasz Figa , Hsin-Yi Wang , Fritz Koenig , Irui Wang , linux-media , devicetree , Linux Kernel Mailing List , linux-arm-kernel , srv_heupstream , "moderated list:ARM/Mediatek SoC support" , Project_Global_Chrome_Upstream_Group@mediatek.com, George Sun X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210822_095036_670170_591FC345 X-CRM114-Status: GOOD ( 24.30 ) X-BeenThere: linux-mediatek@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org On Wed, Aug 18, 2021 at 4:12 PM Ezequiel Garcia wrote: > > +danvet > > Hi, > > On Tue, 10 Aug 2021 at 23:58, Yunfei Dong wrote: > > > > This series adds support for multi hardware decode into mtk-vcodec, by first > > adding component framework to manage each hardware information: interrupt, > > clock, register bases and power. Secondly add core thread to deal with core > > hardware message, at the same time, add msg queue for different hardware > > share messages. Lastly, the architecture of different specs are not the same, > > using specs type to separate them. > > > > I don't think it's a good idea to introduce the component API in the > media subsystem. It doesn't seem to be maintained, IRC there's not even > a maintainer for it, and it has some issues that were never addressed. Defacto dri-devel folks are maintainer component.c, but also I'm not aware of anything missing there? There has been discussions that in various drm subsystems like drm_bridge or drm_panel a few things are missing, which prevent drivers from moving _away_ from component.c to the more specific solutions for panel/bridges. But nothing that's preventing them from using component.c itself. I'm happy to merge a MAINTAINERS patch to clarify the situation if that's needed. -Daniel > It would be really important to avoid it. Is it really needed in the > first place? > > Thanks, > Ezequiel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek 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=-5.7 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 71C70C4320E for ; Sun, 22 Aug 2021 16:50:39 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id A4956611C2 for ; Sun, 22 Aug 2021 16:50:38 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A4956611C2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 0791789D87; Sun, 22 Aug 2021 16:50:37 +0000 (UTC) Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) by gabe.freedesktop.org (Postfix) with ESMTPS id 9A03589D87 for ; Sun, 22 Aug 2021 16:50:35 +0000 (UTC) Received: by mail-ot1-x333.google.com with SMTP id m7-20020a9d4c87000000b0051875f56b95so29444146otf.6 for ; Sun, 22 Aug 2021 09:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=KUQ1Wd1A9uHMPtRYx40LKABn7voa02Y4leoq1TyTTpx+BBE1w/r1SsSTOIUgCT4xfr oGJeHu5D3NKbu0d+8lZPwpu82/jyg8bA5oOOPJc+3h3eqD/tm+u+bfsB0MVHDBtL1LXy QLAGHfOtjkqC9xyeHfDXqtqW8CfEM4VOleO7k= 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=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=FILvoR6w3EmZnsFCrfrcB2YX/WhwHtEWFXOH1aX+yAGVjQ6ACaoWrBewPCv4HJZtxz 6vi5ZjYpsVZOuUxDl3FmmPm+ImfpqXGV/YaYL2ycGCIlBOAGh2BC6pP1d/WO9ifjEja2 9pfY1espKFTbGPCxuhLVDmWLOxmiL6TzxGE+hYwPuswmqf+2WunbgqjOdq0pNJxcbXAB 22jPfZdxiSWo51HzcUBMGV8/VYRwwCpLQagoCBVybYFA5ZgTMef/PM0uSt7NXd8QwNpC mMfqGydX2clyVGcO2M7n1H9d2Ro670qaOWaPzxlhUjHEqaZpRGeKtE9Xxp9021Y64MQ1 Km3Q== X-Gm-Message-State: AOAM533+pxrou3+PDQJr1Km8vQeAUS/vHJG+OHZY/8SI9TRRYmj7w0mG KSyr9O3htOTtz4S2LB7P/m4PA5HWutlKkmVM3wMmxQ== X-Google-Smtp-Source: ABdhPJzsqYUkGnoKx6cZL/MZd0xVLARgQAiHA36o4mNFCThs4ItbOa2X5Lm6FYKo4igPkf8VSlPht+LiVtxMvPa5diM= X-Received: by 2002:a05:6808:1449:: with SMTP id x9mr9094210oiv.14.1629651034674; Sun, 22 Aug 2021 09:50:34 -0700 (PDT) MIME-Version: 1.0 References: <20210811025801.21597-1-yunfei.dong@mediatek.com> In-Reply-To: From: Daniel Vetter Date: Sun, 22 Aug 2021 18:50:23 +0200 Message-ID: Subject: Re: [PATCH v5, 00/15] Using component framework to support multi hardware decode To: Ezequiel Garcia Cc: Yunfei Dong , dri-devel , Alexandre Courbot , Hans Verkuil , Tzung-Bi Shih , Tiffany Lin , Andrew-CT Chen , Mauro Carvalho Chehab , Rob Herring , Matthias Brugger , Tomasz Figa , Hsin-Yi Wang , Fritz Koenig , Irui Wang , linux-media , devicetree , Linux Kernel Mailing List , linux-arm-kernel , srv_heupstream , "moderated list:ARM/Mediatek SoC support" , Project_Global_Chrome_Upstream_Group@mediatek.com, George Sun Content-Type: text/plain; charset="UTF-8" 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: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Wed, Aug 18, 2021 at 4:12 PM Ezequiel Garcia wrote: > > +danvet > > Hi, > > On Tue, 10 Aug 2021 at 23:58, Yunfei Dong wrote: > > > > This series adds support for multi hardware decode into mtk-vcodec, by first > > adding component framework to manage each hardware information: interrupt, > > clock, register bases and power. Secondly add core thread to deal with core > > hardware message, at the same time, add msg queue for different hardware > > share messages. Lastly, the architecture of different specs are not the same, > > using specs type to separate them. > > > > I don't think it's a good idea to introduce the component API in the > media subsystem. It doesn't seem to be maintained, IRC there's not even > a maintainer for it, and it has some issues that were never addressed. Defacto dri-devel folks are maintainer component.c, but also I'm not aware of anything missing there? There has been discussions that in various drm subsystems like drm_bridge or drm_panel a few things are missing, which prevent drivers from moving _away_ from component.c to the more specific solutions for panel/bridges. But nothing that's preventing them from using component.c itself. I'm happy to merge a MAINTAINERS patch to clarify the situation if that's needed. -Daniel > It would be really important to avoid it. Is it really needed in the > first place? > > Thanks, > Ezequiel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch 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.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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 47269C4338F for ; Sun, 22 Aug 2021 16:53:20 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 109D461212 for ; Sun, 22 Aug 2021 16:53:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 109D461212 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mX7zQaTDjYTwH+M1Yhogdom8dBoXfW/cJpSevVi1TT0=; b=ykmOuHV4+Dcs7r iZjKyZ2uiCW53X97zgLDjQOuPSG9+V6Q+4vFdPT2KV6Dqq7I00Nbxz0owBAN5LGWFZhvTWsVnUn7N N+aA/70zmttF11XZfQnnwZgT/F6F0tdAgmggObLDG/vCyYsT7drRJorQAwLpgb6rJjVtDvmDnET4w ymO+Bwf3ijb0FjPOq/zszC/nGuLpg4b7jXNQ+8fr2LN1zMFUIuwuGftfnUsD3oxMUkWdGk1zE/P1U 3HTo6fKgdzh+pUMfg+cwZutkApm/g2ZYr+nhfMBgmXWvmBeqW/xCWQIAfL2HSFaOHsgTCFmRelwJl dWQFxmb3+mCPE6QfQaYg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mHqgG-00EMgv-4l; Sun, 22 Aug 2021 16:50:44 +0000 Received: from mail-ot1-x334.google.com ([2607:f8b0:4864:20::334]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mHqg8-00EMeN-Jh for linux-arm-kernel@lists.infradead.org; Sun, 22 Aug 2021 16:50:41 +0000 Received: by mail-ot1-x334.google.com with SMTP id o16-20020a9d2210000000b0051b1e56c98fso14643940ota.8 for ; Sun, 22 Aug 2021 09:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=KUQ1Wd1A9uHMPtRYx40LKABn7voa02Y4leoq1TyTTpx+BBE1w/r1SsSTOIUgCT4xfr oGJeHu5D3NKbu0d+8lZPwpu82/jyg8bA5oOOPJc+3h3eqD/tm+u+bfsB0MVHDBtL1LXy QLAGHfOtjkqC9xyeHfDXqtqW8CfEM4VOleO7k= 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=dtfidEe/qjxfHjRkhW97hyLbAhf+ZJVGWplTJWO3Pbs=; b=ZYFIMU3RGovHdY5FVLzb9XRxEUqCAZGozE+I6lhQJF+cIXYnp+k+xZFvrw6UeowiV1 rh87ELGkfY1E75CjQS+Y6d77sLhEWeYtJyU1+7ERxZ4CBZzYokeYu7i0uxWd8mi3U1bW Lw1iFsMPjhYVcZO1qk1OusN2boRmAjfxqRFZGUByaM4Csd1i04pDwSxA2yzBcjOjVGBc n1eoS8dIv973GoPtikAYu9cdUN9tmwls3EVZVGz4ZfZCzsdOmVJXE+CD4w/ahRkr5s3A Dv1b8aByx+Pb+dwJ2zLBx1M7Kzp+uT/W0P4D2L4Bon9Ja7avRHoAb/kNAesu12ApS/jO kgJQ== X-Gm-Message-State: AOAM531lQeUzoDsEVeEIS4tJKvCrZ5NiDlB+WvgikJMMBs6JZP5Cffh/ OnG7Fy0WANBaESVjUb7EgBb++TPQHxqlkRRTKiBLAA== X-Google-Smtp-Source: ABdhPJzsqYUkGnoKx6cZL/MZd0xVLARgQAiHA36o4mNFCThs4ItbOa2X5Lm6FYKo4igPkf8VSlPht+LiVtxMvPa5diM= X-Received: by 2002:a05:6808:1449:: with SMTP id x9mr9094210oiv.14.1629651034674; Sun, 22 Aug 2021 09:50:34 -0700 (PDT) MIME-Version: 1.0 References: <20210811025801.21597-1-yunfei.dong@mediatek.com> In-Reply-To: From: Daniel Vetter Date: Sun, 22 Aug 2021 18:50:23 +0200 Message-ID: Subject: Re: [PATCH v5, 00/15] Using component framework to support multi hardware decode To: Ezequiel Garcia Cc: Yunfei Dong , dri-devel , Alexandre Courbot , Hans Verkuil , Tzung-Bi Shih , Tiffany Lin , Andrew-CT Chen , Mauro Carvalho Chehab , Rob Herring , Matthias Brugger , Tomasz Figa , Hsin-Yi Wang , Fritz Koenig , Irui Wang , linux-media , devicetree , Linux Kernel Mailing List , linux-arm-kernel , srv_heupstream , "moderated list:ARM/Mediatek SoC support" , Project_Global_Chrome_Upstream_Group@mediatek.com, George Sun X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210822_095036_676452_04E64244 X-CRM114-Status: GOOD ( 25.71 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Aug 18, 2021 at 4:12 PM Ezequiel Garcia wrote: > > +danvet > > Hi, > > On Tue, 10 Aug 2021 at 23:58, Yunfei Dong wrote: > > > > This series adds support for multi hardware decode into mtk-vcodec, by first > > adding component framework to manage each hardware information: interrupt, > > clock, register bases and power. Secondly add core thread to deal with core > > hardware message, at the same time, add msg queue for different hardware > > share messages. Lastly, the architecture of different specs are not the same, > > using specs type to separate them. > > > > I don't think it's a good idea to introduce the component API in the > media subsystem. It doesn't seem to be maintained, IRC there's not even > a maintainer for it, and it has some issues that were never addressed. Defacto dri-devel folks are maintainer component.c, but also I'm not aware of anything missing there? There has been discussions that in various drm subsystems like drm_bridge or drm_panel a few things are missing, which prevent drivers from moving _away_ from component.c to the more specific solutions for panel/bridges. But nothing that's preventing them from using component.c itself. I'm happy to merge a MAINTAINERS patch to clarify the situation if that's needed. -Daniel > It would be really important to avoid it. Is it really needed in the > first place? > > Thanks, > Ezequiel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel