linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mika.westerberg@linux.intel.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support
Date: Wed, 23 Dec 2015 12:09:59 +0200	[thread overview]
Message-ID: <20151223100959.GK1758@lahna.fi.intel.com> (raw)
In-Reply-To: <BLUPR12MB0451770284D7788418640F699DE60@BLUPR12MB0451.namprd12.prod.outlook.com>

On Wed, Dec 23, 2015 at 10:02:04AM +0000, Zheng, Ivan wrote:
> Why/how can Linux driver make use of such non-ACPI defined methods?

What do you mean exactly?

I added support for these (well, SSCN and FMCN) because I found out that
some vendors include such methods with their BIOS implementation.
Windows driver uses these if present and so do we.

  reply	other threads:[~2015-12-23 10:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 21:19 [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support Loc Ho
2015-12-10 21:19 ` [PATCH v2 1/2] acpi:apd: " Loc Ho
2015-12-11  1:13   ` Ken Xue
2015-12-10 21:19 ` [PATCH v2 2/2] i2c:dw: " Loc Ho
2015-12-15  0:53 ` [PATCH v2 0/2] " Suravee Suthikulanit
2015-12-15 13:27   ` Mika Westerberg
2015-12-15 14:52     ` Suravee Suthikulpanit
2015-12-15 14:59       ` Mika Westerberg
2015-12-15 19:20         ` Loc Ho
2015-12-16  9:04           ` Mika Westerberg
2015-12-16 12:53             ` Jarkko Nikula
2015-12-23  9:34         ` Ken Xue
2015-12-23  9:52           ` Mika Westerberg
2015-12-23  9:59             ` Ken Xue
2015-12-23 10:17               ` Mika Westerberg
2015-12-23 10:02             ` Zheng, Ivan
2015-12-23 10:09               ` Mika Westerberg [this message]
2015-12-23 11:24                 ` Zheng, Ivan
2015-12-23 11:40                   ` Mika Westerberg
2016-01-04  9:09           ` Ben Dooks
2016-01-03  0:54 ` Rafael J. Wysocki
2016-01-04  6:23   ` Loc Ho

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=20151223100959.GK1758@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).