From: Guenter Roeck <linux@roeck-us.net>
To: Daniel Matyas <daniel.matyas@analog.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Hwmon driver for MAX31827 temperature switch
Date: Wed, 26 Apr 2023 07:38:56 -0700 [thread overview]
Message-ID: <abe1301a-8bdf-3e5f-9e52-71f0f77d519b@roeck-us.net> (raw)
In-Reply-To: <20230426124049.258359-1-daniel.matyas@analog.com>
On 4/26/23 05:40, Daniel Matyas wrote:
> Removed of_match_table and kept only id_table. Removed other device id's
> from id_table (I have them only in the devicetree-binding).
>
Please explain. Without of_match_table, it is not possible to bind the driver
using devicetree data. What is the point of that ?
Guenter
> Added mutex protection where it was needed.
>
> Daniel Matyas (2):
> dt-bindings: hwmon: add MAX31827
> hwmon: max31827: add MAX31827 driver
>
> .../bindings/hwmon/adi,max31827.yaml | 54 +++
> Documentation/hwmon/index.rst | 1 +
> Documentation/hwmon/max31827.rst | 83 ++++
> MAINTAINERS | 9 +
> drivers/hwmon/Kconfig | 11 +
> drivers/hwmon/Makefile | 2 +-
> drivers/hwmon/max31827.c | 406 ++++++++++++++++++
> 7 files changed, 565 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/hwmon/adi,max31827.yaml
> create mode 100644 Documentation/hwmon/max31827.rst
> create mode 100644 drivers/hwmon/max31827.c
>
prev parent reply other threads:[~2023-04-26 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 12:40 Daniel Matyas
2023-04-26 12:40 ` [PATCH v3 1/2] dt-bindings: hwmon: add MAX31827 Daniel Matyas
2023-04-26 12:40 ` [PATCH v3 2/2] hwmon: max31827: add MAX31827 driver Daniel Matyas
2023-04-26 14:57 ` Guenter Roeck
2023-04-27 16:56 ` [PATCH v3 1/2] dt-bindings: hwmon: add MAX31827 Rob Herring
2023-04-26 14:38 ` Guenter Roeck [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=abe1301a-8bdf-3e5f-9e52-71f0f77d519b@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=daniel.matyas@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®