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 B89FAC433FE for ; Tue, 4 Jan 2022 22:26:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235454AbiADW0H (ORCPT ); Tue, 4 Jan 2022 17:26:07 -0500 Received: from mail-oi1-f172.google.com ([209.85.167.172]:39592 "EHLO mail-oi1-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234768AbiADW0H (ORCPT ); Tue, 4 Jan 2022 17:26:07 -0500 Received: by mail-oi1-f172.google.com with SMTP id x10so56652903oix.6; Tue, 04 Jan 2022 14:26:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=JnOadLKUCLxTeQKKTc3saQOhwTodIVbhHkqdpkUyL30=; b=WFYzZklu7ExpTwNpAloUxXp5mKb1feZSZPj1q4u3uuJGeMK9gsGAnMt6ITs56VOUlW saDzVyarRYzoO8PnQ//4fbdkJ3gEw2se3vDBTlg8yiGE4dd9lAVdaRuLdIrLh7hGHl+l cd9h9eDQJ7P+lLIz3AFLy53HnEY8Mma2yE20MxfY7xm5Gu5Rz1xCBd23QofbBRipVL0j h1nq8HHtFw57vLv9UwZYNmOZIzUDnLHTt5sunAmVaOZSQ8uNv80en5OGozxWrokrCYyZ cOPt/2uY6NW2hFr4g71FQzZN4jsauSM1CX10Zu+z0F3RsvDqXcJAHRKikHPi4/u+1DGE Bqsg== X-Gm-Message-State: AOAM530QuBof6LR5xclmSiuhFuuSODYCV9QMi54uu1X2n6pTu0shnD2p IZbZ2fOhCdNxn4AI5w+AKA== X-Google-Smtp-Source: ABdhPJxfmZnICaR0AFOGdWsnbelA0aJZsRc1Kgnndk6DcVeWC0CYljTp86RqQf43B5yP69zwu5wQGg== X-Received: by 2002:a05:6808:10d1:: with SMTP id s17mr395747ois.26.1641335166437; Tue, 04 Jan 2022 14:26:06 -0800 (PST) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id c139sm7472227oob.31.2022.01.04.14.26.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jan 2022 14:26:05 -0800 (PST) Received: (nullmailer pid 1557364 invoked by uid 1000); Tue, 04 Jan 2022 22:26:04 -0000 Date: Tue, 4 Jan 2022 16:26:04 -0600 From: Rob Herring To: Dmitry Baryshkov Cc: David Heidelberg , Rob Clark , Sean Paul , Abhinav Kumar , David Airlie , Daniel Vetter , Krishna Manikandan , ~okias/devicetree@lists.sr.ht, linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Discussion: dt-bindings: display: msm: dsi-controller-main: fix the binding Message-ID: References: <20211225205352.76827-1-david@ixit.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Sun, Dec 26, 2021 at 02:34:08AM +0300, Dmitry Baryshkov wrote: > Hi, > > On Sat, 25 Dec 2021 at 23:54, David Heidelberg wrote: > > > > This binding is not much validating the old DSI v2. > > > > Currently we don't differentiate old v2 from new versions, > > so we need to figure out how to validate them. > > > > I propose specific compatible depending on mdss version, but I would be > > glad, if someone with deeper knowledge proposed the names. > > > > I'm willing to implement it then and back from autodetection. > > I'd suggest to use hardware-specific compatible for apq8064 (and maybe > other v2 hosts if somebody adds support). For example > "qcom,apq8064-dsi-ctrl" or "qcom,dsi-ctrl-apq8064" (no strong > preference here). The former. > For 6G hosts it will probably make sense to use IP versions instead > ("qcom-dsi-ctrl-6g-v2.4.1"). Humm, we went down the path of version numbers for QCom blocks, but the result was not much reuse of same version on more than 2-3 parts if that. So stick with SoCs for naming unless there's a strong case that version numbers to SoC parts is 1 to many. Rob 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 D0849C433EF for ; Tue, 4 Jan 2022 22:26:09 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 84F7810E632; Tue, 4 Jan 2022 22:26:08 +0000 (UTC) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) by gabe.freedesktop.org (Postfix) with ESMTPS id 28B2B10E4DE; Tue, 4 Jan 2022 22:26:07 +0000 (UTC) Received: by mail-oi1-f177.google.com with SMTP id s73so61608682oie.5; Tue, 04 Jan 2022 14:26:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=JnOadLKUCLxTeQKKTc3saQOhwTodIVbhHkqdpkUyL30=; b=nwnBBuXaiiMGt9U5auscaNEAgp2g6A6/1IVb5KTXRfBNLQ2tY/neG6qfBTx6pADkl5 Noyn2nlmuz4gSLYq1PNlGaU0rt4ZMUIhO93MmewDgFXQStVhfBo91W2R2L1n8NH4tryy dQSnk98RuVknwllLbfjZE3hPG9MqxXXVhx3pIcPw1qMSf5ngu8em/19pydvXCj3zGxJc gfaXyhQ6sIHifmSRPI6nJnpFCXCrJgdvjOlHDfESCphhrZ0vyk05ImhfYmqLKV0xcO9k /CttrZn8tzdsNfw/vViMzneZAI9uKYQxeEroQU0NEy+HYCnBDxalH9ZQEKJit8pEsP9c +oTw== X-Gm-Message-State: AOAM5319tHlMcu4aNXVJ52tMqBsg5i+M017JmQGwj7IzjQRg54RBmGKv BuSSbpWDmxBBAJUv30owVA== X-Google-Smtp-Source: ABdhPJxfmZnICaR0AFOGdWsnbelA0aJZsRc1Kgnndk6DcVeWC0CYljTp86RqQf43B5yP69zwu5wQGg== X-Received: by 2002:a05:6808:10d1:: with SMTP id s17mr395747ois.26.1641335166437; Tue, 04 Jan 2022 14:26:06 -0800 (PST) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id c139sm7472227oob.31.2022.01.04.14.26.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jan 2022 14:26:05 -0800 (PST) Received: (nullmailer pid 1557364 invoked by uid 1000); Tue, 04 Jan 2022 22:26:04 -0000 Date: Tue, 4 Jan 2022 16:26:04 -0600 From: Rob Herring To: Dmitry Baryshkov Subject: Re: [PATCH] Discussion: dt-bindings: display: msm: dsi-controller-main: fix the binding Message-ID: References: <20211225205352.76827-1-david@ixit.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Krishna Manikandan , devicetree@vger.kernel.org, David Airlie , linux-arm-msm@vger.kernel.org, Abhinav Kumar , David Heidelberg , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, Sean Paul , ~okias/devicetree@lists.sr.ht Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Sun, Dec 26, 2021 at 02:34:08AM +0300, Dmitry Baryshkov wrote: > Hi, > > On Sat, 25 Dec 2021 at 23:54, David Heidelberg wrote: > > > > This binding is not much validating the old DSI v2. > > > > Currently we don't differentiate old v2 from new versions, > > so we need to figure out how to validate them. > > > > I propose specific compatible depending on mdss version, but I would be > > glad, if someone with deeper knowledge proposed the names. > > > > I'm willing to implement it then and back from autodetection. > > I'd suggest to use hardware-specific compatible for apq8064 (and maybe > other v2 hosts if somebody adds support). For example > "qcom,apq8064-dsi-ctrl" or "qcom,dsi-ctrl-apq8064" (no strong > preference here). The former. > For 6G hosts it will probably make sense to use IP versions instead > ("qcom-dsi-ctrl-6g-v2.4.1"). Humm, we went down the path of version numbers for QCom blocks, but the result was not much reuse of same version on more than 2-3 parts if that. So stick with SoCs for naming unless there's a strong case that version numbers to SoC parts is 1 to many. Rob