From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: jdelvare@suse.com, linux@roeck-us.net,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/4] hwmon: (sch56xx) Automatically load on supported hardware
Date: Mon, 31 Jan 2022 10:45:45 +0100 [thread overview]
Message-ID: <f5a96b96-d9e2-2381-3673-632ae85c8b24@redhat.com> (raw)
In-Reply-To: <20220131093756.8075-1-W_Armin@gmx.de>
Hi Armin,
On 1/31/22 10:37, Armin Wolf wrote:
> The hardware monitoring solutions supported by the sch5627 and
> sch5636 drivers are Fujitsu-specific.
> After some online searching, i found out that the solution used
> with the SCH5627 is called "Antiope" by Fujitsu, just like the
> "Theseus" solution inside the SCH5636.
> I also found out that "Antiope" and "Theseus" are listed as
> DMI onboard devices on supported Fujitsu devices, so the
> sch56xx_common module can be loaded automatically an check
> for the DMI devices. However some devices like the Esprimo C700
> have both devices, so after verifying that at least one onboard
> device is present, sch56xx_common still has to detect which chip
> is present.
> This is safe however if at least one device is present.
>
> Tested on a Fujitsu Esprimo P720.
>
> Armin Wolf (4):
> hwmon: (sch56xx) Autoload modules on platform device creation
> hwmon: (sch56xx-common) Add automatic module loading on supported
> devices
> hwmon: (sch56xx-common) Replace msleep() with usleep_range()
> hwmon: (sch56xx-common) Replace WDOG_ACTIVE with WDOG_HW_RUNNING
Not sure why you did a resend? I received the original just fine ?
With that said the entire series looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
for the series.
Regards,
Hans
>
> drivers/hwmon/sch5627.c | 9 +++++++
> drivers/hwmon/sch5636.c | 9 +++++++
> drivers/hwmon/sch56xx-common.c | 44 ++++++++++++++++++++++++++++++----
> 3 files changed, 58 insertions(+), 4 deletions(-)
>
> --
> 2.30.2
>
prev parent reply other threads:[~2022-01-31 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 9:37 Armin Wolf
2022-01-31 9:37 ` [PATCH RESEND 1/4] hwmon: (sch56xx) Autoload modules on platform device creation Armin Wolf
2022-01-31 9:37 ` [PATCH RESEND 2/4] hwmon: (sch56xx-common) Add automatic module loading on supported devices Armin Wolf
2022-01-31 9:37 ` [PATCH RESEND 3/4] hwmon: (sch56xx-common) Replace msleep() with usleep_range() Armin Wolf
2022-01-31 9:37 ` [PATCH RESEND 4/4] hwmon: (sch56xx-common) Replace WDOG_ACTIVE with WDOG_HW_RUNNING Armin Wolf
2022-01-31 9:45 ` Hans de Goede [this message]
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=f5a96b96-d9e2-2381-3673-632ae85c8b24@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--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
all inboxes | Powered by JetHome®