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 B54F9C43334 for ; Wed, 29 Jun 2022 23:00:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230463AbiF2XAB (ORCPT ); Wed, 29 Jun 2022 19:00:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230504AbiF2W7p (ORCPT ); Wed, 29 Jun 2022 18:59:45 -0400 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D726640A2C for ; Wed, 29 Jun 2022 15:58:48 -0700 (PDT) Received: by mail-pl1-x64a.google.com with SMTP id j5-20020a170902da8500b0016b90578019so3076462plx.5 for ; Wed, 29 Jun 2022 15:58:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:message-id:mime-version:subject:from:to:cc; bh=8z7eHNzBfwIuJwCaqp0hLyBEJakQJmDKDOySk1lfElA=; b=eUbZyr9mx264NFAW9qP8q5MAEgRHqfK3anwe0Dc6IZP2ewEvLqCfm5XeD3SqBPuHRs Z3DFo/8B71PWjvM7Sjd7EV6J4Ri36PXB8WjTA36Ijc2QEkc7patrc5xTB/g8L0UBAFqT eJU2mtgFdwsWAiV/MeqVvTFqX2q/ZiC+XX0ynNKA11nahSlv7rgGITwOL6spBMbdKbsZ h8v7EbauDRv+lffCvbNiJLm0YluRrrCyxahEIw5qTil54hs193V3pJTWXEkLWBdUSHW+ w66B6USScOGYDqWNzX1qVAX3OZFPTNJ5XZFxCOUZ2sNQJVugTYXrtAbACF5c70mnpmP0 kBmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:mime-version:subject:from:to:cc; bh=8z7eHNzBfwIuJwCaqp0hLyBEJakQJmDKDOySk1lfElA=; b=SouNk2/0Ad5MYVUtYzYV8u3rtoaurP6Bt0W7nfDbdVjcMIGSXqI36GY95iZXwaVgDm 5Snqqt7+hTs5QqGlt07uIhIaJL9iVt2IqeM7XM7p5URabmdzHhZw3RRaNixdQtt4rHTP HH6oxlMtkIPlEQdje3ArrvxFue2o788x78i33c4NKva/h64eLDO7uh0hvsVl/pD9NGrN 2Vf1Gfj1dfn0Rejepj0Jdh2YchIdWnH8PMJnbpYCCGQv+U/U9gmXrYCB65HnktpjUGdd I1GhbcP8tPg4JAonHrFrwTn9TTJKGQp3gihXjRvfAfftzTAObfX7Mq/+ux7j8iqTWu9O ks6Q== X-Gm-Message-State: AJIora9vs8It3/Dva/yTbfxCGN+a2hskW9pCaqSCbeuLOfZ2j4Z8DAjc X9PpBlRfcxYliAa66kvowBnyOf/+FXRbEBEYJZs= X-Google-Smtp-Source: AGRyM1sxAWgSTfU8h6zzPTVjW8sbDkhdxhC4OHr5/BcukTSsR5JtIFMQdh0mUZ7VmE/cPm/SDJkgsIXcnorKQHBuIuY= X-Received: from willmcvicker.c.googlers.com ([fda3:e722:ac3:cc00:24:72f4:c0a8:2dd0]) (user=willmcvicker job=sendgmr) by 2002:a17:90a:249:b0:1e0:a8a3:3c6c with SMTP id t9-20020a17090a024900b001e0a8a33c6cmr315pje.0.1656543528054; Wed, 29 Jun 2022 15:58:48 -0700 (PDT) Date: Wed, 29 Jun 2022 22:58:40 +0000 Message-Id: <20220629225843.332453-1-willmcvicker@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.37.0.rc0.161.g10f37bed90-goog Subject: [PATCH 4.19 v1 0/2] Fixes for thermal hwmon registration From: Will McVicker To: stable@vger.kernel.org, Jean Delvare , Guenter Roeck , Zhang Rui , Eduardo Valentin , Daniel Lezcano Cc: kernel-team@android.com, Will McVicker , linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All, These two patches fix issues with thermal hwmon registration on 4.19. The upstream commit ddaefa209c4a ("hwmon: Make chip parameter for with_info API mandatory") forces the chip parameter to be mandatory which breaks thermal subsystem devices from probing. These fixes were pulled into 5.4, but missed from 4.19. I have verified them on Pixel 5 with the 4.19 kernel. Thanks, Will Guenter Roeck (2): hwmon: Introduce hwmon_device_register_for_thermal thermal/drivers/thermal_hwmon: Use hwmon_device_register_for_thermal() drivers/hwmon/hwmon.c | 25 +++++++++++++++++++++++++ drivers/thermal/thermal_hwmon.c | 4 ++-- include/linux/hwmon.h | 3 +++ 3 files changed, 30 insertions(+), 2 deletions(-) -- 2.37.0.rc0.161.g10f37bed90-goog