From: Hans de Goede <hdegoede@redhat.com>
To: Kelly Anderson <kelly@xilka.com>,
ike.pan@canonical.com, pobrn@protonmail.com,
mgross@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, markpearson@lenovo.com
Subject: Re: [PATCH v2] add platform support for Ideapad 5 Pro 16ACH6-82L5
Date: Tue, 28 Sep 2021 17:06:12 +0200 [thread overview]
Message-ID: <0f7f2c94-4144-0f74-d3f8-b675c92e10eb@redhat.com> (raw)
In-Reply-To: <11840239.O9o76ZdvQC@comer.internal>
Hi,
On 9/26/21 6:39 AM, Kelly Anderson wrote:
> V2 - Addressed issues brought up by Barnabás Pőcze.
>
> Adding support specifically for Ideapad 5 Pro 16ACH6-82L5 by adding a
> whitelist function that can validate notebooks for which dytc_version
> is less than 5, and seem to work fine at dytc_version 4. This code has
> been tested to work properly on the specified system.
>
> Signed-off-by: Kelly Anderson <kelly@xilka.com>
>
> drivers/platform/x86/ideapad-laptop.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
> index e7a1299e3776..fc54f6ab614f 100644
> --- a/drivers/platform/x86/ideapad-laptop.c
> +++ b/drivers/platform/x86/ideapad-laptop.c
> @@ -868,6 +868,18 @@ static void dytc_profile_refresh(struct ideapad_private *priv)
> }
> }
>
> +static const struct dmi_system_id ideapad_dytc_v4_whitelist_table[] = {
Documentation/process/coding-style.rst chapter 4 "Naming" says:
"""
For symbol names and documentation, avoid introducing new usage of
'master / slave' (or 'slave' independent of 'master') and 'blacklist /
whitelist'.
Recommended replacements for 'master / slave' are:
'{primary,main} / {secondary,replica,subordinate}'
'{initiator,requester} / {target,responder}'
'{controller,host} / {device,worker,proxy}'
'leader / follower'
'director / performer'
Recommended replacements for 'blacklist/whitelist' are:
'denylist / allowlist'
'blocklist / passlist'
"""
So I've done a s/whitelist/allow/ on your patch.
> + {
> + /* Ideapad 5 Pro 16ACH6 */
> + .ident = "LENOVO 82L5",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "82L5")
> + }
> + },
> + {}
> +};
> +
> static int ideapad_dytc_profile_init(struct ideapad_private *priv)
> {
> int err, dytc_version;
> @@ -882,12 +894,20 @@ static int ideapad_dytc_profile_init(struct ideapad_private *priv)
> return err;
>
> /* Check DYTC is enabled and supports mode setting */
> - if (!test_bit(DYTC_QUERY_ENABLE_BIT, &output))
> + if (!test_bit(DYTC_QUERY_ENABLE_BIT, &output)) {
> + dev_info(&priv->platform_device->dev, "DYTC_QUERY_ENABLE_BIT returned false\n");
> return -ENODEV;
> + }
>
> dytc_version = (output >> DYTC_QUERY_REV_BIT) & 0xF;
> - if (dytc_version < 5)
> - return -ENODEV;
> +
> + if (dytc_version < 5) {
> + if ( dytc_version < 4 || ! dmi_check_system(ideapad_dytc_v4_whitelist_table) ) {
There is a bunch of extra spaces here which go against the codingstyle, I've fixed this up
while applying this to my tree:
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> + dev_info(&priv->platform_device->dev,
> + "DYTC_VERSION is less than 4 or is not whitelisted: %d\n", dytc_version);
> + return -ENODEV;
> + }
> + }
>
> priv->dytc = kzalloc(sizeof(*priv->dytc), GFP_KERNEL);
> if (!priv->dytc)
>
prev parent reply other threads:[~2021-09-28 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 4:39 Kelly Anderson
2021-09-28 15:06 ` Hans de Goede [this message]
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=0f7f2c94-4144-0f74-d3f8-b675c92e10eb@redhat.com \
--to=hdegoede@redhat.com \
--cc=ike.pan@canonical.com \
--cc=kelly@xilka.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.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®