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=-9.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 D234FC2BB55 for ; Thu, 16 Apr 2020 16:23:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B364F2223E for ; Thu, 16 Apr 2020 16:23:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587054191; bh=dYe0L8knPjq4V+e3C0CynMr68uvk2h/61C1ujyYiF70=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=nD0h1DOnzQn7b2ikc8BxsdGg3j4TCJ28CEb+mzcJYoNmVG0Yv8zUtZN84YmPBX9ih tIGBMc4ASggOURSmHWsVzmgmSNwae04UNvi84bNoAJtIG9XZgUCOUQDPJYKVUhNrt3 NoE3nM9xnri8xROdTAYy3VlDyX23kyqb8WfQnOEE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391207AbgDPQXJ (ORCPT ); Thu, 16 Apr 2020 12:23:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:50818 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729633AbgDPQXG (ORCPT ); Thu, 16 Apr 2020 12:23:06 -0400 Received: from mail-ej1-f41.google.com (mail-ej1-f41.google.com [209.85.218.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9A03322250; Thu, 16 Apr 2020 16:23:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587054185; bh=dYe0L8knPjq4V+e3C0CynMr68uvk2h/61C1ujyYiF70=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=m92+j7PyJJqSdIZDHDYxGpMk1MSTdEN3OfxmyZ5uDz3gYONFBBkjqZfnO2V19s6L3 uWSFke5h6gqhJSuJUX/v4SaHaHZp1FcOjeDRIRraalXi9n50/SXBviV2xU4LGfnrd5 Ek5R1e51qljTWjy8yVonj+VDn0jnnD+E/Zrj+BWE= Received: by mail-ej1-f41.google.com with SMTP id s9so1713435eju.1; Thu, 16 Apr 2020 09:23:05 -0700 (PDT) X-Gm-Message-State: AGi0Pub+htmOBUicEH+5GKsykiMe17NI6O3zbKw5fJhuoYhKKWaSnVMl iiyvH0OSeZ6gsKPZPhfJWdV5hJ+GlP/+Qprujw== X-Google-Smtp-Source: APiQypJY17+s5/o0+wlz0famZC0WrI5UI7Klts8JPoOZRnB9zgY8QO2uzy/FBMWzeg9CvxriYGO6Q1j1IF4pKi5aPZw= X-Received: by 2002:a17:906:2ad4:: with SMTP id m20mr10975923eje.324.1587054183934; Thu, 16 Apr 2020 09:23:03 -0700 (PDT) MIME-Version: 1.0 References: <20200311165322.1594233-1-enric.balletbo@collabora.com> <20200311165322.1594233-5-enric.balletbo@collabora.com> <02290a21-7392-a2cf-576c-215091ec05e8@suse.com> <1585177534.26117.4.camel@mtksdaap41> <1585234277.12089.3.camel@mtksdaap41> <73ef0b8e-2802-a047-2a56-936b63d264cb@suse.com> In-Reply-To: <73ef0b8e-2802-a047-2a56-936b63d264cb@suse.com> From: Chun-Kuang Hu Date: Fri, 17 Apr 2020 00:22:52 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v12 4/5] soc / drm: mediatek: Move routing control to mmsys device To: Matthias Brugger Cc: CK Hu , Mark Rutland , Kate Stewart , Minghsiu Tsai , Andrew-CT Chen , David Airlie , Michael Turquette , DRI Development , Richard Fontana , Laurent Pinchart , ulrich.hecht+renesas@gmail.com, Collabora Kernel ML , linux-clk@vger.kernel.org, Weiyi Lu , wens@csie.org, Allison Randal , mtk01761 , linux-media@vger.kernel.org, devicetree@vger.kernel.org, Philipp Zabel , Frank Wunderlich , Seiya Wang , sean.wang@mediatek.com, Houlong Wei , Rob Herring , "moderated list:ARM/Mediatek SoC support" , Hsin-Yi Wang , Matthias Brugger , Thomas Gleixner , Mauro Carvalho Chehab , Linux ARM , Stephen Boyd , Greg Kroah-Hartman , rdunlap@infradead.org, linux-kernel , Daniel Vetter , matthias.bgg@kernel.org, Enric Balletbo i Serra Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Hi, Matthias: Matthias Brugger =E6=96=BC 2020=E5=B9=B43=E6=9C=8826=E6= =97=A5 =E9=80=B1=E5=9B=9B =E4=B8=8B=E5=8D=8811:45=E5=AF=AB=E9=81=93=EF=BC= =9A > > > > On 26/03/2020 15:51, CK Hu wrote: > > Hi, Matthias: > > > > On Thu, 2020-03-26 at 12:54 +0100, Matthias Brugger wrote: > >> Hi CK, > >> > >> On 26/03/2020 00:05, CK Hu wrote: > >>> Hi, Matthias: > >>> > >>> On Wed, 2020-03-25 at 17:16 +0100, Matthias Brugger wrote: > >>>> > >>>> On 11/03/2020 17:53, Enric Balletbo i Serra wrote: > >>>>> Provide a mtk_mmsys_ddp_connect() and mtk_mmsys_disconnect() functi= ons to > >>>>> replace mtk_ddp_add_comp_to_path() and mtk_ddp_remove_comp_from_pat= h(). > >>>>> Those functions will allow DRM driver and others to control the dat= a > >>>>> path routing. > >>>>> > >>>>> Signed-off-by: Enric Balletbo i Serra > >>>>> Reviewed-by: Matthias Brugger > >>>>> Reviewed-by: CK Hu > >>>>> Acked-by: CK Hu > >>>> > >>>> This patch does not apply against v5.6-rc1. > >>>> Please rebase as this is a quite big patch and it won't be easy to d= o that by hand. > >>> > >>> I think this patch depends on [1] which has been acked by me and I ha= ve > >>> not picked it. The simple way is that you pick [1] first and then pic= k > >>> this series. > >>> > >>> [1] > >>> https://patchwork.kernel.org/patch/11406227/ > >>> > >> > >> You would need to provide a stable tag for me that I can merge into my= tree. You > >> can also try to merge my for-next [1] which has the newest version fro= m Enric. > >> If you see any merge conflict, then we have to do something about it := ) > >> > >> Regards, > >> Matthias > >> > >> [1] > >> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git= /log/?h=3Dfor-next > >> > > > > You have applied this series, so I would not apply other patches which > > would conflict with this series. After this series land on main stream > > (wish it happen in this merge window), I would rebase other patch on > > main stream. > > > > I haven't (yet) send the pull request. If you want to bring in your patch= es in > v5.7 as well we can find a solution to that. Shall I provide you with a s= table > branch which you can merge? This way you can add all your patches in the = pull > request as well and we don't have to wait for v5.8 to get things into mai= nline. > > Let me know and I'll provide you with a stable branch. This series is in linux-next but does not in main stream. So would you please provide a stable branch so I could pull this series? Regards, Chun-Kuang. > > Regards, > Matthias > > > Regards, > > CK > > > >>> Regards, > >>> CK > >>> > >>>> > >>>> Regards, > >>>> Matthias > >>>> > >>>>> --- > >>>>>