Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp233840pxh; Tue, 9 Nov 2021 09:51:17 -0800 (PST) X-Google-Smtp-Source: ABdhPJw6TwenHPbgjDDFgmUD4D5yk88GbRsaKofbTvLJGVzHdeON/aEgYwg9sLLZJAdBDQ4DXI0b X-Received: by 2002:a05:6402:4316:: with SMTP id m22mr12987122edc.349.1636480277135; Tue, 09 Nov 2021 09:51:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636480277; cv=none; d=google.com; s=arc-20160816; b=yCkOElOFWSv11qouwaQZpC+zBcDKQ/B2Emj/ebpItbMg02J39N/D9TGXBeGvUPMG9m TJQD56u71O55X7czerBIcRt6s6pKbrLkl3quB1XP9xSovFemxgSxXpOR7TRSC36nuUpF StvvvHo/T5TIct8xi6LH4whKHUxx7U6VieviQJ6e+2Ey6OKML5lkX1dGUXQhKx8GMT3z mxcGsFelOAtY8dCHpDPPjZ5cX9mqVPxKpa3Is2bXjGn8MpIfZNHNV/rQbZ870b9XKIub PRPwcVYXoV5OkUAYz6MWa5DiAgRMhblp8uzWB9uIgxwZi4JoUnfw3PdISYagK7F8qNfq /jIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=kus4q4w/MRHo7vb0zRbS2VwR79Spya1yRC0ArOdsenE=; b=hRm1mBD7XPHQ2n3ssihdjp0d/bStDSoSYt7XKvnjj7vzgOBo2CgmhJL7q8ibIfvQ/d oE7CepJjbAw3KPKOM+PXDOCoGNcQ3VLI6MMfLoPxh4GjJtYkj2ex5vJRS1jNyWYBMH5z Akp0IB48QWtpmGbCMWwg09Tf+9uwXYAphjtobH5GwTCTsnVUgGStMV6Lzv31zoQEnTaZ LKiXCpnxEhIPdApwKDS/zW6BDzktqSmAEFMdkAIE3iEkGQhgjQSZZLl+513dJsne44NI zy73bKfDVepUPMJ4f9IDFAWavqc4Cvk4FFPyc335nwmOZoO6MmDA9XiSWcNLB3+DJv3F 06bg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ragnatech-se.20210112.gappssmtp.com header.s=20210112 header.b=ZWZnKj77; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dp22si25877321ejc.472.2021.11.09.09.50.50; Tue, 09 Nov 2021 09:51:17 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ragnatech-se.20210112.gappssmtp.com header.s=20210112 header.b=ZWZnKj77; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244690AbhKIJMh (ORCPT + 99 others); Tue, 9 Nov 2021 04:12:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244688AbhKIJMf (ORCPT ); Tue, 9 Nov 2021 04:12:35 -0500 Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62D28C061766 for ; Tue, 9 Nov 2021 01:09:49 -0800 (PST) Received: by mail-lj1-x230.google.com with SMTP id h11so34997655ljk.1 for ; Tue, 09 Nov 2021 01:09:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ragnatech-se.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=kus4q4w/MRHo7vb0zRbS2VwR79Spya1yRC0ArOdsenE=; b=ZWZnKj77Bb0zN+NtDHkcLIakxLUogbyA7v7+ivtezp4n4NuGhNWL6tJEsoUAl4X2Rz zEK5cQWJwG//muWN+ClyrRUkHFSKzTZ8sb3zWMYQGRfiyDXmY9RRibc2pA5/NwWi1cSH i50S/3hrwkOVmnWp6TgVRLIptDNgAKE66Nszt8RzaMrsQPBJ87+2h2YAvlIl2W68c2CG Tl5dlw4nQrbdXgZAlIuQnhOJ7O2PC+AJeaAxU1Rv1eHInQsjVlHrxAtnItoeCncXvqRB FSelqX4zqam4rHbF6NNFRtJrMmlIridh9KAvX+00U53pz0Tq8iMAsUJ6FKMiI3netaA1 hGbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=kus4q4w/MRHo7vb0zRbS2VwR79Spya1yRC0ArOdsenE=; b=C0H/h3dFGr6OvRs4mhxW/xwtoUb4TtS8glN20ex12B63rUXp8bhFjGMIpJABidORWw Wzdmngy2uT9QK267L+ndjxa59dZN7puiLLqLqBQl4bELy29+c4D7mOazB4la8cVGzAEP wYQDGVhKDDkWxgOF87ZLzIqpsGk1uJg6rFgEv6qHd7+xVdySmWllwsxFuly6kqDbkJFr 3Hx+/JwZMG0OoRL8z+XxV6euYgY0iYpjrZkVyrF8nhdDNttSsENNrebnq1B2nVzXl7ul csFBpH9Zj3ocrIRF8XFUujf/Td20O0BBISHsss0WJMMJlE1bh+oCSAtsBJ7hDacfJCWR xd6A== X-Gm-Message-State: AOAM530dww2Hu5nOAfvSPzjLvQgXWJ76yaCXoO3A2kwlAvj4HBqUCogp Z7A4FlGN/VHu7NWlL8zlt3L3og== X-Received: by 2002:a2e:8515:: with SMTP id j21mr5531503lji.531.1636448987671; Tue, 09 Nov 2021 01:09:47 -0800 (PST) Received: from localhost (h-46-59-88-219.A463.priv.bahnhof.se. [46.59.88.219]) by smtp.gmail.com with ESMTPSA id d11sm191292lfq.303.2021.11.09.01.09.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Nov 2021 01:09:47 -0800 (PST) Date: Tue, 9 Nov 2021 10:09:46 +0100 From: Niklas =?iso-8859-1?Q?S=F6derlund?= To: Geert Uytterhoeven Cc: Kieran Bingham , Linux-Renesas , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Kernel Mailing List , Rob Herring Subject: Re: [PATCH 0/9] arm64: dts: renesas: Thermal binding validation Message-ID: References: <20211104224033.3997504-1-kieran.bingham+renesas@ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-11-09 09:43:33 +0100, Niklas S?derlund wrote: > > > linux/arch/arm64/boot/dts/renesas/r8a77951-ulcb-kf.dt.yaml: > > > thermal-zones: sensor3-thermal:cooling-maps:map0:contribution:0:0: > > > 1024 is greater than the maximum of 100 > > > From schema: Documentation/devicetree/bindings/thermal/thermal-zones.yaml > > > > > > This validation error appears to be pervasive across all of these > > > bindings, but changing that will be more invasive and require someone to > > > perform dedicated testing with the thermal drivers to ensure that the > > > updates to the ranges do not cause unexpected side effects. > > > > Niklas? > > I will have a look. The thermal driver is the one driver where I have > automated CI test running. So the core of the issue is that the definition of the property changed in the txt to yaml conversion. The original definition was, Optional property: - contribution: The cooling contribution to the thermal zone of the Type: unsigned referred cooling device at the referred trip point. Size: one cell The contribution is a ratio of the sum of all cooling contributions within a thermal zone. While the new binding states, contribution: $ref: /schemas/types.yaml#/definitions/uint32 minimum: 0 maximum: 100 description: The percentage contribution of the cooling devices at the specific trip temperature referenced in this map to this thermal zone Looking at the real world usage of this only 2 out of 17 platforms sets a contribution value less or equal to 100. I will send a patch to fix the bindings. -- Kind Regards, Niklas S?derlund