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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 16A8CC3DA49 for ; Tue, 23 Jul 2024 19:25:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=QqsG9LVI/Oe7Jo1CJP56V5bT9Hx2Nybz6hcCO/GL8XI=; b=3ydWCOsvlcKYD9pRwm0QosFa/A 0Gw/VDlDynu+/K1w395i9ttB7GkqTM2YO+2OPSidm65lX+BNPaRNxJYLtq1W/3NMjcnENNDPopriq 4H9wRlPEzHCFcEICK+5vutq6ZhiJ9UbOa14TYV8NKS8oatS7MlOJN8poHCVWO/MAU4OgTRSpxevO5 XmjeTiW8zObpC9HHtUAPxLabWFhIkywwxh4iFc2+xtNOspzfNyIa3FNk/m+gwZwd9In82xqGnqcPY GBrN9LprsW6SzEZ1MFzku8TYrf/y9eBk+IHb4z66IY64jVI+vjL9XfG/PkDFt/oeEqXLL9IT1lziS x4KrCZAg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWL8C-0000000DKgA-3AHN; Tue, 23 Jul 2024 19:25:04 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWL7p-0000000DKbP-2k4b for linux-arm-kernel@lists.infradead.org; Tue, 23 Jul 2024 19:24:43 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 053F960AF3; Tue, 23 Jul 2024 19:24:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7C0E9C4AF0E; Tue, 23 Jul 2024 19:24:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1721762680; bh=2DRmsMG6kRZYBP6pQwNntBFkhKv/vMvD1XVjf+i6onU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nmvUYNz3ONMuK2pG4a893R+elit1FD5m6kh1P896luOy5uwOzX8kZDrGQVNTyTnnR y7BpXGhUNhVO3ImibjUZ5DjhYqCIiysJx7NyXrRg81gThR+FA2gBV4nH/pF8reKv8R QpblgoYkzh14gnlr9uVsQSycwqV9qR1vObIsOYXmq0Am9Be7u2valoMpvILoY61i11 14q6uz9e+OCzNzf8iCyxuZhQPFm1siJ/XEnkV2+PQYaA7lZjgU7RnSOZyNhX4YnZzb yfU2TwaeBdyr9INR4b/3GgBl2kpLFdSMn2/fAf9eswgvQOuCvXlYSPiLqMu1djtWZa zuw2r5+F3YLhQ== Date: Tue, 23 Jul 2024 13:24:39 -0600 From: Rob Herring To: Mateusz Majewski Cc: linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Bartlomiej Zolnierkiewicz , Krzysztof Kozlowski , "Rafael J. Wysocki" , Daniel Lezcano , Zhang Rui , Lukasz Luba , Conor Dooley , Alim Akhtar Subject: Re: [PATCH 6/6] dt-bindings: thermal: samsung,exynos: remove outdated information on trip point count Message-ID: <20240723192439.GA986360-robh@kernel.org> References: <20240723141715.374786-1-m.majewski2@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240723141715.374786-1-m.majewski2@samsung.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240723_122441_780814_A34D6D96 X-CRM114-Status: GOOD ( 15.54 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 23, 2024 at 04:17:14PM +0200, Mateusz Majewski wrote: > Hi :) > > > > + temperature thresholds. The trip points will be set dynamically in > > > + runtime, which means there is no limit on the number of trip points. > > > > How can the hardware change how many trip points it supports? > > Would just removing the whole "The trip points..." sentence be ok? I see > how it is more confusing than helpful. If the old text had nothing to do with the h/w, then I suppose so. I would have assumed the h/w supports some number of thresholds causing some action whether an interrupt or some sort of shutdown. Rob