From: Jeremy Gebben <jgebben@sweptlaser.com>
To: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] hwmon: (lm85) add LM96000 high freqency pwm support
Date: Mon, 4 Feb 2019 13:19:02 -0700 [thread overview]
Message-ID: <20190204201906.8859-1-jgebben@sweptlaser.com> (raw)
Hi,
This patch set 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).
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
Changes since v2:
- add lm96000 type instead of continuing to use lm85
Jeremy Gebben (4):
hwmon: (lm85) remove freq_map size hardcodes
dt-bindings: Add LM96000 as a trivial device
hwmon: (lm85) support the LM96000
hwmon: (lm85) add support for LM96000 high frequencies
.../devicetree/bindings/trivial-devices.yaml | 2 +
Documentation/hwmon/lm85 | 9 +++-
drivers/hwmon/lm85.c | 43 +++++++++++++------
3 files changed, 41 insertions(+), 13 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-04 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 20:19 Jeremy Gebben [this message]
2019-02-04 20:19 ` [PATCH v3 1/4] hwmon: (lm85) remove freq_map size hardcodes Jeremy Gebben
2019-02-04 20:19 ` [PATCH v3 2/4] dt-bindings: Add LM96000 as a trivial device Jeremy Gebben
2019-02-04 20:27 ` Rob Herring
2019-02-04 20:19 ` [PATCH v3 3/4] hwmon: (lm85) support the LM96000 Jeremy Gebben
2019-02-04 20:19 ` [PATCH v3 4/4] hwmon: (lm85) add support for LM96000 high frequencies Jeremy Gebben
2019-02-04 22:45 ` [PATCH v3 0/4] hwmon: (lm85) add LM96000 high freqency pwm support Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190204201906.8859-1-jgebben@sweptlaser.com \
--to=jgebben@sweptlaser.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).