<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/platform/x86, branch linux-5.5.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.5.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.5.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-04-17T14:12:05Z</updated>
<entry>
<title>platform/x86: asus-wmi: Support laptops where the first battery is named BATT</title>
<updated>2020-04-17T14:12:05Z</updated>
<author>
<name>Kristian Klausen</name>
</author>
<published>2020-03-03T18:02:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ee5e0cc2414ce947778ba91171c492937278363a'/>
<id>urn:sha1:ee5e0cc2414ce947778ba91171c492937278363a</id>
<content type='text'>
commit 6b3586d45bba14f6912f37488090c37a3710e7b4 upstream.

The WMI method to set the charge threshold does not provide a
way to specific a battery, so we assume it is the first/primary
battery (by checking if the name is BAT0).
On some newer ASUS laptops (Zenbook UM431DA) though, the
primary/first battery isn't named BAT0 but BATT, so we need
to support that case.

Fixes: 7973353e92ee ("platform/x86: asus-wmi: Refactor charge threshold to use the battery hooking API")
Cc: stable@vger.kernel.org
Signed-off-by: Kristian Klausen &lt;kristian@klausen.dk&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: intel_int0002_vgpio: Use acpi_register_wakeup_handler()</title>
<updated>2020-04-13T11:16:39Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2020-04-03T15:48:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0cc7f888024376857715eef59509028aa4aa98a1'/>
<id>urn:sha1:0cc7f888024376857715eef59509028aa4aa98a1</id>
<content type='text'>
commit 767191db8220db29f78c031f4d27375173c336d5 upstream.

The Power Management Events (PMEs) the INT0002 driver listens for get
signalled by the Power Management Controller (PMC) using the same IRQ
as used for the ACPI SCI.

Since commit fdde0ff8590b ("ACPI: PM: s2idle: Prevent spurious SCIs from
waking up the system") the SCI triggering, without there being a wakeup
cause recognized by the ACPI sleep code, will no longer wakeup the system.

This breaks PMEs / wakeups signalled to the INT0002 driver, the system
never leaves the s2idle_loop() now.

Use acpi_register_wakeup_handler() to register a function which checks
the GPE0a_STS register for a PME and trigger a wakeup when a PME has
been signalled.

Fixes: fdde0ff8590b ("ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system")
Cc: 5.4+ &lt;stable@vger.kernel.org&gt; # 5.4+
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Acked-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: pmc_atom: Add Lex 2I385SW to critclk_systems DMI table</title>
<updated>2020-04-02T13:09:52Z</updated>
<author>
<name>Georg Müller</name>
</author>
<published>2020-02-03T20:11:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd13b06c4d299a318f235b60140c47d2a874ff62'/>
<id>urn:sha1:dd13b06c4d299a318f235b60140c47d2a874ff62</id>
<content type='text'>
commit 95b31e35239e5e1689e3d965d692a313c71bd8ab upstream.

The Lex 2I385SW board has two Intel I211 ethernet controllers. Without
this patch, only the first port is usable. The second port fails to
start with the following message:

    igb: probe of 0000:02:00.0 failed with error -2

Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
Tested-by: Georg Müller &lt;georgmueller@gmx.net&gt;
Signed-off-by: Georg Müller &lt;georgmueller@gmx.net&gt;
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: intel_mid_powerbtn: Take a copy of ddata</title>
<updated>2020-02-14T21:53:01Z</updated>
<author>
<name>Mika Westerberg</name>
</author>
<published>2020-01-22T16:05:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=08a36797bfdc08a3900ff628c1d1c60aac89a61c'/>
<id>urn:sha1:08a36797bfdc08a3900ff628c1d1c60aac89a61c</id>
<content type='text'>
commit 5e0c94d3aeeecc68c573033f08d9678fecf253bd upstream.

The driver gets driver_data from memory that is marked as const (which
is probably put to read-only memory) and it then modifies it. This
likely causes some sort of fault to happen.

Fix this by taking a copy of the structure.

Fixes: c94a8ff14de3 ("platform/x86: intel_mid_powerbtn: make mid_pb_ddata const")
Signed-off-by: Mika Westerberg &lt;mika.westerberg@linux.intel.com&gt;
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: intel_scu_ipc: Fix interrupt support</title>
<updated>2020-02-11T12:36:45Z</updated>
<author>
<name>Mika Westerberg</name>
</author>
<published>2020-01-22T16:28:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f49f1ea9433fa0bbec4c62d294daec28902f1293'/>
<id>urn:sha1:f49f1ea9433fa0bbec4c62d294daec28902f1293</id>
<content type='text'>
commit e48b72a568bbd641c91dad354138d3c17d03ee6f upstream.

Currently the driver has disabled interrupt support for Tangier but
actually interrupt works just fine if the command is not written twice
in a row. Also we need to ack the interrupt in the handler.

Signed-off-by: Mika Westerberg &lt;mika.westerberg@linux.intel.com&gt;
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: asus-wmi: Fix keyboard brightness cannot be set to 0</title>
<updated>2020-01-13T09:50:59Z</updated>
<author>
<name>Jian-Hong Pan</name>
</author>
<published>2019-12-30T08:30:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=176a7fca81c5090a7240664e3002c106d296bf31'/>
<id>urn:sha1:176a7fca81c5090a7240664e3002c106d296bf31</id>
<content type='text'>
Some of ASUS laptops like UX431FL keyboard backlight cannot be set to
brightness 0. According to ASUS' information, the brightness should be
0x80 ~ 0x83. This patch fixes it by following the logic.

Fixes: e9809c0b9670 ("asus-wmi: add keyboard backlight support")
Signed-off-by: Jian-Hong Pan &lt;jian-hong@endlessm.com&gt;
Reviewed-by: Daniel Drake &lt;drake@endlessm.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: intel_pmc_core: update Comet Lake platform driver</title>
<updated>2020-01-13T09:37:50Z</updated>
<author>
<name>Harry Pan</name>
</author>
<published>2020-01-06T09:57:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=515ff674bb9bf06186052e352c4587dab8defaf0'/>
<id>urn:sha1:515ff674bb9bf06186052e352c4587dab8defaf0</id>
<content type='text'>
Adding new CML CPU model ID into platform driver support list.

Signed-off-by: Harry Pan &lt;harry.pan@intel.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: GPD pocket fan: Allow somewhat lower/higher temperature limits</title>
<updated>2020-01-13T09:37:50Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2020-01-06T14:42:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3'/>
<id>urn:sha1:1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3</id>
<content type='text'>
Allow the user to configure the fan to turn on / speed-up at lower
thresholds then before (20 degrees Celcius as minimum instead of 40) and
likewise also allow the user to delay the fan speeding-up till the
temperature hits 90 degrees Celcius (was 70).

Cc: Jason Anderson &lt;jasona.594@gmail.com&gt;
Reported-by: Jason Anderson &lt;jasona.594@gmail.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: GPD pocket fan: Use default values when wrong modparams are given</title>
<updated>2020-01-13T09:37:50Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2020-01-06T14:42:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6ae01050e49f0080ae30575d9b45a6d4a3d7ee23'/>
<id>urn:sha1:6ae01050e49f0080ae30575d9b45a6d4a3d7ee23</id>
<content type='text'>
Use our default values when wrong module-parameters are given, instead of
refusing to load. Refusing to load leaves the fan at the BIOS default
setting, which is "Off". The CPU's thermal throttling should protect the
system from damage, but not-loading is really not the best fallback in this
case.

This commit fixes this by re-setting module-parameter values to their
defaults if they are out of range, instead of failing the probe with
-EINVAL.

Cc: stable@vger.kernel.org
Cc: Jason Anderson &lt;jasona.594@gmail.com&gt;
Reported-by: Jason Anderson &lt;jasona.594@gmail.com&gt;
Fixes: 594ce6db326e ("platform/x86: GPD pocket fan: Use a min-speed of 2 while charging")
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: intel-ips: Use the correct style for SPDX License Identifier</title>
<updated>2020-01-13T09:37:50Z</updated>
<author>
<name>Nishad Kamdar</name>
</author>
<published>2019-12-19T14:30:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dbff1e07b02d11fae04dd4b1954600baee9e94cc'/>
<id>urn:sha1:dbff1e07b02d11fae04dd4b1954600baee9e94cc</id>
<content type='text'>
This patch corrects the SPDX License Identifier style in
header files related to x86 Platform Specific Drivers.
For C header files Documentation/process/license-rules.rst
mandates C-like comments (opposed to C source files where
C++ style should be used).

Changes made by using a script provided by Joe Perches here:
https://lkml.org/lkml/2019/2/7/46.

Suggested-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: Nishad Kamdar &lt;nishadkamdar@gmail.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
</feed>
