From: Slawomir Stepien <sst@poczta.fm>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, przemyslaw.cencner@nokia.com,
krzysztof.adamski@nokia.com, alexander.sverdlin@nokia.com
Subject: Re: [PATCH 0/8] Add support for ADT7481 in lm90
Date: Sun, 22 May 2022 16:52:45 +0200 [thread overview]
Message-ID: <YopOPSnafQi4n9Y+@t480s.localdomain> (raw)
In-Reply-To: <62a519ee-c909-bdb8-e686-084ffe8a8bcf@roeck-us.net>
On maj 20, 2022 09:01, Guenter Roeck wrote:
> On 5/20/22 06:45, Guenter Roeck wrote:
> > On 5/20/22 02:32, Slawomir Stepien wrote:
> > > From: Slawomir Stepien <slawomir.stepien@nokia.com>
> > >
> > > This patch series adds support for ADT7481 in lm90.c driver and extends the
> > > device-tree options for it.
> > >
> > > The ADT7481 is quite similar to MAX6696 (already supported in lm90) so a lot of
> > > code is reused.
> > >
> > > One major problem in fitting the ADT7481 in lm90.c is the chip detection.
> > > However it seems that the chip has been designed and produced with correct
> > > values at locations: 0xfe (manufactured id) and 0xff (chip id), but this is not
> > > documented in the datasheet.
> > >
> >
> > Before we go too far along this route, would you mind using my own patch series
> > as base to implement the devicetree changes ? I had prepared an extensive
> > patch series a while ago, adding not only support for ADT7481 but for
> > several other chips as well, I just never got around to sending it out.
> >
>
> I made my lm90 patch series available in branch hwmon-lm90 of
> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
>
> The patches in this series were module tested and tested on real hardware
> with the test scripts at git@github.com:groeck/module-tests.git;
> look for scripts/lm90-real.sh and scripts/lm90.sh.
I will test that out.
If I would be happy with that branch, should I rebase all my changes based on that branch and send
the patches to the lists?
--
Slawomir Stepien
next prev parent reply other threads:[~2022-05-22 14:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 9:32 [PATCH 0/8] Add support for ADT7481 in lm90 Slawomir Stepien
2022-05-20 9:32 ` [PATCH 1/8] dt-bindings: hwmon: " Slawomir Stepien
2022-05-20 10:08 ` Krzysztof Kozlowski
2022-05-20 9:32 ` [PATCH 2/8] dt-bindings: hwmon: Add 'extended-range-enable' property support " Slawomir Stepien
2022-05-20 10:09 ` Krzysztof Kozlowski
2022-05-20 10:57 ` Slawomir Stepien
2022-05-20 9:32 ` [PATCH 3/8] dt-bindings: hwmon: Allow specifying channels for lm90 Slawomir Stepien
2022-05-20 10:13 ` Krzysztof Kozlowski
2022-05-20 12:38 ` Slawomir Stepien
2022-05-20 12:47 ` Krzysztof Kozlowski
2022-05-20 13:23 ` Slawomir Stepien
2022-05-20 13:34 ` Krzysztof Kozlowski
2022-05-20 14:02 ` Guenter Roeck
2022-05-20 13:42 ` Guenter Roeck
2022-05-20 14:09 ` Krzysztof Kozlowski
2022-05-20 14:22 ` Guenter Roeck
2022-05-24 11:53 ` Slawomir Stepien
2022-05-24 12:17 ` Slawomir Stepien
2022-05-24 17:27 ` Slawomir Stepien
2022-05-24 17:59 ` Krzysztof Kozlowski
2022-05-25 7:07 ` Slawomir Stepien
2022-05-20 9:32 ` [PATCH 4/8] hwmon: (lm90) add support for ADT7481 Slawomir Stepien
2022-05-20 9:32 ` [PATCH 5/8] hwmon: (lm90) define maximum number of channels that are supported Slawomir Stepien
2022-05-21 2:36 ` Guenter Roeck
2022-05-22 14:59 ` Slawomir Stepien
2022-05-20 9:32 ` [PATCH 6/8] hwmon: (lm90) enable the extended temperature range Slawomir Stepien
2022-05-20 9:32 ` [PATCH 7/8] hwmon: (lm90) read the channel's label from device-tree Slawomir Stepien
2022-05-20 10:15 ` Krzysztof Kozlowski
2022-05-20 11:01 ` Slawomir Stepien
2022-05-20 11:41 ` Krzysztof Kozlowski
2022-05-20 9:32 ` [PATCH 8/8] hwmon: (lm90) read the channel's offset " Slawomir Stepien
2022-05-20 13:45 ` [PATCH 0/8] Add support for ADT7481 in lm90 Guenter Roeck
2022-05-20 16:01 ` Guenter Roeck
2022-05-22 14:52 ` Slawomir Stepien [this message]
2022-05-22 15:00 ` 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=YopOPSnafQi4n9Y+@t480s.localdomain \
--to=sst@poczta.fm \
--cc=alexander.sverdlin@nokia.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.adamski@nokia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=przemyslaw.cencner@nokia.com \
--cc=robh+dt@kernel.org \
/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