Received: by 2002:a05:7412:cfc7:b0:fc:a2b0:25d7 with SMTP id by7csp2140493rdb; Tue, 20 Feb 2024 20:08:44 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCVzN0g52RFlMlhRTJJIQ04Xmv9bW3g647qNZb865szF4ohF0ro5zhAVL5dV/MPblWNokkCns4lbUwQods0DXzxeqKTuvWxZHIqe2SSbMg== X-Google-Smtp-Source: AGHT+IF1cyO19ZUpUYM97ZupCDIleKMN+rH+VBjex2jDsjD9hSks3IHYN6lkmHWBAULrsi1GtBkn X-Received: by 2002:a05:6402:609:b0:564:eff:5798 with SMTP id n9-20020a056402060900b005640eff5798mr8948020edv.38.1708488524775; Tue, 20 Feb 2024 20:08:44 -0800 (PST) Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id t21-20020aa7d715000000b005640a717b42si3960265edq.170.2024.02.20.20.08.44 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Feb 2024 20:08:44 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-74043-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@google.com header.s=20230601 header.b=xMyMoqWJ; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-74043-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-74043-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=REJECT sp=REJECT dis=REJECT) header.from=google.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 509CB1F25532 for ; Wed, 21 Feb 2024 04:08:44 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id DA7133984A; Wed, 21 Feb 2024 04:08:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="xMyMoqWJ" Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2794D38DDD for ; Wed, 21 Feb 2024 04:08:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.208.54 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708488512; cv=none; b=XFKZDleNKuPw/VW+DU8Et56QA8bMRWrouWU3j1kq4uGLwKoxpLAkhp3fW+3Ac1GRiFbV9Ztdh9a7wVVEdmKVWBt6ZMmSvvlQJN4vuixvUC6de5wHOaENTdfaZK7Qoe13b9ybW6anqf/L1fQDJ47VCgj/C+xp+s8Pu93UT78pfhs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708488512; c=relaxed/simple; bh=VMnZZMlvZpAbCe/9PN4y8l6fqn6fzCdYpCLaJwhENmQ=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=aAtrv8JohoRBwqL4FQtPWJfHgAAZnENFCI3l2AWSNvHeWWX7nmmAlx+7D3z/MFIzRxBGqJq6jAI9MdSi1XtKj9hwZ3O9THO+//H4g/m4NxMgq5pwDQLdYfqoshAJ1WWzHUxF43SyMZdm42Aj+Za6MaUrDXc0/NrPgRNQWr0n2Tw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=xMyMoqWJ; arc=none smtp.client-ip=209.85.208.54 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=google.com Received: by mail-ed1-f54.google.com with SMTP id 4fb4d7f45d1cf-564d311513bso5015a12.0 for ; Tue, 20 Feb 2024 20:08:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1708488509; x=1709093309; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1vYLUdRHnLOuE5GlvVy5mmDzCcmYulWt5UKno2mI/Ts=; b=xMyMoqWJWUh+y/Z7mD1swhWNCdspx5wwLL/H6thBwHhdCxoeo5NL9HnfVoYpll3wQR FBi23f/6ITJisMLOy/rh/cmGA9ExQLxygiZQwu5Tksbwy264juz64oMyLem1Yts9EJgo lMg+2fsgnmtK+tRuLpxdngmnJQpEvV6bj/aIdqFQPqnV8yai+zFjK34GJqkSKLsRHbtc hE+ZWHamJbUevirArV2knhqefRIezkM8M9v1IBwVydOVRRRkXmoEQWGFoLJylxpen5/N F1PnQbBWEyaPyT2QuCkLfOUAyC3Nr39tCg0gcjiXzOGC/ZX2QOsIql3Qwb894CkvIbvV 1zmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708488509; x=1709093309; h=content-transfer-encoding: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=1vYLUdRHnLOuE5GlvVy5mmDzCcmYulWt5UKno2mI/Ts=; b=pIvzeTFFm0aDn3t0VIeQcf9BOt7bj21gz8QMYZU3pEnLv2Hl1d8/PGkX1tTo9DwJZM ifCDW4x2Lpl7hUuqj8EBjm/P3Wzai1iwpnOIeky9iV7O/LltYw/7CdcT5FXzV4Lk+bNs Begnz4jqBq8Uy4UpN0oTlaeEBahGstnlmKOqRWIi/lHiZZXWx1vMmpvDFHm2KpfhWO6G xg1nlY3+cQibrnUHLEddDxaAc421mr6FnvDNdZdEuRgpMoZPfbMOZosm5umxswISzsU4 aeAtnkGbENJ8LKm/hXlMgMW5w+k0neEIWyTaISFzY0l7giMnTj5yhpj0O0qGPqxdDuiY IpMA== X-Forwarded-Encrypted: i=1; AJvYcCXu8rC4pjQeulj4UW872GAnKEZqtjSdSJ5DTiXquvGebpdNH0NcD3n4wFrzQkPGX/NSFBv6ueH6Aa5CrVNfpgiZz4WSTfoHQ36K1bVv X-Gm-Message-State: AOJu0YzPoOOZArgwzTm6abmsLbTflrgmBc78vc1ic2Cptdh+kRg08+Ty C5KWjvJkRpTPAD9hic947tiAfC7tC9x/42IRsDF+PC1Iabr6N6QD5ePItYbiqtd2UHizXQT+ntn A8Y+bN7fvrqslwNdNDL2sFBKi8u6rFEWcxUwH X-Received: by 2002:a50:d5d9:0:b0:563:f48f:a5bc with SMTP id g25-20020a50d5d9000000b00563f48fa5bcmr47442edj.5.1708488509288; Tue, 20 Feb 2024 20:08:29 -0800 (PST) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20240212213147.489377-1-saravanak@google.com> <20240212213147.489377-4-saravanak@google.com> <20240214-stable-anytime-b51b898d87af@spud> In-Reply-To: From: Saravana Kannan Date: Tue, 20 Feb 2024 20:07:48 -0800 Message-ID: Subject: Re: [PATCH v2 3/4] dt-bindings: Add post-init-supplier property To: Krzysztof Kozlowski Cc: Conor Dooley , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Greg Kroah-Hartman , "Rafael J. Wysocki" , Ard Biesheuvel , Frank Rowand , Len Brown , Andy Shevchenko , Daniel Scally , Heikki Krogerus , Sakari Ailus , kernel-team@android.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-efi@vger.kernel.org, linux-acpi@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Feb 17, 2024 at 2:27=E2=80=AFAM Krzysztof Kozlowski wrote: > > On 15/02/2024 00:32, Saravana Kannan wrote: > > > > Good point. Done. > > > >>> + # One or more suppliers can be marked as post initialization sup= plier > >>> + description: > >>> + List of phandles to suppliers that are not needed for initiali= zing or > >>> + resuming this device. > >>> + $ref: /schemas/types.yaml#/definitions/phandle-array > >>> + items: > >>> + maxItems: 1 > >> > >> Rob's bot rightfully complains here about invalid syntax. > > > > I added these two lines based on Rob's feedback. Is the indentation > > that's wrong? > > > > Yeah, I'm trying to run the dts checker, but I haven't be able to get > > it to work on my end. See my email to Rob on the v1 series about this. > > > > $ make DT_CHECKER_FLAGS=3D-m dt_binding_check > > > > The best I could get out of it is a bunch of error reports on other > > files and then: > > ... > > /Documentation/devicetree/bindings/post-init-suppliers.yaml: > > ignoring, error parsing file > > ... > > > > I also tried to use DT_SCHEMA_FILES so I can only test this one file, > > but that wasn't working either: > > I see the errors immediately during testing, no special arguments needed: > > crosc64_dt_binding_check post-init-supplier.yaml > make[1]: Entering directory '/home/krzk/dev/linux/linux/out' > LINT Documentation/devicetree/bindings > DTEX Documentation/devicetree/bindings/post-init-supplier.example.dt= s > ../Documentation/devicetree/bindings/post-init-supplier.yaml:84:12: > [error] syntax error: mapping values are not allowed here (syntax) > CHKDT Documentation/devicetree/bindings/processed-schema.json > ../Documentation/devicetree/bindings/post-init-supplier.yaml:84:12: > mapping values are not allowed in this context > make[3]: *** [../Documentation/devicetree/bindings/Makefile:26: > Documentation/devicetree/bindings/post-init-supplier.example.dts] Error 1 > make[3]: *** Deleting file > 'Documentation/devicetree/bindings/post-init-supplier.example.dts' > make[3]: *** Waiting for unfinished jobs.... > ../Documentation/devicetree/bindings/post-init-supplier.yaml:84:12: > mapping values are not allowed in this context > SCHEMA Documentation/devicetree/bindings/processed-schema.json > /home/krzk/dev/linux/linux/Documentation/devicetree/bindings/post-init-su= pplier.yaml: > ignoring, error parsing file > make[2]: *** [/home/krzk/dev/linux/linux/Makefile:1424: > dt_binding_check] Error 2 > make[1]: *** [/home/krzk/dev/linux/linux/Makefile:240: __sub-make] Error = 2 > make[1]: Leaving directory '/home/krzk/dev/linux/linux/out' > make: *** [Makefile:240: __sub-make] Error 2 I think I was just getting overwhelmed with the sea of error logs I saw (for unrelated files). If I don't use the flags it's way too noisy and it's not always the first thing that's reported. This is what I see now and I think I now understand what to look for. $ make DT_CHECKER_FLAGS=3D-m dt_binding_check DT_SCHEMA_FILES=3DDocumentation/devicetree/bindings/post-init-suppliers.yam= l LINT Documentation/devicetree/bindings /Documentation/devicetree/bindings/post-init-suppliers.yaml:84:12: [error] syntax error: mapping values are not allowed here (syntax) CHKDT Documentation/devicetree/bindings/processed-schema.json /Documentation/devicetree/bindings/post-init-suppliers.yaml:84:12: mapping values are not allowed in this context SCHEMA Documentation/devicetree/bindings/processed-schema.json /mnt/android/linus-tree/Documentation/devicetree/bindings/tpm/ibm,vtpm.yaml= : ignoring, error in schema: properties /mnt/android/linus-tree/Documentation/devicetree/bindings/post-init-supplie= rs.yaml: ignoring, error parsing file /mnt/android/linus-tree/Documentation/devicetree/bindings/soc/tegra/nvidia,= tegra20-pmc.yaml: ignoring, error in schema: allOf: 0: then: properties: pinmux /mnt/android/linus-tree/Documentation/devicetree/bindings/net/lantiq,pef225= 6.yaml: ignoring, error in schema: properties: lantiq,data-rate-bps /mnt/android/linus-tree/Documentation/devicetree/bindings/iio/pressure/hone= ywell,mprls0025pa.yaml: ignoring, error in schema: properties: honeywell,pmin-pascal /mnt/android/linus-tree/Documentation/devicetree/bindings/iio/pressure/hone= ywell,hsc030pa.yaml: ignoring, error in schema: properties: honeywell,pmax-pascal DTEX Documentation/devicetree/bindings/post-init-suppliers.example.dts Documentation/devicetree/bindings/post-init-suppliers.yaml:84:12: mapping values are not allowed in this context make[2]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/post-init-suppliers.example.dts] Error 1 make[2]: *** Deleting file 'Documentation/devicetree/bindings/post-init-suppliers.example.dts' make[1]: *** [/mnt/android/linus-tree/Makefile:1432: dt_binding_check] Erro= r 2 make: *** [Makefile:240: __sub-make] Error 2 > > > https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sou= rces-with-the-devicetree-schema/ > > I assume you develop on some older trees, because both next and v6.8-rc1 > work... or standard issues: old dtschema, old yamllint. > > I am afraid you do it for some old Android kernel... :( No, I always develop on Linus's tree and test it on an android kernel that's behind Linus's tree by a month or so. My yamllint version is 1.32.0, but until 2 weeks ago the latest yamllint version was 1.33.0. And dt-schema is 2022.08.2-5 and I had to revert this from Linus's tree to get it to work: b32dcf23a03e dt-bindings: Drop kernel copy of common reserved-memory bindin= gs Unfortunately, AFAIK, I don't have permissions to change the package repo, so can't really install a newer version. Thanks for the tips. -Saravana -Saravana