From: Hans de Goede <hdegoede@redhat.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
Divya Bharathi <divya27392@gmail.com>,
"dvhart@infradead.org" <dvhart@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"Bharathi, Divya" <Divya.Bharathi@Dell.com>,
"Ksr, Prasanth" <Prasanth.Ksr@dell.com>
Subject: Re: [PATCH] Introduce support for Systems Management Driver over WMI for Dell Systems
Date: Mon, 14 Sep 2020 10:57:53 +0200 [thread overview]
Message-ID: <25c9e901-ed28-eb87-bd89-652c3710b62b@redhat.com> (raw)
In-Reply-To: <c5a6e340-66ec-e03b-a9a8-9c61b9f388d5@redhat.com>
Hi,
On 9/14/20 10:45 AM, Hans de Goede wrote:
<snip>
>>>> + lower_bound: A file that can be read to obtain the lower
>>>> + bound value of the <attr>
>>>> +
>>>> + modifier: A file that can be read to obtain attribute-level
>>>> + dependency rule which has to be met to configure <attr>
>>>> +
>>>> + scalar_increment: A file that can be read to obtain the
>>>> + resolution of the incremental value this attribute accepts.
>>>> +
>>>> + upper_bound: A file that can be read to obtain the upper
>>>> + bound value of the <attr>
>>>
>>> Are these integers or also possibly floats? I guess possibly also floats, right?
>>> Then at a minimum this should specify which decimal-separator is used (I assume
>>> we will go with the usual '.' as decimal separator).
>>
>> In practice they're integers, but I don't see why they couldn't be floats.
>
> Hmm, that is a bit hand-wavy, for an userspace ABI we really need to define
> this clearly. Either it is integers (which is fine), or it is floats and we need
> to define a decimal-separator as part of the ABI.
>
> Note the reason why I started wondering about this in the first place is the
> scalar_increment attribute. I think that can use some clarification too.
p.s.
I just realized that the lower_ / upper_bound attributes would be
better if they were renamed to min_value and max_value then everyone
will immediately understand what they are without even needing to
consult the docs.
Regards,
Hans
next prev parent reply other threads:[~2020-09-14 8:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 14:31 Divya Bharathi
2020-08-08 18:37 ` Limonciello, Mario
2020-08-10 8:27 ` Andy Shevchenko
2020-09-01 9:49 ` Hans de Goede
2020-09-01 14:17 ` Limonciello, Mario
2020-09-14 9:13 ` Hans de Goede
2020-09-14 9:13 ` Hans de Goede
2020-09-14 16:06 ` Limonciello, Mario
2020-09-17 10:11 ` Hans de Goede
2020-09-17 16:18 ` Limonciello, Mario
2020-09-21 10:02 ` Hans de Goede
2020-09-21 15:26 ` Limonciello, Mario
2020-09-22 8:57 ` Hans de Goede
2020-09-22 9:14 ` Hans de Goede
2020-09-22 18:02 ` Limonciello, Mario
2020-09-22 9:02 ` Hans de Goede
2020-09-01 10:09 ` Hans de Goede
2020-09-01 14:22 ` Limonciello, Mario
2020-09-14 8:45 ` Hans de Goede
2020-09-14 8:57 ` Hans de Goede [this message]
2020-09-01 11:41 ` Hans de Goede
2020-09-02 8:04 ` Andy Shevchenko
2020-09-03 14:27 ` Limonciello, Mario
2020-09-14 9:53 ` Hans de Goede
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=25c9e901-ed28-eb87-bd89-652c3710b62b@redhat.com \
--to=hdegoede@redhat.com \
--cc=Divya.Bharathi@Dell.com \
--cc=Mario.Limonciello@dell.com \
--cc=Prasanth.Ksr@dell.com \
--cc=divya27392@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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®