From: Wolfram Sang <wsa@the-dreams.de>
To: Viktor Krasnov <vkrasnov@dev.rtsoft.ru>
Cc: jdelvare@suse.com, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, jarkko.nikula@linux.intel.com,
echerkasov@dev.rtsoft.ru, Michael.Brunner@kontron.com
Subject: Re: [PATCH v2] i2c: i2c-scmi: add a MS HID
Date: Sun, 16 Apr 2017 21:50:13 +0200 [thread overview]
Message-ID: <20170416195013.oldw47c4novlyxwh@ninjato> (raw)
In-Reply-To: <1491322707-2991-1-git-send-email-vkrasnov@dev.rtsoft.ru>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
On Tue, Apr 04, 2017 at 07:18:27PM +0300, Viktor Krasnov wrote:
> From: Edgar Cherkasov <echerkasov@dev.rtsoft.ru>
>
> Description of the problem:
> - i2c-scmi driver contains only two identifiers "SMBUS01" and "SMBUSIBM";
> - the fist HID (SMBUS01) is clearly defined in "SMBus Control Method
> Interface Specification, version 1.0": "Each device must specify
> 'SMBUS01' as its _HID and use a unique _UID value";
> - unfortunately, BIOS vendors (like AMI) seem to ignore this requirement
> and implement "SMB0001" HID instead of "SMBUS01";
> - I speculate that they do this because only "SMB0001" is hard coded in
> Windows SMBus driver produced by Microsoft.
>
> This leads to following situation:
> - SMBus works out of box in Windows but not in Linux;
> - board vendors are forced to add correct "SMBUS01" HID to BIOS to make
> SMBus work in Linux. Moreover the same board vendors complain that
> tools (3-rd party ASL compiler) do not like the "SMBUS01" identifier
> and produce errors. So they need to constantly patch the compiler for
> each new version of BIOS.
>
> As it is very unlikely that BIOS vendors implement a correct HID in
> future, I would propose to consider whether it is possible to work around
> the problem by adding MS HID to the Linux i2c-scmi driver.
>
> v2: move the definition of the new HID to the driver itself.
>
> Signed-off-by: Edgar Cherkasov <echerkasov@dev.rtsoft.ru>
> Signed-off-by: Michael Brunner <Michael.Brunner@kontron.com>
> Acked-by: Viktor Krasnov <vkrasnov@dev.rtsoft.ru>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-04-16 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 16:18 [PATCH v2] i2c: i2c-scmi: add a MS HID Viktor Krasnov
2017-04-05 12:59 ` Jean Delvare
2017-04-06 8:03 ` Mika Westerberg
2017-04-16 19:50 ` Wolfram Sang [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=20170416195013.oldw47c4novlyxwh@ninjato \
--to=wsa@the-dreams.de \
--cc=Michael.Brunner@kontron.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=echerkasov@dev.rtsoft.ru \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=vkrasnov@dev.rtsoft.ru \
/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).