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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 262D1C04A95 for ; Wed, 28 Sep 2022 08:17:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234083AbiI1IQ7 (ORCPT ); Wed, 28 Sep 2022 04:16:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234036AbiI1IQS (ORCPT ); Wed, 28 Sep 2022 04:16:18 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1464C58DE6; Wed, 28 Sep 2022 01:15:19 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id E92746601FE2; Wed, 28 Sep 2022 09:15:16 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1664352917; bh=Bnxo4mGsNU340ALBwPeBDHXqIRSVH5Ima6FLJazC9P8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=EM5n0AgUsjv8qkG8idc3sYRm2E1CS3spXQUnVBu/bIBJnkpbAbDk43Jy4HK9IlKYE EXPRzxBAlmUCGqHa7wLfONXKs9vONZCkdB4OmsyEoEQ4WUDbN5QJzOtFTh9vVLuPq6 V38MJHBHmNy6bR4fM6QXBgV4HLPJqgBoYKNWSazdAw/Q0/m7EDgGpkTF0DvSp7EF2V lzYyr0vzk0Bhy8+cHbTScJslif5wL5a1Gjh98o4EoDLBrO4VE4da6wS6way8W1oJV8 CX32UcHrxEJpS6xwNbhYqaaMbyouRQOF/wNxuonw25921RMiGKfRl0EfgTVakdvsjE 37AKzrmbMDIhA== Message-ID: <7028eda1-d11f-5437-dda4-d261554a453c@collabora.com> Date: Wed, 28 Sep 2022 10:15:14 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 Subject: Re: [PATCH v5 1/6] dt-bindings: arm: mediatek: mmsys: change compatible for MT8195 Content-Language: en-US To: "Jason-JH.Lin" , Matthias Brugger , Chun-Kuang Hu , Rob Herring , Krzysztof Kozlowski Cc: CK Hu , Rex-BC Chen , Singo Chang , Nancy Lin , dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com References: <20220927152704.12018-1-jason-jh.lin@mediatek.com> <20220927152704.12018-2-jason-jh.lin@mediatek.com> From: AngeloGioacchino Del Regno In-Reply-To: <20220927152704.12018-2-jason-jh.lin@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 27/09/22 17:26, Jason-JH.Lin ha scritto: > For previous MediaTek SoCs, such as MT8173, there are 2 display HW > pipelines binding to 1 mmsys with the same power domain, the same > clock driver and the same mediatek-drm driver. > > For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines binding to > 2 different power domains, different clock drivers and different > mediatek-drm drivers. > > Moreover, Hardware pipeline of VDOSYS0 has these components: COLOR, > CCORR, AAL, GAMMA, DITHER. They are related to the PQ (Picture Quality) > and they makes VDOSYS0 supports PQ function while they are not > including in VDOSYS1. > > Hardware pipeline of VDOSYS1 has the component ETHDR (HDR related > component). It makes VDOSYS1 supports the HDR function while it's not > including in VDOSYS0. > > To summarize0: > Only VDOSYS0 can support PQ adjustment. > Only VDOSYS1 can support HDR adjustment. > > Therefore, we need to separate these two different mmsys hardwares to > 2 different compatibles for MT8195. > > Fixes: 81c5a41d10b9 ("dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding") > Signed-off-by: Jason-JH.Lin > Signed-off-by: Bo-Chen Chen Reviewed-by: AngeloGioacchino Del Regno