From: Paul Menzel <pmenzel@molgen.mpg.de> To: Guenter Roeck <linux@roeck-us.net> Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org, jdelvare@suse.com, corbet@lwn.net, Ban Feng <baneric926@gmail.com>, openbmc@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, DELPHINE_CHIU@wiwynn.com, naresh.solanki@9elements.com, billy_tsai@aspeedtech.com, kcfeng0@nuvoton.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, kwliu@nuvoton.com Subject: Re: [PATCH v4 3/3] hwmon: Driver for Nuvoton NCT7363Y Date: Wed, 28 Feb 2024 12:03:56 +0100 [thread overview] Message-ID: <e2b0b8e3-9b39-4621-9e43-d7de02286a27@molgen.mpg.de> (raw) In-Reply-To: <4b06d535-6739-47b5-ad1e-0ff94322620e@roeck-us.net> Dear Guenter, Am 28.02.24 um 10:03 schrieb Guenter Roeck: > On 2/27/24 23:57, Paul Menzel wrote: >> Am 27.02.24 um 01:56 schrieb baneric926@gmail.com: >>> From: Ban Feng <kcfeng0@nuvoton.com> >>> >>> NCT7363Y is an I2C based hardware monitoring chip from Nuvoton. >> >> Please reference the datasheet. > > Note that something like > > Datasheet: Available from Nuvoton upon request > > is quite common for hardware monitoring chips and acceptable. Yes, it would be nice to document it though. (And finally for vendors to just make them available for download.) >> Could you please give a high level description of the driver design? > > Can you be more specific ? I didn't have time yet to look into details, > but at first glance this looks like a standard hardware monitoring driver. > One could argue that the high level design of such drivers is described > in Documentation/hwmon/hwmon-kernel-api.rst. > > I don't usually ask for a additional design information for hwmon drivers > unless some chip interaction is unusual and needs to be explained, > and then I prefer to have it explained in the code. Given that, I am > quite curious and would like to understand what you are looking for. For a 10+ lines commit, in my opinion the commit message should say something about the implementation. Even it is just, as you wrote, a note, that it follows the standard design. Kind regards, Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Menzel <pmenzel@molgen.mpg.de> To: Guenter Roeck <linux@roeck-us.net> Cc: Ban Feng <baneric926@gmail.com>, jdelvare@suse.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, corbet@lwn.net, linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org, kcfeng0@nuvoton.com, kwliu@nuvoton.com, openbmc@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, DELPHINE_CHIU@wiwynn.com, naresh.solanki@9elements.com, billy_tsai@aspeedtech.com Subject: Re: [PATCH v4 3/3] hwmon: Driver for Nuvoton NCT7363Y Date: Wed, 28 Feb 2024 12:03:56 +0100 [thread overview] Message-ID: <e2b0b8e3-9b39-4621-9e43-d7de02286a27@molgen.mpg.de> (raw) In-Reply-To: <4b06d535-6739-47b5-ad1e-0ff94322620e@roeck-us.net> Dear Guenter, Am 28.02.24 um 10:03 schrieb Guenter Roeck: > On 2/27/24 23:57, Paul Menzel wrote: >> Am 27.02.24 um 01:56 schrieb baneric926@gmail.com: >>> From: Ban Feng <kcfeng0@nuvoton.com> >>> >>> NCT7363Y is an I2C based hardware monitoring chip from Nuvoton. >> >> Please reference the datasheet. > > Note that something like > > Datasheet: Available from Nuvoton upon request > > is quite common for hardware monitoring chips and acceptable. Yes, it would be nice to document it though. (And finally for vendors to just make them available for download.) >> Could you please give a high level description of the driver design? > > Can you be more specific ? I didn't have time yet to look into details, > but at first glance this looks like a standard hardware monitoring driver. > One could argue that the high level design of such drivers is described > in Documentation/hwmon/hwmon-kernel-api.rst. > > I don't usually ask for a additional design information for hwmon drivers > unless some chip interaction is unusual and needs to be explained, > and then I prefer to have it explained in the code. Given that, I am > quite curious and would like to understand what you are looking for. For a 10+ lines commit, in my opinion the commit message should say something about the implementation. Even it is just, as you wrote, a note, that it follows the standard design. Kind regards, Paul
next prev parent reply other threads:[~2024-02-28 11:05 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-27 0:56 [PATCH v4 0/3] hwmon: Driver for Nuvoton NCT7363Y baneric926 2024-02-27 0:56 ` baneric926 2024-02-27 0:56 ` [PATCH v4 1/3] dt-bindings: hwmon: fan: Add fan binding to schema baneric926 2024-02-27 0:56 ` baneric926 2024-03-05 0:22 ` Zev Weiss 2024-03-05 0:22 ` Zev Weiss 2024-03-05 0:41 ` Guenter Roeck 2024-03-05 0:41 ` Guenter Roeck 2024-03-05 0:49 ` Guenter Roeck 2024-03-05 0:49 ` Guenter Roeck 2024-03-07 7:41 ` Ban Feng 2024-03-07 7:41 ` Ban Feng 2024-03-07 18:53 ` Guenter Roeck 2024-03-07 18:53 ` Guenter Roeck 2024-03-18 0:58 ` Ban Feng 2024-03-18 0:58 ` Ban Feng 2024-02-27 0:56 ` [PATCH v4 2/3] dt-bindings: hwmon: Add NCT7363Y documentation baneric926 2024-02-27 0:56 ` baneric926 2024-02-28 7:30 ` Paul Menzel 2024-02-28 7:30 ` Paul Menzel 2024-03-06 7:56 ` Ban Feng 2024-03-06 7:56 ` Ban Feng 2024-02-27 0:56 ` [PATCH v4 3/3] hwmon: Driver for Nuvoton NCT7363Y baneric926 2024-02-27 0:56 ` baneric926 2024-02-28 7:57 ` Paul Menzel 2024-02-28 7:57 ` Paul Menzel 2024-02-28 9:03 ` Guenter Roeck 2024-02-28 9:03 ` Guenter Roeck 2024-02-28 11:03 ` Paul Menzel [this message] 2024-02-28 11:03 ` Paul Menzel 2024-02-28 16:03 ` Guenter Roeck 2024-02-28 16:03 ` Guenter Roeck 2024-02-28 16:25 ` Commit messages (was: [PATCH v4 3/3] hwmon: Driver for Nuvoton NCT7363Y) Paul Menzel 2024-02-28 16:25 ` Paul Menzel 2024-03-07 0:58 ` Ban Feng 2024-03-07 0:58 ` Ban Feng 2024-03-07 0:55 ` [PATCH v4 3/3] hwmon: Driver for Nuvoton NCT7363Y Ban Feng 2024-03-07 0:55 ` Ban Feng 2024-03-02 8:18 ` Zev Weiss 2024-03-02 8:18 ` Zev Weiss 2024-03-05 0:28 ` Zev Weiss 2024-03-05 0:28 ` Zev Weiss 2024-03-07 7:36 ` Ban Feng 2024-03-07 7:36 ` Ban Feng 2024-03-07 7:35 ` Ban Feng 2024-03-07 7:35 ` Ban Feng 2024-03-12 23:18 ` Zev Weiss 2024-03-12 23:18 ` Zev Weiss 2024-03-12 23:58 ` Guenter Roeck 2024-03-12 23:58 ` Guenter Roeck 2024-03-13 0:21 ` Zev Weiss 2024-03-13 0:21 ` Zev Weiss 2024-03-18 1:02 ` Ban Feng 2024-03-18 1:02 ` Ban Feng 2024-03-19 0:35 ` Zev Weiss 2024-03-19 0:35 ` Zev Weiss
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=e2b0b8e3-9b39-4621-9e43-d7de02286a27@molgen.mpg.de \ --to=pmenzel@molgen.mpg.de \ --cc=DELPHINE_CHIU@wiwynn.com \ --cc=baneric926@gmail.com \ --cc=billy_tsai@aspeedtech.com \ --cc=conor+dt@kernel.org \ --cc=corbet@lwn.net \ --cc=devicetree@vger.kernel.org \ --cc=jdelvare@suse.com \ --cc=kcfeng0@nuvoton.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=kwliu@nuvoton.com \ --cc=linux-doc@vger.kernel.org \ --cc=linux-hwmon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@roeck-us.net \ --cc=naresh.solanki@9elements.com \ --cc=openbmc@lists.ozlabs.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.