platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Nikita Kravets" <teackot@gmail.com>,
	"Barnabás Pőcze" <pobrn@protonmail.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86: Add new msi-ec driver
Date: Wed, 1 Mar 2023 16:19:54 +0100	[thread overview]
Message-ID: <03e01393-f9ab-30d2-ba0b-e2f5022c43e9@redhat.com> (raw)
In-Reply-To: <CAPXvF06Gr_Dh9NukoTmnpd+s4uNJaVOvXjmkhQ7NVOnOie1xjg@mail.gmail.com>

Hi,

Before diving into a full review of the driver I thought
it would be good to first catch up with the email thread sofar.

I agree with everything discussed so far. One clarifying remark
below:

On 2/15/23 22:27, Nikita Kravets wrote:

<snip>

>> This will start poking the embedded controller when the module is loaded, regardless of the platform. I am not sure that is desirable.
> 
> It only reads though, can it cause any harm?

I have seen cases where some weird (i2c) hw reacts to
reads as if they are writes.

But since this is using the standardized ACPI EC access
routines I believe that doing reads should generally
speaking be safe.

Also it seems that atm the module must always be loaded
manually ?

I don't see any MODULE_ALIAS or MODULE_DEVICE_TABLE entries
in the driver to make it auto-load.

I think this should get a dmi_system_id tables with known
MSI DMI_SYS_VENDOR() matches in there + a
MODULE_DEVICE_TABLE() pointing to the dmi_system_id table
to have the driver auto-load on MSI systems.

I think what we should do here is:

1. Get the module in the mainline kernel
2. Do a blogpost asking MSI laptop users to test
3. Assuming testing does not show any regressions / issues
   (it will likely show lots of unsupported fw versions)
   add the MODULE_DEVICE_TABLE().

Regards,

Hans



  reply	other threads:[~2023-03-01 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 13:25 [PATCH] platform/x86: Add new msi-ec driver Nikita Kravets
2023-02-14 15:03 ` Barnabás Pőcze
2023-02-15 21:27   ` Nikita Kravets
2023-03-01 15:19     ` Hans de Goede [this message]
2023-03-01 17:50 ` Hans de Goede
2023-03-01 20:17   ` Nikita Kravets
2023-03-02  8:56     ` Hans de Goede
2023-03-02 12:45       ` Nikita Kravets
2023-03-02 14:05         ` 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=03e01393-f9ab-30d2-ba0b-e2f5022c43e9@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.com \
    --cc=teackot@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;
as well as URLs for NNTP newsgroup(s).