From: Guenter Roeck <linux@roeck-us.net>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org
Subject: Re: WIP: [PATCH] hwmon: (w83627ehf) convert to with_info interface
Date: Tue, 19 Nov 2019 13:21:08 -0800 [thread overview]
Message-ID: <20191119212108.GA16985@roeck-us.net> (raw)
In-Reply-To: <20191119181822.GC26171@gallifrey>
On Tue, Nov 19, 2019 at 06:18:22PM +0000, Dr. David Alan Gilbert wrote:
>
> Hi Jean, Guenter,
> I'm part way through converting w83627ehf to use the devm_hwmon_device_register_with_info
> interface and had some questions I'd appreciate the answer to. My WIP
> code is attached below.
>
> a) In the existing driver, all the pseudo files are showing up as:
> /sys/devices/platform/w83627ehf.656/blah_input
> with the rework:
> /sys/devices/platform/w83627ehf.656/hwmon/hwmon1/
>
> my reading is that the reworked one is correct?
> Although I guess the change is a pain for people with paths
> in tools.
>
No one should have absolute path names like the above in their tools.
So far none of the driver conversions caused trouble, so hopefully
we should be fine.
> b) The device has an intrusion0_alarm & intrusion1_alarm
> that seems pretty common looking in drivers/hwmon - some other
> devices have a intrustion%d_beep. Does it make sense to add
> a new hwmon_intrusion type to hwmon_sensor_types ?
>
Yes, we should add hwmon_intrusion to hwmon_sensor_types, with _alarm
and _beep as supported attributes.
> c) The device has a bunch more pwm variants:
> pwm2_max_output, pwm2_start_output, pwm2_step_output, pwm2_stop_output,
> pwm2_stop_time, pwm2_target, pwm2_tolerance
>
> for each/some of it's outputs. What's the right thing to
> do there? Add them all to hwmon_pwm_attr_templates ?
> (Unfortunately it looks like everyone has fun with their own
> pwm settings).
>
We'll have to keep sysfs files for those for the time being,
unless there are some which are officially listed in
Documentation/hwmon/sysfs-interface.rst.
> For reference, I seem to have a w83667hg on an ASRock P55M Pro.
>
> The current status is that 'reading' seems to work (from what I can tell
> but not looked at the PWM), and I've not converted the writers yet.
>
Good start. I would suggest to run your patch through checkpatch.
It will tell you, for example, that S_IRUGO et al ran out of favor,
and that you are supposed to use octals instead.
Thanks,
Guenter
next prev parent reply other threads:[~2019-11-19 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 18:18 WIP: [PATCH] hwmon: (w83627ehf) convert to with_info interface Dr. David Alan Gilbert
2019-11-19 21:21 ` Guenter Roeck [this message]
2019-11-20 17:26 ` Dr. David Alan Gilbert
2019-11-20 18:47 ` 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=20191119212108.GA16985@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@treblig.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