Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp10748524rwb; Fri, 25 Nov 2022 07:26:15 -0800 (PST) X-Google-Smtp-Source: AA0mqf7okjWR22Yu/Bk2IdZkzRsErvTxMsKxEEW3NsxzgZ2kMxBPCD1u2LRU7momDab/sZBzZaXF X-Received: by 2002:a17:902:9a01:b0:186:8791:e9a7 with SMTP id v1-20020a1709029a0100b001868791e9a7mr21844838plp.91.1669389974921; Fri, 25 Nov 2022 07:26:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669389974; cv=none; d=google.com; s=arc-20160816; b=dwt1sn2mLrDR6IuILabFl1RXxQwH6UvyxvJBV4cJnk9L/gnHeYUvoDSbSyXZk5pL7b arc3lw++H6aNPlQRhgXh+sNLPk61876vPAxTmIW1dL4Hg2TnnCSx8pg8Wsr2xDZgNSFV C6P/8a5QshVd+7uxI+IWJf7nAyU0poV4t6SIjd0M4zo5qFTtI2yf5BK8WWQvNDw/Nw0k MsoY8eJRkCWIWJNbJiPaXiVtEcJ8SxzH4Oh+HCSLclXwQIoPAKA1k0dzgoyK0dI5Hlp2 5sWMZnuwFZ+sDXlkOLs4BWBww+CYi8E87eBnU0pN3c2cjssJud9lfr/cXnj1SdVwh55T OCtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=jdhD7TyJAV9Yjv88DjHcR22sCnTCoFYgtGFsGgYfXW0=; b=F9PrdZ0y/BNjg7AdLKIsERCC6ZYuwxyCkxzvRuVsRiPDqP0kmolH9GMGIe3C5cMhgX sBCceWvDKgzYlUrqLC97i9ekG4QdLgmvUqfv8i7zg2yXq4aQkqcPGsPI3+TsmV7zDL+F eruHVb8Fzg23y64uXTTwSXO+cA4jmdh8pTYWEumoF4R40Y48x5HK5PSQtpZg7hZ+ZxgP 1fsJMLpCEJzsiInofGAS+/R21cRE58IeviJPXDB9AcYpVr7xs93g8+NE5j7xtg3B+7Od HXQsl0IzhWf52Uvj1xatd7hkOgvL1ZpBZptrcrTEr0OdxvyLP1n2gdNyaSjA/VicTUOT G+RQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Uqm0qn5p; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cv5-20020a056a0044c500b00573ede1a4easi3932951pfb.88.2022.11.25.07.26.00; Fri, 25 Nov 2022 07:26:14 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Uqm0qn5p; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229814AbiKYO51 (ORCPT + 86 others); Fri, 25 Nov 2022 09:57:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52932 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229735AbiKYO5Z (ORCPT ); Fri, 25 Nov 2022 09:57:25 -0500 Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22FC73D939 for ; Fri, 25 Nov 2022 06:57:24 -0800 (PST) Received: by mail-pg1-x529.google.com with SMTP id 130so4152099pgc.5 for ; Fri, 25 Nov 2022 06:57:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jdhD7TyJAV9Yjv88DjHcR22sCnTCoFYgtGFsGgYfXW0=; b=Uqm0qn5phqXeWhCqw/F05B4fb0YwjNUdPVyTz7nqy4Q+gyHwPLQ6HvMR1FgS8jsCQU q1IK7QHUqNoSej2t1wae6i6GrPqtmNhKTjRNOXv6dBWEzRWn3zQdAUmrUhsthaHH4ikA cKR2je4BA6e11up3gJriA/c3gADhUN24D8E0lcOKMwEyz+uwt53A6gsbAQTo8nUyFU29 Nzm2onZOM9+PF/v7Fqfbx9qr3HMphnAgYbvo2Oh7YGfVdmy0npoS0XPfeShCqUtIbkWN 3x124UDWLQJk1XjK6AP0SfKR3Jb8jr/J7dC5VtiH9wtkfA9KDI0Bz/IE257BuNOsWrFa g8Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=jdhD7TyJAV9Yjv88DjHcR22sCnTCoFYgtGFsGgYfXW0=; b=FTaeG6nV1qeMmJujJfNhk6gEwl42TuofSHOzPjgnEATP4mnKTR4ccEJTqVAO+fB4kd v61+rz5xBq7/nXokA5GOyozxMg2ceyP2zUi4/ZH9vPggG3nKJgNoGgjP5nKmAK7IDFtU cFX2bO3NFtXj8CfcfAsOiyzm4k6NAtVaOITC/M/7tOxCSAqsUHr9a2phAW10WLa5S1ve DaOleO4B9ZjN1zkM5xP+YnT5W8zYrZn77NOdJWP9BcjAE6MbNUp6hHMpg1ku/R0jdaof MzdYxi8gED70WM7xVdCCaO/f//TDTzpQtkz87lWn3LP4bl6n5/D3GgQw8ddyYF0uQ5KS pQ8w== X-Gm-Message-State: ANoB5pnHmMuLZzErtyW+zVv3SGDQ3wmC2VyxBOFsjrPJqvIRqJkWWALZ rWZu10WXWYTpOASkeLF6QYevyn+ZWbSSpVfp9OiIyQ== X-Received: by 2002:a63:e008:0:b0:46f:5979:8889 with SMTP id e8-20020a63e008000000b0046f59798889mr16712060pgh.119.1669388243590; Fri, 25 Nov 2022 06:57:23 -0800 (PST) MIME-Version: 1.0 References: <20221125112201.240178-1-krzysztof.kozlowski@linaro.org> <20221125112201.240178-3-krzysztof.kozlowski@linaro.org> In-Reply-To: From: Sam Protsenko Date: Fri, 25 Nov 2022 08:57:12 -0600 Message-ID: Subject: Re: [PATCH 3/4] dt-bindings: soc: samsung: exynos-sysreg: add dedicated SYSREG compatibles to Exynos5433 To: Krzysztof Kozlowski Cc: Lee Jones , Rob Herring , Krzysztof Kozlowski , Alim Akhtar , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, Sriranjani P , Chanho Park Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 25 Nov 2022 at 08:47, Krzysztof Kozlowski wrote: > > On 25/11/2022 15:22, Sam Protsenko wrote: > > On Fri, 25 Nov 2022 at 05:22, Krzysztof Kozlowski > > wrote: > >> > >> Exynos5433 has several different SYSREGs, so use dedicated compatibles > >> for them. > >> > >> Signed-off-by: Krzysztof Kozlowski > >> > >> --- > >> > >> Cc: Sriranjani P > >> Cc: Chanho Park > >> Cc: Sam Protsenko > >> --- > > > > Hi Krzysztof, > > > > Just curious: what is the rationale for adding those more specific > > sysregs? AFAIR, e.g. in Exynos850, different SysReg instances have > > pretty much the same register layout. > > > > On Exynos5433 all these blocks have different registers. Are you saying > that Exynos850 has four (or more) sysregs which are exactly the same? > Same registers? Why would they duplicate it? > Ah, no, you are right. Just checked it, they are different. Just first couple of registers are similar between blocks, that's why I memorized it wrong. So as I understand, adding those new compatibles follows "describe HW, not a driver" rule? Because AFAIU, right now it'll fallback to "syscon" compatible anyway. > Best regards, > Krzysztof >