<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/drivers/hid/intel-ish-hid/ipc/ipc.c, branch linus/master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/drivers/hid/intel-ish-hid/ipc/ipc.c?h=linus%2Fmaster</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/drivers/hid/intel-ish-hid/ipc/ipc.c?h=linus%2Fmaster'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2022-01-06T14:39:43Z</updated>
<entry>
<title>HID: intel-ish-hid: ipc: Specify no cache snooping on TGL and ADL</title>
<updated>2022-01-06T14:39:43Z</updated>
<author>
<name>Ye Xiang</name>
<email>xiang.ye@intel.com</email>
</author>
<published>2021-12-17T07:45:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=bcad6d1bd9177740176ea79f6d0fc9f5b07e0c43'/>
<id>urn:sha1:bcad6d1bd9177740176ea79f6d0fc9f5b07e0c43</id>
<content type='text'>
Specify that both TGL and ADL don't support DMA cache snooping.

Signed-off-by: Ye Xiang &lt;xiang.ye@intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: ipc: Specify that EHL no cache snooping</title>
<updated>2021-06-14T13:55:09Z</updated>
<author>
<name>Even Xu</name>
<email>even.xu@intel.com</email>
</author>
<published>2021-06-10T06:21:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=aa59d6bb5ec88e30802174f9accc5d2dc50209ad'/>
<id>urn:sha1:aa59d6bb5ec88e30802174f9accc5d2dc50209ad</id>
<content type='text'>
Specify that EHL doesn't support DMA cache snooping.

Acked-by: Pandruvada, Srinivas &lt;srinivas.pandruvada@intel.com&gt;
Signed-off-by: Even Xu &lt;even.xu@intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: ipc: Correct fw_reset_work_fn() function name in header</title>
<updated>2021-04-07T15:56:34Z</updated>
<author>
<name>Lee Jones</name>
<email>lee.jones@linaro.org</email>
</author>
<published>2021-03-26T14:34:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=5f87e027913009bfcdd368b8ab9e10c1a8c8b22f'/>
<id>urn:sha1:5f87e027913009bfcdd368b8ab9e10c1a8c8b22f</id>
<content type='text'>
Fixes the following W=1 kernel build warning(s):

 drivers/hid/intel-ish-hid/ipc/ipc.c:553: warning: expecting prototype for ish_fw_reset_work_fn(). Prototype was for fw_reset_work_fn() instead

Cc: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;
Cc: Jiri Kosina &lt;jikos@kernel.org&gt;
Cc: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;
Cc: Zhang Lixu &lt;lixu.zhang@intel.com&gt;
Cc: "Krzysztof Wilczyński" &lt;kw@linux.com&gt;
Cc: linux-input@vger.kernel.org
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Acked-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;
Signed-off-by: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: ipc: Address EHL Sx resume issues</title>
<updated>2021-01-06T16:20:02Z</updated>
<author>
<name>Zhang Lixu</name>
<email>lixu.zhang@intel.com</email>
</author>
<published>2020-12-16T06:36:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=2f4ec1548b4e816b25c1486df30b1a2920c62cbc'/>
<id>urn:sha1:2f4ec1548b4e816b25c1486df30b1a2920c62cbc</id>
<content type='text'>
When OOB is disabled, FW will be power gated when system is in S3/S4/S5
which is the same behavior with legacy ISH FW.
When OOB is enabled, FW will always power on which is totally different
comparing to legacy ISH FW.

So NO_D3 flag is not enough to check FW's status after resume.
Here we can use IPC FW status register to check host link status.
If it is false, it means FW get reset after power gated, need go through
the whole initialization flow; If it is true, it means FW is alive, just
set host ready bit to let fw know host is up.

Co-developed-by: Wei Jiang &lt;wei.w.jiang@intel.com&gt;
Signed-off-by: Wei Jiang &lt;wei.w.jiang@intel.com&gt;
Signed-off-by: Even Xu &lt;even.xu@intel.com&gt;
Signed-off-by: Zhang Lixu &lt;lixu.zhang@intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>PCI/PM: Rename pci_dev.d3_delay to d3hot_delay</title>
<updated>2020-09-29T19:21:50Z</updated>
<author>
<name>Krzysztof Wilczyński</name>
<email>kw@linux.com</email>
</author>
<published>2020-07-30T21:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=3789af9a13e5561738c0f2114e3a5e22c843ca3e'/>
<id>urn:sha1:3789af9a13e5561738c0f2114e3a5e22c843ca3e</id>
<content type='text'>
PCI devices support two variants of the D3 power state: D3hot (main power
present) D3cold (main power removed).  Previously struct pci_dev contained:

  unsigned int    d3_delay;       /* D3-&gt;D0 transition time in ms */
  unsigned int    d3cold_delay;   /* D3cold-&gt;D0 transition time in ms */

"d3_delay" refers specifically to the D3hot state.  Rename it to
"d3hot_delay" to avoid ambiguity and align with the ACPI "_DSM for
Specifying Device Readiness Durations" in the PCI Firmware spec r3.2,
sec 4.6.9.

There is no change to the functionality.

Link: https://lore.kernel.org/r/20200730210848.1578826-1-kw@linux.com
Signed-off-by: Krzysztof Wilczyński &lt;kw@linux.com&gt;
Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: ipc: set NO_D3 flag only when needed</title>
<updated>2019-08-19T12:01:50Z</updated>
<author>
<name>Zhang Lixu</name>
<email>lixu.zhang@intel.com</email>
</author>
<published>2019-08-08T10:21:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=c1ca58f6982bb815c27a4a75f0f430f87b624f66'/>
<id>urn:sha1:c1ca58f6982bb815c27a4a75f0f430f87b624f66</id>
<content type='text'>
Currently, the NO_D3 flag is set in ish_probe(), and cleared in
ish_remove(). So even if the system goes into S3, ISH is still
in D0i3 state. It makes more sense that put ISH into D3 as system
goes into S3 and put ISH into D0i3 as system goes into suspend-to-idle.
I remove the NO_D3 setting in ish_probe(), so that ISH can enter
D3 state when system enters S3. Only set N0_D3 flag when system
enters the suspend-to-idle or platform specified, and clear it
when system resume.

When the ISH enters D3, the FW will check the DMA bit status.
If the DMA bit is set, the FW will reset automatically. So the
DMA bit need be clear before putting ISH into D3 state.

Signed-off-by: Zhang Lixu &lt;lixu.zhang@intel.com&gt;
Acked-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 288</title>
<updated>2019-06-05T15:36:37Z</updated>
<author>
<name>Thomas Gleixner</name>
<email>tglx@linutronix.de</email>
</author>
<published>2019-05-29T14:18:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=2025cf9e193de05b0654570dd639acb49ebd3adf'/>
<id>urn:sha1:2025cf9e193de05b0654570dd639acb49ebd3adf</id>
<content type='text'>
Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms and conditions of the gnu general public license
  version 2 as published by the free software foundation this program
  is distributed in the hope it will be useful but without any
  warranty without even the implied warranty of merchantability or
  fitness for a particular purpose see the gnu general public license
  for more details

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 263 file(s).

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Reviewed-by: Allison Randal &lt;allison@lohutok.net&gt;
Reviewed-by: Alexios Zavras &lt;alexios.zavras@intel.com&gt;
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190529141901.208660670@linutronix.de
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-5.1/i2c-hid' into for-linus</title>
<updated>2019-03-05T14:42:51Z</updated>
<author>
<name>Jiri Kosina</name>
<email>jkosina@suse.cz</email>
</author>
<published>2019-03-05T14:42:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=9f66d83ed704bc9ac0f09eb744f8e76a81006eb9'/>
<id>urn:sha1:9f66d83ed704bc9ac0f09eb744f8e76a81006eb9</id>
<content type='text'>
Fix dmesg flood for Elan touchpanels which are too slow to assert IRQ from Kai-Heng Feng
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: move doorbell writing before flush</title>
<updated>2019-02-15T21:47:21Z</updated>
<author>
<name>Hong Liu</name>
<email>hong.liu@intel.com</email>
</author>
<published>2019-02-12T12:05:22Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=7e06e0d5493b3e88016b247fe92f67a071d2c655'/>
<id>urn:sha1:7e06e0d5493b3e88016b247fe92f67a071d2c655</id>
<content type='text'>
Reading of IPC_REG_ISH_HOST_FWSTS will flush both message register
and doorbell. So move the doorbell write before reading of
IPC_REG_ISH_HOST_FWSTS.

Signed-off-by: Hong Liu &lt;hong.liu@intel.com&gt;
Tested-by: Hongyan Song &lt;hongyan.song@intel.com&gt;
Acked-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>HID: intel-ish-hid: Optimize writing ipc message from queue</title>
<updated>2019-02-15T21:47:21Z</updated>
<author>
<name>Hong Liu</name>
<email>hong.liu@intel.com</email>
</author>
<published>2019-02-12T12:05:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=b22f805bbe090d42e2eed86aa075687e47f924b7'/>
<id>urn:sha1:b22f805bbe090d42e2eed86aa075687e47f924b7</id>
<content type='text'>
Currently we are using one additional static variable and a spinlock to
prevent contention of writing IPC messages to ISH hardware, which is
not necessary. Once ISH is ready to accept new data, we can push new
data to hardware. This pushing of new data is already protected by
wr_processing_spinlock for contention, which is enough. So use this
spinlock to check both readiness for accepting new data and once ready
allow writing of ipc message from queue to ISH hardware.

While here, cleaned up some space after return.

Signed-off-by: Hong Liu &lt;hong.liu@intel.com&gt;
Tested-by: Hongyan Song &lt;hongyan.song@intel.com&gt;
Acked-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
</feed>
