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 47976C5479D for ; Mon, 9 Jan 2023 08:37:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233215AbjAIIhn (ORCPT ); Mon, 9 Jan 2023 03:37:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47746 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236664AbjAIIhL (ORCPT ); Mon, 9 Jan 2023 03:37:11 -0500 Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B5A013F20 for ; Mon, 9 Jan 2023 00:37:09 -0800 (PST) Received: by mail-wm1-x336.google.com with SMTP id p1-20020a05600c1d8100b003d8c9b191e0so5978505wms.4 for ; Mon, 09 Jan 2023 00:37:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; 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=VeKLpPbr+0opZSsyaNdS4GmUMbw67mVC1MhWp/RMXc8=; b=j2DjT+bRzJvVjlkLjqfEEWT4jY+ZoP+BoB4sAMBIO8cn6gtDboHm/Ows1bCAQ9adgi jZopYzGek5pMHwrtI3kPPh/XubnGujItQpxANrzd1vsKSEqrB/3f2KCYbslJgqxU4F04 jcTQsAvnTmoroqicVgZCnnagXid9Cl4M+cGU9Wc7zRCB1C8muo8V83NCv3EI+0Mq5BID vEFfTJglWJiF8hrXUzAPoKnEVbfkpw8wMMSSW9luI2MwCqs0ZcuMxltYcRJ04xpzXGNk WxXnHbviX9Q19lbTysK/QbFKI/7P4l3/Afm+xh9OatEhNf6LKhlplQtNkkUazIEE4td7 /DuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=VeKLpPbr+0opZSsyaNdS4GmUMbw67mVC1MhWp/RMXc8=; b=yCp9tMIQ7HH9IM72MkcKOES4FpKA3nCHaoCsqtOSuyVcH7f/XvLf/1Z9gJOkLKALtn SNO/1+D3j1m0ezNPpiXxDnpUcaKd8UpV+XwxqXiA5/YtD3hmrob+VCng7SRZoSGrvtu1 okw37IUjfPv5lKlYZ0rPvnsv9gKvkOq8EO3e1+cRXd3wgYmoIR0bXl7ryTnWEbX1AF7I MwEqRMATAC2p9dGprKbWSIJ8SbFN7sF9unfCi2fwe1lSVJ21tC+Q6C/rtc0wyv7MIOgq 8Jt/NKf59wKRlFzFNpSndn/yjYp9oGQRBeiH6GwSLXKTiBpVD1Sc85g9/hL8IHhMkC0a WzBg== X-Gm-Message-State: AFqh2kqi7KsP4k1kmCVus6a+9L3j04+9pA7n2S1R/6xsi15wZutTUPTz 0g6lYJlQu7wR5Zj08sfOpOzhZg== X-Google-Smtp-Source: AMrXdXvGZLtPPaGN5nHVCLSVwjBxlwNzC4/VdLmgdwDyBjlcW7SIj67hiUhm6HTg1UV9Bvxw3EagYw== X-Received: by 2002:a05:600c:4f96:b0:3d9:ed3b:5b3e with SMTP id n22-20020a05600c4f9600b003d9ed3b5b3emr2846989wmq.19.1673253428081; Mon, 09 Jan 2023 00:37:08 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id e35-20020a5d5963000000b00276d8c2332fsm8834593wri.108.2023.01.09.00.37.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 Jan 2023 00:37:07 -0800 (PST) Message-ID: Date: Mon, 9 Jan 2023 09:37:05 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v3 1/4] dt-bindings: soc: samsung: exynos-sysreg: add dedicated SYSREG compatibles to Exynos850 Content-Language: en-US To: Rob Herring , Sriranjani P Cc: krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org, alim.akhtar@samsung.com, pankaj.dubey@samsung.com, ravi.patel@samsung.com, sathya@samsung.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org References: <20221214044342.49766-1-sriranjani.p@samsung.com> <20221214044342.49766-2-sriranjani.p@samsung.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 09/01/2023 02:15, Rob Herring wrote: > On Tue, Dec 13, 2022 at 10:47 PM Sriranjani P wrote: >> >> Exynos850 has two different SYSREGs, hence add dedicated compatibles for >> them and deprecate usage of generic Exynos850 compatible alone. >> >> Signed-off-by: Sriranjani P >> --- >> .../soc/samsung/samsung,exynos-sysreg.yaml | 15 ++++++++++++--- >> 1 file changed, 12 insertions(+), 3 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml >> index 4954790eda6c..427df05224e5 100644 >> --- a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml >> +++ b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml >> @@ -17,7 +17,6 @@ properties: >> - samsung,exynos3-sysreg >> - samsung,exynos4-sysreg >> - samsung,exynos5-sysreg >> - - samsung,exynos850-sysreg >> - samsung,exynosautov9-sysreg >> - tesla,fsd-cam-sysreg >> - tesla,fsd-fsys0-sysreg >> @@ -33,9 +32,17 @@ properties: >> - const: samsung,exynos5433-sysreg >> - const: syscon >> - items: >> - - const: samsung,exynos5433-sysreg >> + - enum: >> + - samsung,exynos5433-sysreg >> + - samsung,exynos850-sysreg >> + - const: syscon >> + deprecated: true > > This is throwing an error in linux-next now. > > How can 1 item in a list be deprecated? What's the not deprecated > value for the entry? Probably this needs to move up to 'items' as the > whole entry is deprecated. I missed this. I'll fix it. I'll updated my dtschema and see the error now. Best regards, Krzysztof