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 2D697C678D4 for ; Tue, 7 Mar 2023 13:15:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230211AbjCGNPv (ORCPT ); Tue, 7 Mar 2023 08:15:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231318AbjCGNPP (ORCPT ); Tue, 7 Mar 2023 08:15:15 -0500 Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 089DD4C6EF for ; Tue, 7 Mar 2023 05:13:58 -0800 (PST) Received: by mail-lf1-x133.google.com with SMTP id r27so16976030lfe.10 for ; Tue, 07 Mar 2023 05:13:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678194835; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=3RGJsxW2mZ6YK2vSWLUn1VWroGwxCh40q2+uvcFwRq0=; b=Y2/HaVYbigstDk28wbyl0mnZ0+kQ4dcAaD+XWImVqSyju6Khcj5Ybc/ZOolUztOmRz uHuYWAXWXVxIu7BGxLL4QVfTQKhLmNUJMB6L4MK9AIVkQp25231O1oL9rKlGZxZg2osA kp1llG64T8PduVzZ6AWmlUuqsY+2kK52wBnJXGdsIzNoxFaSwtvbhXKvMHO6iF5vB4/q GhGaZhvlUNGUsRdCLcD7XpYsazMax2If/EegMs8WWaX8C335KEzmCCBhb35VAP6hEKLT D3D2KJ6ELsy9u5RaOX4fnxpUGYB83e8g07NfkYoF27N3RUFHARVu2hCFQTmzYmm17IPd caHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678194835; h=content-transfer-encoding:in-reply-to:from:references:cc: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=3RGJsxW2mZ6YK2vSWLUn1VWroGwxCh40q2+uvcFwRq0=; b=ADziaCwYOV1gF8ItSiht42ZtBlho7G9Am7fEjKi9UXVwT511Kwa0a8CL+5JuDLbym9 twHvtcXM569e40a29Vmcn6TSTD+Z4DfbbWGOUF5//5oWzHAkbikbCPL/5mNcQnqWYi0I hp0AunHE62NT7P7nRmbPgxNBH11ncFjPzEDP9BsEAD6O41ofPHdW7SetBl4lg07oSXAs mdMGC/uk2WGMaFjn9PGYhUeddZkpDT3I/KGbI79nz8w+YTRBF2/Y4agt1VitgB4caJPs T9x0+vnNIAdJadofL9RqggJLaXV7YV0YsV+0SADurLHsojvv7Ixw/oYA2b8WMHNHlgGi tVNw== X-Gm-Message-State: AO0yUKWo0NccPlh/Or3AudwvD+ckN13vEN/ykz536KD54S0vfLpVEIvc 4ut3rnL/U0grU1O0NmyqiDPjFw== X-Google-Smtp-Source: AK7set9BnfzCM/0PKMhiTvDKoLbDXgQYTu5+SDyFFlcTRB7cIsnnJ7LgMS833H3WUFwTx5rLyGpfJg== X-Received: by 2002:a19:5210:0:b0:4a4:68b8:c2e4 with SMTP id m16-20020a195210000000b004a468b8c2e4mr3943261lfb.59.1678194835019; Tue, 07 Mar 2023 05:13:55 -0800 (PST) Received: from [192.168.1.101] (abyj16.neoplus.adsl.tpnet.pl. [83.9.29.16]) by smtp.gmail.com with ESMTPSA id j8-20020ac253a8000000b00497a32e2576sm2027677lfh.32.2023.03.07.05.13.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Mar 2023 05:13:54 -0800 (PST) Message-ID: Date: Tue, 7 Mar 2023 14:13:53 +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] firmware: qcom_scm: Add SM6375 compatible Content-Language: en-US To: linux-arm-msm@vger.kernel.org, andersson@kernel.org, agross@kernel.org Cc: marijn.suijten@somainline.org, linux-kernel@vger.kernel.org References: <20230307012247.3655547-1-konrad.dybcio@linaro.org> From: Konrad Dybcio In-Reply-To: <20230307012247.3655547-1-konrad.dybcio@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7.03.2023 02:22, Konrad Dybcio wrote: > While it was introduced in bindings, requiring a core clock, and added > into the DT, this compatible was apparently forgotten about on the driver > side of things. Fix it. > > Signed-off-by: Konrad Dybcio > --- > drivers/firmware/qcom_scm.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index 916a0c2fc903..2e8961c84b68 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -1494,6 +1494,7 @@ static const struct of_device_id qcom_scm_dt_match[] = { > }, > { .compatible = "qcom,scm-msm8994" }, > { .compatible = "qcom,scm-msm8996" }, > + { .compatible = "qcom,scm-sm6375", .data = (void *)SCM_HAS_CORE_CLK }, On a second thought, maybe the qcom,scm compatible could optionally consume all three clocks with schema guarding how many should be used, to prevent having to add nonsensical compatibles? Konrad > { .compatible = "qcom,scm" }, > {} > };