From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"markgross@kernel.org" <markgross@kernel.org>,
"Mark Pearson" <markpearson@lenovo.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] platform/x86: think-lmi: Add possible_values for ThinkStation
Date: Sat, 18 Mar 2023 20:08:58 -0400 [thread overview]
Message-ID: <aa2f353f-6da5-4ec2-8a83-bffe310bd7b0@app.fastmail.com> (raw)
In-Reply-To: <e56512fa-b738-44f5-9dc4-57d46c994afd@t-8ch.de>
On Sat, Mar 18, 2023, at 7:52 PM, Thomas Weißschuh wrote:
> On Sat, Mar 18, 2023 at 01:53:33PM -0400, Mark Pearson wrote:
>> Thanks Thomas
>>
>> On Sat, Mar 18, 2023, at 12:35 PM, Thomas Weißschuh wrote:
>> > Hi Mark,
>> >
>> > please also CC linux-kernel@vger.kernel.org and previous reviewers.
>> >
>> > On Fri, Mar 17, 2023 at 11:46:34AM -0400, Mark Pearson wrote:
>> >> -static struct kobj_attribute attr_current_val = __ATTR_RW_MODE(current_value, 0600);
>> >> +static ssize_t type_show(struct kobject *kobj, struct kobj_attribute *attr,
>> >> + char *buf)
>> >> +{
>> >> + struct tlmi_attr_setting *setting = to_tlmi_attr_setting(kobj);
>> >> +
>> >> + if (setting->possible_values) {
>> >> + /* Figure out what setting type is as BIOS does not return this */
>> >> + if (strchr(setting->possible_values, ','))
>> >> + return sysfs_emit(buf, "enumeration\n");
>> >> + }
>> >> + /* Anything else is going to be a string */
>> >> + return sysfs_emit(buf, "string\n");
>> >> +}
>> >
>> > This patch seems to introduce a lot of churn, is it intentional?
>> Yes(ish). It got cleaned up as the functions were in a weird order when I introduced the is_visible. The actual changes are very small - but it did make it look messier than it really is.
>> Is this a big concern? I know it makes the review a bit more painful and my apologies for that.
>
> Not a big concern. The shuffling around could be done in a dedicated
> patch that explicitly only moves code around.
>
>> >> @@ -1440,6 +1451,25 @@ static int tlmi_analyze(void)
>> >> if (ret || !setting->possible_values)
>> >> pr_info("Error retrieving possible values for %d : %s\n",
>> >> i, setting->display_name);
>> >> + } else {
>> >> + /*
>> >> + * Older Thinkstations don't support the bios_selections API.
>> >> + * Instead they store this as a [Optional:Option1,Option2] section of the
>> >> + * name string.
>> >> + * Try and pull that out if it's available.
>> >> + */
>> >> + char *item, *optstart, *optend;
>> >> +
>> >> + if (!tlmi_setting(setting->index, &item, LENOVO_BIOS_SETTING_GUID)) {
>> >> + optstart = strstr(item, "[Optional:");
>> >> + if (optstart) {
>> >> + optstart += strlen("[Optional:");
>> >> + optend = strstr(optstart, "]");
>> >> + if (optend)
>> >> + setting->possible_values =
>> >> + kstrndup(optstart, optend - optstart, GFP_KERNEL);
>> >> + }
>> >> + }
>> >
>> > The patch now does two things:
>> > 1) Hide the sysfs attributes if the value is not available
>> > 2) Extract the value from the description
>> >
>> > Maybe it could be split in two?
>> Sure. I did contemplate that and then ultimately decided it was all from the same intent so left it. But I can split.
>
> Would look nicer to me, but it's only one opinion.
I have worked through this and it is nicer. Next version will be split (and I unwound some of the code re-org too).
I'm going to hold off a couple of days before pushing the changes for review in case there are other pieces of feedback.
Mark
next prev parent reply other threads:[~2023-03-19 0:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:46 [PATCH v3 1/3] platform/x86: think-lmi: add missing type attribute Mark Pearson
2023-03-17 15:46 ` [PATCH v3 2/3] platform/x86: think-lmi: Add possible_values for ThinkStation Mark Pearson
2023-03-18 16:35 ` Thomas Weißschuh
2023-03-18 17:53 ` Mark Pearson
2023-03-18 23:52 ` Thomas Weißschuh
2023-03-19 0:08 ` Mark Pearson [this message]
2023-03-19 9:34 ` Hans de Goede
2023-03-18 17:59 ` Mark Pearson
2023-03-19 0:01 ` Thomas Weißschuh
2023-03-19 0:04 ` Mark Pearson
2023-03-17 15:46 ` [PATCH v3 3/3] platform/x86: think-lmi: use correct possible_values delimters Mark Pearson
2023-03-18 14:37 ` Barnabás Pőcze
2023-03-18 17:55 ` Mark Pearson
2023-03-18 16:39 ` Thomas Weißschuh
2023-03-18 18:06 ` Mark Pearson
2023-03-19 0:11 ` Thomas Weißschuh
2023-03-19 0:18 ` Mark Pearson
2023-03-20 0:52 ` [PATCH v3 1/3] platform/x86: think-lmi: add missing type attribute Limonciello, Mario
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=aa2f353f-6da5-4ec2-8a83-bffe310bd7b0@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=hdegoede@redhat.com \
--cc=markgross@kernel.org \
--cc=markpearson@lenovo.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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;
as well as URLs for NNTP newsgroup(s).