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 7ADD1C6FD19 for ; Thu, 16 Mar 2023 06:52:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229602AbjCPGwk (ORCPT ); Thu, 16 Mar 2023 02:52:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40686 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229544AbjCPGwg (ORCPT ); Thu, 16 Mar 2023 02:52:36 -0400 Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B4F415A915 for ; Wed, 15 Mar 2023 23:52:34 -0700 (PDT) Received: by mail-ed1-x531.google.com with SMTP id z21so3613506edb.4 for ; Wed, 15 Mar 2023 23:52:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678949553; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=yDwcFhaglD9ZblUjfqRWfAkGmbeU601dCSliwkSidio=; b=QhWlqAaSYay4qQh+PyIZoJnEqeJpgLcD5wLkFWR14psLl8K2kPx+vKEybsmlfMBOLa G9EB2ivHAvFg5yV9FeacdSq6nrvjiUCX61hwJeJCKiYahTFJOoO4FOU54EGB1e5NhSVa b+ARDzL/DzxPc8Whg9jOb0wWfWPEk+wIgoVT9KcXun1O8w3dvmeN6GImJ766mAVM5ZUF Or/QSV7MYTu/O2NB2ddVPCB0wrc14BvG9ZyY/18rX04cgpzx6JmI9YF/xXwpW6UWq7tH L+RAOHVXVgdvbrgRXx+FzK+esykam1LvOaBKYFWVZZj+80Jcit1q+Fsaby5MDnMGnUEz yRZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678949553; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=yDwcFhaglD9ZblUjfqRWfAkGmbeU601dCSliwkSidio=; b=nvS9AjNoxO2iuWWQSRWB9REs8GyBlkDwkCczayptBwE2nYTDyujeY/kcuxTnCV4pxE EagBVwc3UDbwvTZtgX+B1l5z1eYxkqKp/2/t4h5y9bXd3gg93f3JMuPcXCLj0HdEjcLg OjKu6UWe8qDOdt1ZfwwMrLP4M+uHenGpoHtn0p7SWe89qnasEzrdrJRBfRUfVjKBl7oF OzaAaTxcE0ounQ6dqcDB0kYmIxzjE0oHfBRt5kfuJjjPxE/kQyj8v0ykvOUnrD40YtvM 1P9mVVlhkv66GeN7ThVPKiBImvgdaeXjw1T/1sUKbpBuvnmgjgAyl6dwZTNKj9jBZoZR 85Zw== X-Gm-Message-State: AO0yUKWWpXNqb0QvM52bhL46j/5LKU9fCIqHf97AWVntDne36KjPZotQ VTkX3ss9Wi7xf2xYY7f6jGB25Q== X-Google-Smtp-Source: AK7set+zESAdNb4+mITVojQI4XtD8Bu60zKmFg+VVW2czRdtRcVmnEQYuB8E7uRTrBU3fmtoGPs5VA== X-Received: by 2002:a17:906:1351:b0:924:576b:b145 with SMTP id x17-20020a170906135100b00924576bb145mr8865256ejb.55.1678949553248; Wed, 15 Mar 2023 23:52:33 -0700 (PDT) Received: from ?IPV6:2a02:810d:15c0:828:9827:5f65:8269:a95f? ([2a02:810d:15c0:828:9827:5f65:8269:a95f]) by smtp.gmail.com with ESMTPSA id v10-20020a50a44a000000b004fd204d180dsm3358273edb.64.2023.03.15.23.52.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 23:52:32 -0700 (PDT) Message-ID: <290b9b19-a320-38a1-4426-51f5725dd54f@linaro.org> Date: Thu, 16 Mar 2023 07:52:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v2 00/13] mailbox/arm64/ qcom: rework compatibles for fallback Content-Language: en-US To: Dmitry Baryshkov , 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 References: <20230314080917.68246-1-krzysztof.kozlowski@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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... > > For the reference, on msm8994 the apcs is a clock controller for the l2 > clocks (which we do not support yet). If I'm not mistaken, on msm8976 > the apcs region contains a mux for the cluster1 clocks. On sdm630/660 > the apcs region also seems to be involved in CPU clocks scaling. The question is this means they are incompatible? > > On the other hand, the sc7180/sm8150 part seems logical. > Best regards, Krzysztof