<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/drivers/platform/x86/Kconfig, branch master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/drivers/platform/x86/Kconfig?h=master</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/drivers/platform/x86/Kconfig?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2022-09-09T19:58:16Z</updated>
<entry>
<title>platform/x86: Battery charge mode in toshiba_acpi (sysfs)</title>
<updated>2022-09-09T19:58:16Z</updated>
<author>
<name>Arvid Norlander</name>
<email>lkml@vorpal.se</email>
</author>
<published>2022-09-02T18:00:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=8ef5db9eb084f6212345a7b09355c78ce05f71e2'/>
<id>urn:sha1:8ef5db9eb084f6212345a7b09355c78ce05f71e2</id>
<content type='text'>
This commit adds the ACPI battery hook which in turns adds the sysfs
entries.

Because the Toshiba laptops only support two modes (eco or normal), which
in testing correspond to 80% and 100% we simply round to the nearest
possible level when set.

It is possible that Toshiba laptops other than the Z830 has different set
points for the charging. If so, a quirk table could be introduced in the
future for this. For now, assume that all laptops that support this feature
work the same way.

Tested on a Toshiba Satellite Z830.

Signed-off-by: Arvid Norlander &lt;lkml@vorpal.se&gt;
Link: https://lore.kernel.org/r/20220902180037.1728546-3-lkml@vorpal.se
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: toshiba_acpi: Add fan RPM reading (hwmon interface)</title>
<updated>2022-09-09T19:58:15Z</updated>
<author>
<name>Arvid Norlander</name>
<email>lkml@vorpal.se</email>
</author>
<published>2022-09-02T17:40:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=c727ba4cd95a12d8e43b02963d3ba4daddbd100c'/>
<id>urn:sha1:c727ba4cd95a12d8e43b02963d3ba4daddbd100c</id>
<content type='text'>
This expands on the previous commit, exporting the fan RPM via hwmon.

This will look something like the following when using the "sensors"
command from lm_sensors:

toshiba_acpi_sensors-acpi-0
Adapter: ACPI interface
fan1:           0 RPM

Signed-off-by: Arvid Norlander &lt;lkml@vorpal.se&gt;
Acked-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Link: https://lore.kernel.org/r/20220902174018.1720029-3-lkml@vorpal.se
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: nvidia-wmi-ec-backlight: Use acpi_video_get_backlight_type()</title>
<updated>2022-09-03T10:17:26Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-08-17T12:37:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=8d0ca287fd8cdc8110f5e441ec14874158f32a0f'/>
<id>urn:sha1:8d0ca287fd8cdc8110f5e441ec14874158f32a0f</id>
<content type='text'>
Add an acpi_video_get_backlight_type() == acpi_backlight_nvidia_wmi_ec
check. This will make nvidia-wmi-ec-backlight properly honor the user
selecting a different backlight driver through the acpi_backlight=...
kernel commandline option.

Since the auto-detect code check for nvidia-wmi-ec-backlight in
drivers/acpi/video_detect.c already checks that the WMI advertised
brightness-source is the embedded controller, this new check makes it
unnecessary for nvidia_wmi_ec_backlight_probe() to check this itself.

Suggested-by: Daniel Dadap &lt;ddadap@nvidia.com&gt;
Reviewed-by: Daniel Dadap &lt;ddadap@nvidia.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: p2sb: Move out of X86_PLATFORM_DEVICES dependency</title>
<updated>2022-08-01T14:26:38Z</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2022-07-18T14:53:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=42d0d4232ac1620c38a73bd133bf9927c9bc3ac4'/>
<id>urn:sha1:42d0d4232ac1620c38a73bd133bf9927c9bc3ac4</id>
<content type='text'>
The P2SB library is used for various drivers, including server
platforms. That's why the dependency on X86_PLATFORM_DEVICES
seems superfluous.

Reported-by: kernel test robot &lt;lkp@intel.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Link: https://lore.kernel.org/r/20220718145328.14374-1-andriy.shevchenko@linux.intel.com
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: asus-wmi: Add mic-mute LED classdev support</title>
<updated>2022-07-14T20:02:57Z</updated>
<author>
<name>PaddyKP_Yao</name>
<email>PaddyKP_Yao@asus.com</email>
</author>
<published>2022-07-11T11:51:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=b644c95598adfe2b968e97daee3a890dd2fda84d'/>
<id>urn:sha1:b644c95598adfe2b968e97daee3a890dd2fda84d</id>
<content type='text'>
In some new ASUS devices, hotkey Fn+F13 is used for mic mute. If mic-mute
LED is present by checking WMI ASUS_WMI_DEVID_MICMUTE_LED, we will add a
mic-mute LED classdev, asus::micmute, in the asus-wmi driver to control
it. The binding of mic-mute LED controls will be swithched with LED
trigger.

Signed-off-by: PaddyKP_Yao &lt;PaddyKP_Yao@asus.com&gt;
Link: https://lore.kernel.org/r/20220711115125.2072508-1-PaddyKP_Yao@asus.com
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: panasonic-laptop: filter out duplicate volume up/down/mute keypresses</title>
<updated>2022-06-28T19:45:40Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-06-24T11:23:39Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=5e24e1eca1f2a3aed924e44606134a9381c3ccb9'/>
<id>urn:sha1:5e24e1eca1f2a3aed924e44606134a9381c3ccb9</id>
<content type='text'>
On some Panasonic models the volume up/down/mute keypresses get
reported both through the Panasonic ACPI HKEY interface as well as
through the atkbd device.

Filter out the atkbd scan-codes for these to avoid reporting presses
twice.

Note normally we would leave the filtering of these to userspace by mapping
the scan-codes to KEY_UNKNOWN through /lib/udev/hwdb.d/60-keyboard.hwdb.
However in this case that would cause regressions since we were filtering
the Panasonic ACPI HKEY events before, so filter these in the kernel.

Fixes: ed83c9171829 ("platform/x86: panasonic-laptop: Resolve hotkey double trigger bug")
Reported-and-tested-by: Stefan Seyfried &lt;seife+kernel@b1-systems.com&gt;
Reported-and-tested-by: Kenneth Chan &lt;kenneth.t.chan@gmail.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20220624112340.10130-7-hdegoede@redhat.com
</content>
</entry>
<entry>
<title>platform/x86: panasonic-laptop: don't report duplicate brightness key-presses</title>
<updated>2022-06-28T19:45:38Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-06-24T11:23:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=027f88453dbf34cafce1c31e93c216665cdd71d2'/>
<id>urn:sha1:027f88453dbf34cafce1c31e93c216665cdd71d2</id>
<content type='text'>
The brightness key-presses might also get reported by the ACPI video bus,
check for this and in this case don't report the presses to avoid reporting
2 presses for a single key-press.

Fixes: ed83c9171829 ("platform/x86: panasonic-laptop: Resolve hotkey double trigger bug")
Reported-and-tested-by: Stefan Seyfried &lt;seife+kernel@b1-systems.com&gt;
Reported-and-tested-by: Kenneth Chan &lt;kenneth.t.chan@gmail.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20220624112340.10130-6-hdegoede@redhat.com
</content>
</entry>
<entry>
<title>platform/x86: acer_wmi: Cleanup Kconfig selects</title>
<updated>2022-06-27T07:37:49Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-06-20T14:56:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=349da8ee726a19c5034145199985bbf78a1e933d'/>
<id>urn:sha1:349da8ee726a19c5034145199985bbf78a1e933d</id>
<content type='text'>
ACER_WMI already depends on ACPI_WMI which depends on ACPI
so the "depends on ACPI" is unnecessary.

And since ACER_WMI already depends on ACPI adding an "if ACPI"
to the ACPI_VIDEO select is nonsense.

While at it also group all the selects together.

Reviewed-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Link: https://lore.kernel.org/r/20220620145628.5882-1-hdegoede@redhat.com
</content>
</entry>
<entry>
<title>platform/x86: Move AMD platform drivers to separate directory</title>
<updated>2022-06-22T09:57:55Z</updated>
<author>
<name>Shyam Sundar S K</name>
<email>Shyam-sundar.S-k@amd.com</email>
</author>
<published>2022-06-08T19:32:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=ef233eafe5adc54ddc39a1b6cc483dddc744bf97'/>
<id>urn:sha1:ef233eafe5adc54ddc39a1b6cc483dddc744bf97</id>
<content type='text'>
Currently, AMD supported platform drivers are grouped under generic "x86"
folder structure. Move the current drivers (amd-pmc and amd_hsmp) to a
separate directory. This would also mean the newer driver submissions to
pdx86 subsystem in the future will also land in AMD specific directory.

Reviewed-by: Naveen Krishna Chatradhi &lt;NaveenKrishna.Chatradhi@amd.com&gt;
Tested-by: Suma Hegde &lt;suma.hegde@amd.com&gt;
Signed-off-by: Shyam Sundar S K &lt;Shyam-sundar.S-k@amd.com&gt;
Link: https://lore.kernel.org/r/20220608193212.2827257-1-Shyam-sundar.S-k@amd.com
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: Drop the PMC_ATOM Kconfig option</title>
<updated>2022-06-12T12:41:22Z</updated>
<author>
<name>Hans de Goede</name>
<email>hdegoede@redhat.com</email>
</author>
<published>2022-05-03T14:02:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=3cd8cc98d63492f6f69edd4486c9bd1fe29f91c3'/>
<id>urn:sha1:3cd8cc98d63492f6f69edd4486c9bd1fe29f91c3</id>
<content type='text'>
The def_bool y PMC_ATOM Kconfig option provides a couple of symbols used
by the code enabled by the X86_INTEL_LPSS option and it registers some
clocks. These clocks are only registered on Bay Trail, Cherry Trail and
Brasswell Intel SoCs and kernels targeting these SoCs must always have
the X86_INTEL_LPSS option enabled otherwise many things will not work.

Building the PMC_ATOM code on kernels which are not targeting the
mentioned SoCs and which do not have the X86_INTEL_LPSS enabled is
not useful.

This means that we can simplify things by replacing the PMC_ATOM Kconfig
option in Makefiles with X86_INTEL_LPSS and then drop the option.

Cc: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Acked-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Acked-by: Stephen Boyd &lt;sboyd@kernel.org&gt;
Link: https://lore.kernel.org/r/20220503140207.101218-2-hdegoede@redhat.com
</content>
</entry>
</feed>
