Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp298663ybx; Thu, 31 Oct 2019 20:49:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqxqEkAhxM5oEDyaELpz5vnB2x3Ai1C1fQkKbwQwn80+SeueGtDAqjFAzP1WVIc4mooXLW+K X-Received: by 2002:a05:6402:19:: with SMTP id d25mr10244264edu.186.1572580196411; Thu, 31 Oct 2019 20:49:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572580196; cv=none; d=google.com; s=arc-20160816; b=ga/jjQrrBSbjvRA0T7/wm0yp26tS5C8x7Fy6SF7JEMytD7369DXGKBaVRqLFGWkI7h Tckniiuz43/kZhmPE+hoQuOfPYpsMOPbsyNsM4hs51798pUO1exw9f9ajOn8PpP2XrbS 7eL1vBrDwbVRgLxEA1lWDqCZpSo/MacBnQQkLsmuV2/340q8gcVOyt6M7K1CLj9EsBAe Xaf0D5RkAWc56Z8FJOcKXFRPTxFwg1I+pY8PcPOknYOWFR4Fhjn92eq2stGPJCXACg6N cGbAllLEP++PAu4PVJsYINNoK+0bIbh/6/KX8EREhw99RY97YAOAKU4I4lUJslzikteU eAzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=2aKKAbR7LSxTgSQC6+zc//x+NNPcrArey5OEFPW8knU=; b=CCkFcV2RB8LHu1/vvW6D1jLCYiNFwhvxjpgqXr5IYR8GWgJZgB3qGeaFuMyfqqZbPF ARDb8wkNLqt6y1TTuRzlBdHzDaPTY9g8wSsUm5Dv9cXrhE+M+ZVxRMiQgP88qHB4buzW GatTv/VK4uc4Ri9zdtkc/o3iFmx9+yxIOJKGmXbbVpAeb6MfyiuH2fcnxPdBE6ueRCA2 hPIbBbpG8dhfDyxC79zxhASL/lRWBgp5iVLgIowQRhIjD0IXPQBiVuWsTzWWUBeTwV46 3W85ZiGJsMfvGc/g0iSIxE2YYry7nff4ENPnbEgw/Y+yJyi2v56+IGEopgSyVVl80bZG JWJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vTGvqh2b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f13si5836257edl.170.2019.10.31.20.49.33; Thu, 31 Oct 2019 20:49:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vTGvqh2b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729446AbfKADE7 (ORCPT + 99 others); Thu, 31 Oct 2019 23:04:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:54614 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726793AbfKADE7 (ORCPT ); Thu, 31 Oct 2019 23:04:59 -0400 Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 68C6A217D9; Fri, 1 Nov 2019 03:04:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572577498; bh=nU6uqOVFaCsulLB14w3V7HfkrQ0IMKZJP3c9WxF8K20=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=vTGvqh2b7quzmstG195V56puCkgWoM1VlheFQG+9axMEtSr28lRYaSTp9SsxJPjPP y3lQgR7VIvU4oOJ/5ZJZEtlnD4vvARiJgO/6v/sknd967OhCt7MEer9GFtUQS2PCsT oimyKhk9SY9UrQdaGwrnODbFMGvG9VExlwqKLxJ8= Received: by mail-wr1-f50.google.com with SMTP id l10so8381405wrb.2; Thu, 31 Oct 2019 20:04:58 -0700 (PDT) X-Gm-Message-State: APjAAAX3zofpHyg4xToctFH3YZ8SeCHas7rJrnFh5Ov43fkwi1Ayct7b 7hOYJSvo0Af6awISVutaEU53ORFuKp3RIzFESjk= X-Received: by 2002:a5d:6203:: with SMTP id y3mr8698187wru.142.1572577496753; Thu, 31 Oct 2019 20:04:56 -0700 (PDT) MIME-Version: 1.0 References: <20191030163807.17817-1-wens@kernel.org> <91017889-2ae7-d467-eed3-6d3b2bb130b9@gmx.net> In-Reply-To: <91017889-2ae7-d467-eed3-6d3b2bb130b9@gmx.net> From: Chen-Yu Tsai Date: Fri, 1 Nov 2019 11:04:45 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] thermal: brcmstb: enable hwmon To: Stefan Wahren Cc: Chen-Yu Tsai , Markus Mayer , Florian Fainelli , Zhang Rui , Eduardo Valentin , Daniel Lezcano , Amit Kucheria , "open list:BROADCOM BCM281XX..." , linux-kernel , linux-arm-kernel , "open list:THERMAL" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 31, 2019 at 9:09 PM Stefan Wahren wrote: > > Hi Chen-Yu, > > Am 30.10.19 um 17:38 schrieb Chen-Yu Tsai: > > From: Chen-Yu Tsai > > > > By defaul of-based thermal driver do not have hwmon entries registered. > > > > Do this explicitly so users can use standard hwmon interfaces and tools > > to read the temperature. > > > > This is based on similar changes for bcm2835_thermal in commit > > d56c19d07e0b ("thermal: bcm2835: enable hwmon explicitly"). > > > > Signed-off-by: Chen-Yu Tsai > > --- > > > > This patch was only compile tested. A similar patch [1] was submitted to > > the downstream kernel, which I did build and actually run on a Raspberry > > Pi 4. > > just a note: from my understanding [2] the brcmstb_thermal isn't the > right driver for BCM2711. Please consider the current downstream > solution for BCM2711 support as a quick hack to avoid writing a new > thermal driver. But must confess that i didn't test Florian's recent > changes yet. Thanks for the tip. I only saw the thread after posting this patch. ChenYu > Regards > Stefan > > [2] - > https://github.com/raspberrypi/linux/issues/3101#issuecomment-527554223 > > > > > This one for mainline is much simpler, as it does not need to deal with > > the error path or device removal, due to the use of devres. > > > > [1] https://github.com/raspberrypi/linux/pull/3307 > > > > --- > > drivers/thermal/broadcom/brcmstb_thermal.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) >