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 7D407C6FD1D for ; Thu, 23 Mar 2023 09:44:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229532AbjCWJoj (ORCPT ); Thu, 23 Mar 2023 05:44:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58886 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229791AbjCWJoT (ORCPT ); Thu, 23 Mar 2023 05:44:19 -0400 Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0F32BE181 for ; Thu, 23 Mar 2023 02:44:17 -0700 (PDT) Received: by mail-yb1-xb34.google.com with SMTP id b18so5001681ybp.1 for ; Thu, 23 Mar 2023 02:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1679564656; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=i0CJdvpb8yQ5/UPQq3eqdF8V0b2VDfu62Lq2XgBdJoE=; b=iOfz1k2QXlxMVkChIRX/Q6LEjm61VoKTWMzjmB+VNlmb4QFiAuXUushWMB9sAJWcOC Gue4QqvkSWmYH1wu5XDtnEL9rFrBLPuitxJIc/Lcnnd3D4aLcmvx4472gVPdRzvnKuO7 WRC1MNDBl65bW0JBUqzPgtG4uewkfrQa6Whp2xYRKSPk/lSSC6jgV2mplSVKskrPH4QV k/k/vZ3GC1IomjZORnsKWn3+0/hOQx75/5LrS8DwymX9FZtIaGpu5pQB+bEtyh4gpo7j pDcKOvBYlapJPq3C10lT49Qv1wjzfzZGcBDWvjy4nBvpTmKdjZ9hurRg5j9v1wBYJ3q9 lXIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679564656; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=i0CJdvpb8yQ5/UPQq3eqdF8V0b2VDfu62Lq2XgBdJoE=; b=M391aVGIVGOlwchsmaNLzgYK/h1CGCHsmwCqkWuOA20aDdB2VOROvaduk2JWq0GP0o jRAhNP/iU0yZ45slmCZD1hz5yj5lDIxj4c1oUoMiqR4jFTX6Qkoe5Y8Il7cTjuJQ0XTZ waO3+j0IzQsZ9GeMt2dTAV02ep5Thxw6QoT6inLyWOwgCBDLT89A3SxjMEKpj2aSWr/Q HAVYRUbBUeglO/Py9+y9FPcxVJaD3P7jaTDMxjUGGeQKQQ9u5fCdkwvy3kktg/z0SJlH 4cGGAxAzbgKoWXLGaIC+1E1Mjy63PIJhbD0lRNkya3FYKEPoOeHF9eCwwvvCFCHjTu4W ECLA== X-Gm-Message-State: AAQBX9cEdFkh2meUyDmTDRBEzgrQnFSpRR7QYoZsUaVUQ83U6IJXxBW/ tabluhUHvwEsYYUytefPkW1ykpJCJ+nnduWS4ZOrlA== X-Google-Smtp-Source: AKy350b1NP6ZPxn4L6Wed0Ucwykk/ZsjRotiCdbdm938Sbe7iZvFXw+Kq68tz05lDs41Hx++zYytMWzfNgx5XB8hiXY= X-Received: by 2002:a05:6902:1502:b0:b75:8ac3:d5cf with SMTP id q2-20020a056902150200b00b758ac3d5cfmr619723ybu.9.1679564656218; Thu, 23 Mar 2023 02:44:16 -0700 (PDT) MIME-Version: 1.0 References: <20230314080917.68246-1-krzysztof.kozlowski@linaro.org> <290b9b19-a320-38a1-4426-51f5725dd54f@linaro.org> <59a6ef88-758f-4ec4-f663-47e4caa552c5@linaro.org> <554dd2ca-0514-dc1e-9add-d49a711bc1f2@linaro.org> In-Reply-To: <554dd2ca-0514-dc1e-9add-d49a711bc1f2@linaro.org> From: Dmitry Baryshkov Date: Thu, 23 Mar 2023 11:44:04 +0200 Message-ID: Subject: Re: [PATCH v2 00/13] mailbox/arm64/ qcom: rework compatibles for fallback To: Krzysztof Kozlowski Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Jassi Brar , Rob Herring , Krzysztof Kozlowski , Manivannan Sadhasivam , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, 23 Mar 2023 at 08:33, Krzysztof Kozlowski wrote: > > On 22/03/2023 23:28, Dmitry Baryshkov wrote: > > On Wed, 22 Mar 2023 at 19:37, Krzysztof Kozlowski > > wrote: > >> > >> On 16/03/2023 07:52, Krzysztof Kozlowski wrote: > >>> On 14/03/2023 13:16, Dmitry Baryshkov wrote: > >>>> On 14/03/2023 10:09, Krzysztof Kozlowski wrote: > >>>>> Hi, > >>>>> > >>>>> Changes since v1 > >>>>> ================ > >>>>> 1. Rebase > >>>>> 2. Make msm8994 fallback for several variants, not msm8953, because the latter > >>>>> actually might take some clocks. > >>>> > >>>> Although the approach looks correct, I think that in some cases it tries > >>>> to mark devices compatible judging from the current driver, not from the > >>>> hardware itself. > >>> > >>> Which is what compatibility is about... > > > > Well, I was trying to say that once we update the driver, the devices > > will not be compatible. But probably our definitions of being > > compatible differ. > > What do you want to update in the driver? What's going to happen with > it? What is missing? Some of these platforms do not have CPUfreq support, which will most likely require programming of cluster and L2/L3 clocks being part of this region. For the reference, I think that sc7180/sm8150/other new platforms are proper examples of 'compatible' devices, so the patchset itself has a correct/good idea beneath. It's just that additional research might be required for the older platforms. -- With best wishes Dmitry