<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/platform, branch v5.1.10</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=v5.1.10</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=v5.1.10'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2019-06-15T09:53:03+00:00</updated>
<entry>
<title>platform/x86: intel_pmc_ipc: adding error handling</title>
<updated>2019-06-15T09:53:03+00:00</updated>
<author>
<name>Junxiao Chang</name>
<email>junxiao.chang@intel.com</email>
</author>
<published>2019-04-08T09:40:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=93e97bcfaa4bee62ec401ad7206ace9e8246d43a'/>
<id>urn:sha1:93e97bcfaa4bee62ec401ad7206ace9e8246d43a</id>
<content type='text'>
[ Upstream commit e61985d0550df8c2078310202aaad9b41049c36c ]

If punit or telemetry device initialization fails, pmc driver should
unregister and return failure.

This change is to fix a kernel panic when removing kernel module
intel_pmc_ipc.

Fixes: 48c1917088ba ("platform:x86: Add Intel telemetry platform device")
Signed-off-by: Junxiao Chang &lt;junxiao.chang@intel.com&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>platform/chrome: cros_ec_proto: check for NULL transfer function</title>
<updated>2019-06-15T09:53:01+00:00</updated>
<author>
<name>Enrico Granata</name>
<email>egranata@chromium.org</email>
</author>
<published>2019-04-03T22:40:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1f9dc1d54c1278f338444da24d0d43c61dbd5959'/>
<id>urn:sha1:1f9dc1d54c1278f338444da24d0d43c61dbd5959</id>
<content type='text'>
[ Upstream commit 94d4e7af14a1170e34cf082d92e4c02de9e9fb88 ]

As new transfer mechanisms are added to the EC codebase, they may
not support v2 of the EC protocol.

If the v3 initial handshake transfer fails, the kernel will try
and call cmd_xfer as a fallback. If v2 is not supported, cmd_xfer
will be NULL, and the code will end up causing a kernel panic.

Add a check for NULL before calling the transfer function, along
with a helpful comment explaining how one might end up in this
situation.

Signed-off-by: Enrico Granata &lt;egranata@chromium.org&gt;
Reviewed-by: Jett Rink &lt;jettrink@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>platform/x86: dell-laptop: fix rfkill functionality</title>
<updated>2019-05-16T17:35:33+00:00</updated>
<author>
<name>Mario Limonciello</name>
<email>mario.limonciello@dell.com</email>
</author>
<published>2019-03-27T14:25:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e2bc9bc6eede76f4d5f003e855959e0bfcc9779e'/>
<id>urn:sha1:e2bc9bc6eede76f4d5f003e855959e0bfcc9779e</id>
<content type='text'>
commit 6cc13c28da5beee0f706db6450e190709700b34a upstream.

When converting the driver two arguments were transposed leading
to rfkill not working.

BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=201427
Reported-by: Pepijn de Vos &lt;pepijndevos@gmail.com&gt;
Fixes: 549b49 ("platform/x86: dell-smbios: Introduce dispatcher for SMM calls")
Signed-off-by: Mario Limonciello &lt;mario.limonciello@dell.com&gt;
Acked-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Cc: &lt;stable@vger.kernel.org&gt; # 4.14.x
Signed-off-by: Darren Hart (VMware) &lt;dvhart@infradead.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>platform/x86: thinkpad_acpi: Disable Bluetooth for some machines</title>
<updated>2019-05-16T17:35:33+00:00</updated>
<author>
<name>Jiaxun Yang</name>
<email>jiaxun.yang@flygoat.com</email>
</author>
<published>2019-03-07T09:37:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=59190fff6b228dc1297acdc8b725bf77655e6c68'/>
<id>urn:sha1:59190fff6b228dc1297acdc8b725bf77655e6c68</id>
<content type='text'>
commit f7db839fccf087664e5587966220821289b6a9cb upstream.

Some AMD based ThinkPads have a firmware bug that calling
"GBDC" will cause Bluetooth on Intel wireless cards blocked.

Probe these models by DMI match and disable Bluetooth subdriver
if specified Intel wireless card exist.

Cc: stable &lt;stable@vger.kernel.org&gt; # 4.14+
Signed-off-by: Jiaxun Yang &lt;jiaxun.yang@flygoat.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: sony-laptop: Fix unintentional fall-through</title>
<updated>2019-05-16T17:35:32+00:00</updated>
<author>
<name>Gustavo A. R. Silva</name>
<email>gustavo@embeddedor.com</email>
</author>
<published>2019-04-24T18:09:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=67acc44d45ae722f47b33d5b48948a033d6c571d'/>
<id>urn:sha1:67acc44d45ae722f47b33d5b48948a033d6c571d</id>
<content type='text'>
commit 1cbd7a64959d33e7a2a1fa2bf36a62b350a9fcbd upstream.

It seems that the default case should return AE_CTRL_TERMINATE, instead
of falling through to case ACPI_RESOURCE_TYPE_END_TAG and returning AE_OK;
otherwise the line of code at the end of the function is unreachable and
makes no sense:

return AE_CTRL_TERMINATE;

This fix is based on the following thread of discussion:

https://lore.kernel.org/patchwork/patch/959782/

Fixes: 33a04454527e ("sony-laptop: Add SNY6001 device handling (sonypi reimplementation)")
Cc: stable@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&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>Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux</title>
<updated>2019-04-13T21:33:56+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2019-04-13T21:33:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=09bad0df3974ef9e682447f48bb7fd55c48513f3'/>
<id>urn:sha1:09bad0df3974ef9e682447f48bb7fd55c48513f3</id>
<content type='text'>
Pull clk fixes from Stephen Boyd:
 "Here's more than a handful of clk driver fixes for changes that came
  in during the merge window:

   - Fix the AT91 sama5d2 programmable clk prescaler formula

   - A bunch of Amlogic meson clk driver fixes for the VPU clks

   - A DMI quirk for Intel's Bay Trail SoC's driver to properly mark pmc
     clks as critical only when really needed

   - Stop overwriting CLK_SET_RATE_PARENT flag in mediatek's clk gate
     implementation

   - Use the right structure to test for a frequency table in i.MX's
     PLL_1416x driver"

* tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux:
  clk: imx: Fix PLL_1416X not rounding rates
  clk: mediatek: fix clk-gate flag setting
  platform/x86: pmc_atom: Drop __initconst on dmi table
  clk: x86: Add system specific quirk to mark clocks as critical
  clk: meson: vid-pll-div: remove warning and return 0 on invalid config
  clk: meson: pll: fix rounding and setting a rate that matches precisely
  clk: meson-g12a: fix VPU clock parents
  clk: meson: g12a: fix VPU clock muxes mask
  clk: meson-gxbb: round the vdec dividers to closest
  clk: at91: fix programmable clock for sama5d2
</content>
</entry>
<entry>
<title>platform/x86: pmc_atom: Drop __initconst on dmi table</title>
<updated>2019-04-11T17:25:37+00:00</updated>
<author>
<name>Stephen Boyd</name>
<email>sboyd@kernel.org</email>
</author>
<published>2019-04-11T17:22:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=b995dcca7cf12f208cfd95fd9d5768dca7cccec7'/>
<id>urn:sha1:b995dcca7cf12f208cfd95fd9d5768dca7cccec7</id>
<content type='text'>
It's used by probe and that isn't an init function. Drop this so that we
don't get a section mismatch.

Reported-by: kbuild test robot &lt;lkp@intel.com&gt;
Cc: David Müller &lt;dave.mueller@gmx.ch&gt;
Cc: Hans de Goede &lt;hdegoede@redhat.com&gt;
Cc: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Fixes: 7c2e07130090 ("clk: x86: Add system specific quirk to mark clocks as critical")
Signed-off-by: Stephen Boyd &lt;sboyd@kernel.org&gt;
</content>
</entry>
<entry>
<title>clk: x86: Add system specific quirk to mark clocks as critical</title>
<updated>2019-04-10T22:54:12+00:00</updated>
<author>
<name>David Müller</name>
<email>dave.mueller@gmx.ch</email>
</author>
<published>2019-04-08T13:33:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=7c2e07130090ae001a97a6b65597830d6815e93e'/>
<id>urn:sha1:7c2e07130090ae001a97a6b65597830d6815e93e</id>
<content type='text'>
Since commit 648e921888ad ("clk: x86: Stop marking clocks as
CLK_IS_CRITICAL"), the pmc_plt_clocks of the Bay Trail SoC are
unconditionally gated off. Unfortunately this will break systems where these
clocks are used for external purposes beyond the kernel's knowledge. Fix it
by implementing a system specific quirk to mark the necessary pmc_plt_clks as
critical.

Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
Signed-off-by: David Müller &lt;dave.mueller@gmx.ch&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Reviewed-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Signed-off-by: Stephen Boyd &lt;sboyd@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'tag-chrome-platform-fixes-for-v5.1-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux</title>
<updated>2019-03-19T18:28:15+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2019-03-19T18:28:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=babf09c3837f3cf4b58225225609445419c338e6'/>
<id>urn:sha1:babf09c3837f3cf4b58225225609445419c338e6</id>
<content type='text'>
Pull chrome platform fixes from Benson Leung:
 "Two fixes:

   - Fix locking and close a potential race condition in the new
     wilco_ec driver.

   - Fix a warning in cros_ec_debugfs on systems that do not support
     console logging, such as the Asus C201"

* tag 'tag-chrome-platform-fixes-for-v5.1-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:
  platform/chrome: cros_ec_debugfs: cancel/schedule logging work only if supported
  platform/chrome: Fix locking pattern in wilco_ec_mailbox()
</content>
</entry>
<entry>
<title>platform/chrome: cros_ec_debugfs: cancel/schedule logging work only if supported</title>
<updated>2019-03-19T18:00:30+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2019-03-19T16:32:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=57aeef7f7a6848024b92c32bf23e8c85a8ac896d'/>
<id>urn:sha1:57aeef7f7a6848024b92c32bf23e8c85a8ac896d</id>
<content type='text'>
The following traceback was reported on ASUS C201, which does not support
console logging.

------------[ cut here ]------------
WARNING: CPU: 2 PID: 361 at kernel/workqueue.c:3030 __flush_work+0x38/0x154
Modules linked in: snd_soc_hdmi_codec cros_ec_debugfs cros_ec_sysfs uvcvideo dw_hdmi_cec dw_hdmi_i2s_audio videobuf2_vmalloc cfg80211 gpio_charger rk_crypto rfkill videobuf2_memops videobuf2_v4l2 des_generic videobuf2_common ofpart m25p80 spi_nor tpm_i2c_infineon sbs_battery mtd tpm joydev cros_ec_dev coreboot_table evdev mousedev ip_tables x_tables [last unloaded: brcmutil]
CPU: 2 PID: 361 Comm: systemd-sleep Not tainted 5.1.0-rc1-1-ARCH+ #1
Hardware name: Rockchip (Device Tree)
[&lt;c020e4b0&gt;] (unwind_backtrace) from [&lt;c020ac18&gt;] (show_stack+0x10/0x14)
[&lt;c020ac18&gt;] (show_stack) from [&lt;c07a3e04&gt;] (dump_stack+0x7c/0x9c)
[&lt;c07a3e04&gt;] (dump_stack) from [&lt;c0222748&gt;] (__warn+0xd0/0xec)
[&lt;c0222748&gt;] (__warn) from [&lt;c022279c&gt;] (warn_slowpath_null+0x38/0x44)
[&lt;c022279c&gt;] (warn_slowpath_null) from [&lt;c02365d0&gt;] (__flush_work+0x38/0x154)
[&lt;c02365d0&gt;] (__flush_work) from [&lt;c023786c&gt;] (__cancel_work_timer+0x114/0x1a4)
[&lt;c023786c&gt;] (__cancel_work_timer) from [&lt;bf33233c&gt;] (cros_ec_debugfs_suspend+0x14/0x1c [cros_ec_debugfs])
[&lt;bf33233c&gt;] (cros_ec_debugfs_suspend [cros_ec_debugfs]) from [&lt;c056a888&gt;] (dpm_run_callback+0x64/0xcc)
[&lt;c056a888&gt;] (dpm_run_callback) from [&lt;c056ad2c&gt;] (__device_suspend+0x174/0x3a8)
[&lt;c056ad2c&gt;] (__device_suspend) from [&lt;c056b9e0&gt;] (dpm_suspend+0x174/0x1e0)
[&lt;c056b9e0&gt;] (dpm_suspend) from [&lt;c026b3e0&gt;] (suspend_devices_and_enter+0x6c/0x50c)
[&lt;c026b3e0&gt;] (suspend_devices_and_enter) from [&lt;c026ba8c&gt;] (pm_suspend+0x20c/0x274)
[&lt;c026ba8c&gt;] (pm_suspend) from [&lt;c026a628&gt;] (state_store+0x54/0x88)
[&lt;c026a628&gt;] (state_store) from [&lt;c03cd2d0&gt;] (kernfs_fop_write+0x114/0x180)
[&lt;c03cd2d0&gt;] (kernfs_fop_write) from [&lt;c035d48c&gt;] (__vfs_write+0x1c/0x154)
[&lt;c035d48c&gt;] (__vfs_write) from [&lt;c035f9e8&gt;] (vfs_write+0xb8/0x198)
[&lt;c035f9e8&gt;] (vfs_write) from [&lt;c035fbc0&gt;] (ksys_write+0x3c/0x74)
[&lt;c035fbc0&gt;] (ksys_write) from [&lt;c0201000&gt;] (ret_fast_syscall+0x0/0x4c)
Exception stack(0xe9365fa8 to 0xe9365ff0)
5fa0: 00000004 beef8b28 00000004 beef8b28 00000004 00000000
5fc0: 00000004 beef8b28 02319170 00000004 beef8b28 00000004 b6f3d900 beef8b74
5fe0: 0000006c beef8a98 b6c0adac b6c66534
---[ end trace f4ee5df14e8ea0ec ]---

If console logging is not supported, the work structure is never
initialized, resulting in the traceback. Calling cancel/schedule functions
conditionally fixes the problem.

While at it, also fix error handling in the probe function.

Reported-by: Urja Rannikko &lt;urjaman@gmail.com&gt;
Cc: Urja Rannikko &lt;urjaman@gmail.com&gt;
Fixes: 6fce0a2cf5a05 ("mfd / platform: cros_ec: Move debugfs attributes to its own driver")
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Benson Leung &lt;bleung@chromium.org&gt;
</content>
</entry>
</feed>
