From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Derek John Clark" <derekjohn.clark@gmail.com>,
"Joaquín Ignacio Aramendía" <samsagax@gmail.com>,
"Jean Delvare" <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] hwmon: (oxp-sensors) Cache state of PWM enable mode
Date: Fri, 27 Dec 2024 00:13:40 +0100 [thread overview]
Message-ID: <28b7a9b2-a2ea-473e-8a17-2b987169b669@math.uni-bielefeld.de> (raw)
In-Reply-To: <94e512e0-8105-4123-b9be-8a9805f7cfca@roeck-us.net>
On 12/26/24 22:05, Guenter Roeck wrote:
> On Thu, Dec 26, 2024 at 06:00:19PM +0100, tjakobi@math.uni-bielefeld.de wrote:
>> From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
>>
>> The driver is in full control of the enable mode, so we
>> don't need to read it from HW every single time.
>>
>
> That is not a reason for adding that much additional code.
> What is the problem that is being solved, and why is it worth that much
> additional code ?
I don't think it's that much additional code, but anyway: Reading from
EC is not exactly fast, and I want this value cached for another reason.
It turns out that some devices use a different scaling for the PWM value
depending on whether the PWM is controlled automatically by the EC, or
manually through the driver. And I don't want to do an additional EC
read to figure this out, if I can avoid it.
With best wishes,
Tobias
>
> Plus, again, all those runtime feature checks in attribute handling
> code are completely wrong.
>
> Guenter
next prev parent reply other threads:[~2024-12-26 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 17:00 [PATCH 0/4] hwmon: (oxp-sensors) Cleanup device type handling tjakobi
2024-12-26 17:00 ` [PATCH 1/4] hwmon: (oxp-sensors) Separate logic from device-specific data tjakobi
2024-12-26 20:54 ` Guenter Roeck
2024-12-26 22:59 ` Tobias Jakobi
2025-01-07 17:33 ` Guenter Roeck
2024-12-26 21:04 ` Guenter Roeck
2024-12-26 23:05 ` Tobias Jakobi
2025-01-07 17:34 ` Guenter Roeck
2024-12-26 17:00 ` [PATCH 2/4] hwmon: (oxp-sensors) Fix typos in documentation tjakobi
2024-12-26 17:00 ` [PATCH 3/4] hwmon: (oxp-sensors) Fix wording in code comment tjakobi
2024-12-26 20:52 ` Guenter Roeck
2024-12-26 22:56 ` Tobias Jakobi
2025-01-07 17:24 ` Guenter Roeck
2024-12-26 17:00 ` [PATCH 4/4] hwmon: (oxp-sensors) Cache state of PWM enable mode tjakobi
2024-12-26 21:05 ` Guenter Roeck
2024-12-26 23:13 ` Tobias Jakobi [this message]
2025-01-07 17:43 ` 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=28b7a9b2-a2ea-473e-8a17-2b987169b669@math.uni-bielefeld.de \
--to=tjakobi@math.uni-bielefeld.de \
--cc=derekjohn.clark@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=samsagax@gmail.com \
/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®