From patchwork Thu Jan 31 22:06:14 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jeremy Gebben X-Patchwork-Id: 10791531 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 829BA14E1 for ; Thu, 31 Jan 2019 22:07:01 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 7A7913101E for ; Thu, 31 Jan 2019 22:07:01 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 6BC37314B1; Thu, 31 Jan 2019 22:07:01 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 5F1B83101E for ; Thu, 31 Jan 2019 22:06:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729020AbfAaWG5 (ORCPT ); Thu, 31 Jan 2019 17:06:57 -0500 Received: from mail-it1-f196.google.com ([209.85.166.196]:36692 "EHLO mail-it1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729005AbfAaWG4 (ORCPT ); Thu, 31 Jan 2019 17:06:56 -0500 Received: by mail-it1-f196.google.com with SMTP id c9so6885466itj.1 for ; Thu, 31 Jan 2019 14:06:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sweptlaser-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id; bh=s//WKIUtaIH0wRpbyXK/xy0gdxoHenTpSnbPv7jjHjg=; b=S10wpksu3gKB0l02Esx08e6f2VmxjRuauKQ7Fd/NHM6PFR/8Fy1KSMSCVS9iQcQliM /zOqM6Ko9b718S1B2/cKCD8kG2f8j1Exosub/+Y5EIThvE4MNnhi3zc1GSkZdDpWnEga zMm3PrSiE9NIv+jM0LeotMKh5vQRMEGcurvLzK9EoUqd9pduS1AWZcdsrBeH4TjDFglt 7Fht+ZNYxt0Tp/xqZgRhfmsN1sKGBjoeUU4ikJRbpq630SIis5cfBn57Z3Be/QKldn2z 8nvZ6gIJYJ6+6adeOqzYXWjogzFbRv59Mjbl7d2k2G2e8GgHoZjY8b/d+uMYr175VqUy xp3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id; bh=s//WKIUtaIH0wRpbyXK/xy0gdxoHenTpSnbPv7jjHjg=; b=FQVFGxbswS0UTEOCt69zuxLcDNl+/L5RcBnvtqsT2iHFQHCiDkRdTQEHPP43CnT7Kr IowxHxOD1PyatzMGD7BrJvWpXsFVW0WAKUiHBLO6vQFXwDpcLOJeM9ACSV6xdXvwht5P XHNTC5Am3e7F1oT9efr95VEJwc2GPT4BrsBjZ3SO/jkQtiDO/H2sWOVhNE3RxEh+R7R5 GgncfZ0xIP5EhyNyYIcP1z7DDKlsjLuR1xKu20ycuk0lT7keMewdvSMZ9PAS4sp1m5f9 oYqfexTGUTXA/Dw2bELhLO+1MiDndy2fIEi/myGYDRpD04OgPQkyxATnmS42bW7PFqDh APDA== X-Gm-Message-State: AJcUukfUgTFd2OxZwLMre2FEHgdazjOipToK/lF8pId7XwWH4AzUSL2P 8EyT5hsvu8w6iHAJkmkjczBUCw== X-Google-Smtp-Source: ALg8bN7xap+KRRH4zb+lS0wNlj/xrMMxrEG+riUmUos0/0BDwGvGrgitRFxo6k2fkdlluAoJ8BDGLA== X-Received: by 2002:a02:570d:: with SMTP id u13mr22402974jaa.71.1548972415953; Thu, 31 Jan 2019 14:06:55 -0800 (PST) Received: from yngvi.hq.sweptlaser.com ([63.147.146.226]) by smtp.googlemail.com with ESMTPSA id l186sm286439itl.22.2019.01.31.14.06.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 14:06:55 -0800 (PST) From: Jeremy Gebben To: Jean Delvare , Guenter Roeck , linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/3] hwmon: (lm85) add LM96000 high freqency pwm support Date: Thu, 31 Jan 2019 15:06:14 -0700 Message-Id: <20190131220617.15223-1-jgebben@sweptlaser.com> X-Mailer: git-send-email 2.17.1 Sender: linux-hwmon-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hwmon@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Hi, This patch adds support for the PWM frequencies from 22.5 to 30 kHz available on the LM96000. It looks like this chip has been supported for a long time, but wasn't mentioned in the docs (which I have updated). Also, it has been using the generic 'lm85' prefix, which I have not changed to avoid breaking userspace or device tree files. AFAICT, lm85_detect() will only return 'lm85' for LM96000 chips, so it doesn't look like you can get a bare 'lm85' prefix with any other chips. I stumbled on to a 10 year old thread discussing a patch which looks like an early attempt to add support for this chip, which may be of interest: https://lm-sensors.lm-sensors.narkive.com/1SIwaMDT/patch-hwmon-lm96000-support Thanks for reviewing, Jeremy Changes since v1: - replace freq_map_mask with freq_map_size Jeremy Gebben (3): hwmon: (lm85) remove freq_map size hardcodes hwmon: (lm85) Document the LM96000 as supported hwmon: (lm85) add support for LM96000 high frequencies Documentation/hwmon/lm85 | 9 ++++++++- drivers/hwmon/lm85.c | 32 ++++++++++++++++++++++---------- 2 files changed, 30 insertions(+), 11 deletions(-)