<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/platform/x86/dell, branch linux-5.14.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.14.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.14.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2021-09-30T08:12:59Z</updated>
<entry>
<title>platform/x86: dell: fix DELL_WMI_PRIVACY dependencies &amp; build error</title>
<updated>2021-09-30T08:12:59Z</updated>
<author>
<name>Randy Dunlap</name>
</author>
<published>2021-09-18T04:48:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d12feda3daf7af64168ffde39b8e394cde0dd48f'/>
<id>urn:sha1:d12feda3daf7af64168ffde39b8e394cde0dd48f</id>
<content type='text'>
[ Upstream commit 5b72dafaca73b33416c82457ae615e6f2022e901 ]

When DELL_WMI=y, DELL_WMI_PRIVACY=y, and LEDS_TRIGGER_AUDIO=m, there
is a linker error since the LEDS trigger code is built as a loadable
module. This happens because DELL_WMI_PRIVACY is a bool that depends
on a tristate (LEDS_TRIGGER_AUDIO=m), which can be dangerous.

ld: drivers/platform/x86/dell/dell-wmi-privacy.o: in function `dell_privacy_wmi_probe':
dell-wmi-privacy.c:(.text+0x3df): undefined reference to `ledtrig_audio_get'

Fixes: 8af9fa37b8a3 ("platform/x86: dell-privacy: Add support for Dell hardware privacy")
Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Cc: Perry Yuan &lt;Perry.Yuan@dell.com&gt;
Cc: Dell.Client.Kernel@dell.com
Cc: platform-driver-x86@vger.kernel.org
Cc: Hans de Goede &lt;hdegoede@redhat.com&gt;
Cc: Mark Gross &lt;mgross@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20210918044829.19222-1-rdunlap@infradead.org
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>platform/x86: dell-smbios-wmi: Add missing kfree in error-exit from run_smbios_call</title>
<updated>2021-09-18T11:43:33Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2021-08-26T14:08:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=45d69a44c1e3079ca01dbc2f33fe8a0ca287f2fc'/>
<id>urn:sha1:45d69a44c1e3079ca01dbc2f33fe8a0ca287f2fc</id>
<content type='text'>
[ Upstream commit 0487d4fc42d7f31a56cfd9e2237f9ebd889e6112 ]

As pointed out be Kees Cook if we return -EIO because the
obj-&gt;type != ACPI_TYPE_BUFFER, then we must kfree the
output buffer before the return.

Fixes: 1a258e670434 ("platform/x86: dell-smbios-wmi: Add new WMI dispatcher driver")
Reported-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Link: https://lore.kernel.org/r/20210826140822.71198-1-hdegoede@redhat.com
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'driver-core-5.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core</title>
<updated>2021-07-05T20:51:41Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2021-07-05T20:51:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5c13f1fdef9fed65b95c3c5f343d22c425ac1d7'/>
<id>urn:sha1:f5c13f1fdef9fed65b95c3c5f343d22c425ac1d7</id>
<content type='text'>
Pull driver core changes from Greg KH:
 "Here is the small set of driver core and debugfs updates for 5.14-rc1.

  Included in here are:

   - debugfs api cleanups (touched some drivers)

   - devres updates

   - tiny driver core updates and tweaks

  Nothing major in here at all, and all have been in linux-next for a
  while with no reported issues"

* tag 'driver-core-5.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (27 commits)
  docs: ABI: testing: sysfs-firmware-memmap: add some memmap types.
  devres: Enable trace events
  devres: No need to call remove_nodes() when there none present
  devres: Use list_for_each_safe_from() in remove_nodes()
  devres: Make locking straight forward in release_nodes()
  kernfs: move revalidate to be near lookup
  drivers/base: Constify static attribute_group structs
  firmware_loader: remove unneeded 'comma' macro
  devcoredump: remove contact information
  driver core: Drop helper devm_platform_ioremap_resource_wc()
  component: Rename 'dev' to 'parent'
  component: Drop 'dev' argument to component_match_realloc()
  device property: Don't check for NULL twice in the loops
  driver core: auxiliary bus: Fix typo in the docs
  drivers/base/node.c: make CACHE_ATTR define static DEVICE_ATTR_RO
  debugfs: remove return value of debugfs_create_ulong()
  debugfs: remove return value of debugfs_create_bool()
  scsi: snic: debugfs: remove local storage of debugfs files
  b43: don't save dentries for debugfs
  b43legacy: don't save dentries for debugfs
  ...
</content>
</entry>
<entry>
<title>platform/x86: dell-wmi-sysman: Change user experience when Admin/System Password is modified</title>
<updated>2021-06-28T09:53:24Z</updated>
<author>
<name>Prasanth KSR</name>
</author>
<published>2021-06-28T08:49:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0e695c3f7f66c66e0a1da90cc5378198a656d494'/>
<id>urn:sha1:0e695c3f7f66c66e0a1da90cc5378198a656d494</id>
<content type='text'>
Whenever user has changed an Admin/System Password using the sysfs,
then we are automatically copying the new password to existing
password field.

Co-developed-by: Divya Bharathi &lt;divya.bharathi@dell.com&gt;
Signed-off-by: Divya Bharathi &lt;divya.bharathi@dell.com&gt;
Signed-off-by: Prasanth KSR &lt;prasanth.ksr@dell.com&gt;
Link: https://lore.kernel.org/r/20210628084906.4233-1-prasanth.ksr@dell.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: Remove "default n" entries</title>
<updated>2021-06-22T09:05:08Z</updated>
<author>
<name>Andy Shevchenko</name>
</author>
<published>2021-06-18T12:55:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3ece696c1acaa2ecac2e55143fc0c3ac413369c0'/>
<id>urn:sha1:3ece696c1acaa2ecac2e55143fc0c3ac413369c0</id>
<content type='text'>
Linus already once did that for PDx86, don't repeat our mistakes.
TL;DR: 'n' *is* the default 'default'.

Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20210618125516.53510-1-andriy.shevchenko@linux.intel.com
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: dell-wmi-sysman/think-lmi: Make fw_attr_class global static</title>
<updated>2021-06-16T15:47:55Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2021-06-09T14:59:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cb58c277ff1a35432cd84a6cc9768c60ce4c2cad'/>
<id>urn:sha1:cb58c277ff1a35432cd84a6cc9768c60ce4c2cad</id>
<content type='text'>
The dell-wmi-sysman and think-lmi kernel modules both have a global
struct class *fw_attr_class variable, leading to the following compile
errors when both are builtin:

ld: drivers/platform/x86/think-lmi.o:(.bss+0x0): multiple definition of `fw_attr_class'; drivers/platform/x86/dell/dell-wmi-sysman/sysman.o:(.bss+0x0): first defined here

In both cases the variable is only used in the file where it is declared.
Make both declarations static to avoid the linker error.

Cc: Mark Pearson &lt;markpearson@lenovo.com&gt;
Cc: Dell.Client.Kernel@dell.com
Reported-by: Nathan Chancellor &lt;nathan@kernel.org&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Link: https://lore.kernel.org/r/20210609145952.113393-1-hdegoede@redhat.com
</content>
</entry>
<entry>
<title>platform/x86: dell-wmi-sysman: Use firmware_attributes_class helper</title>
<updated>2021-06-16T15:47:52Z</updated>
<author>
<name>Mark Pearson</name>
</author>
<published>2021-05-30T22:31:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8a1c379c5a03281295c436faf21b0e4716e5b8a8'/>
<id>urn:sha1:8a1c379c5a03281295c436faf21b0e4716e5b8a8</id>
<content type='text'>
Update Dell WMI sysman driver to use newly implemented helper module.

Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Mark Pearson &lt;markpearson@lenovo.com&gt;
Link: https://lore.kernel.org/r/20210530223111.25929-2-markpearson@lenovo.com
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: dell-privacy: Add support for Dell hardware privacy</title>
<updated>2021-06-16T15:47:51Z</updated>
<author>
<name>Perry Yuan</name>
</author>
<published>2021-05-06T11:56:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8af9fa37b8a3637832cbf8fdd9bd828bd5f0de66'/>
<id>urn:sha1:8af9fa37b8a3637832cbf8fdd9bd828bd5f0de66</id>
<content type='text'>
add support for Dell privacy driver for the Dell units equipped
hardware privacy design, which protect users privacy of audio and
camera from hardware level. Once the audio or camera privacy mode
activated, any applications will not get any audio or video stream
when user pressed ctrl+F4 hotkey, audio privacy mode will be
enabled, micmute led will be also changed accordingly
The micmute led is fully controlled by hardware &amp; EC(embedded controller)
and camera mute hotkey is Ctrl+F9. Currently design only emits
SW_CAMERA_LENS_COVER event while the camera lens shutter will be
changed by EC &amp; HW(hardware) control

*The flow is like this:
1) User presses key. HW does stuff with this key (timeout timer is started)
2) WMI event is emitted from BIOS to kernel
3) WMI event is received by dell-privacy
4) KEY_MICMUTE emitted from dell-privacy
5) Userland picks up key and modifies kcontrol for SW mute
6) Codec kernel driver catches and calls ledtrig_audio_set
7) dell-privacy notifies EC, the timeout is cancelled and the HW mute
   is activated. If the EC is not notified then the HW mic mute will
   activate when the timeout triggers, just a bit later than with the
   active ack.

Signed-off-by: Perry Yuan &lt;perry_yuan@dell.com&gt;
Link: https://lore.kernel.org/r/20210506115605.1504-1-Perry_Yuan@Dell.com
[hdegoede@redhat.com: Rework Kconfig/Makefile bits + other small fixups]
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: dell-wmi: Rename dell-wmi.c to dell-wmi-base.c</title>
<updated>2021-06-16T15:47:51Z</updated>
<author>
<name>Hans de Goede</name>
</author>
<published>2021-05-18T09:47:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8bf388a0a0fe257dd7be9db0352b5b71b4e9138a'/>
<id>urn:sha1:8bf388a0a0fe257dd7be9db0352b5b71b4e9138a</id>
<content type='text'>
Rename dell-wmi.c to dell-wmi-base.c, so that we can have other
dell-wmi-foo.c files which can be added to dell-wmi.ko as "plugins"
controlled by separate boolean Kconfig options.

Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>platform/x86: dcdbas: drop unneeded assignment in host_control_smi()</title>
<updated>2021-06-16T15:47:49Z</updated>
<author>
<name>Yang Li</name>
</author>
<published>2021-05-12T08:57:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e48af75dc7f3059c5a18d7176913457eef5765ad'/>
<id>urn:sha1:e48af75dc7f3059c5a18d7176913457eef5765ad</id>
<content type='text'>
Making '==' operation with ESM_STATUS_CMD_UNSUCCESSFUL directly
after calling the function inb() is more efficient, so assignment
to 'cmd_status' is redundant.

Eliminate the following clang_analyzer warning:
drivers/platform/x86/dell/dcdbas.c:397:11: warning: Although the value
stored to 'cmd_status' is used in the enclosing expression, the value
is never actually read from 'cmd_status'

No functional change.

Reported-by: Abaci Robot &lt;abaci@linux.alibaba.com&gt;
Signed-off-by: Yang Li &lt;yang.lee@linux.alibaba.com&gt;
Link: https://lore.kernel.org/r/1620809825-84105-1-git-send-email-yang.lee@linux.alibaba.com
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
</feed>
