On 2/4/21 11:13 PM, Srinivas Pandruvada wrote:
> On Thu, 2021-02-04 at 16:33 +0800, You-Sheng Yang wrote:
>> Added Tiger Lake H PCI device ID to the supported device list.
>>
>> Signed-off-by: You-Sheng Yang
> Did you get chance to verify on a platform?
> Do you see sen
Added Tiger Lake H PCI device ID to the supported device list.
Signed-off-by: You-Sheng Yang
---
drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 +
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/hid/intel-ish-hid/ipc/hw-ish.h
b/drivers/hid
ot;, pure garbage data.
So is there something missed in the iwl_dev_info_table, or better, just
find another solid safe way to handle such trans/cfg mix?
Regards,
You-Sheng Yang
Tested and commented on the issue page. Thank you for the correction.
--
Cheers,
You-Sheng Yang
On 2019-10-08 15:17, Luciano Coelho wrote:
> On Tue, 2019-10-08 at 14:05 +0800, You-Sheng Yang wrote:
>> Follow-up for commit fddbfeece9c7 ("iwlwifi: fw: don't send
>> GEO_TX_
Follow-up for commit fddbfeece9c7 ("iwlwifi: fw: don't send
GEO_TX_POWER_LIMIT command to FW version 36"). There is no
GEO_TX_POWER_LIMIT command support for all revisions of FW version
29, either.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204151
Signed-off-by:
ions to the HOST
> specified Power State in under 1 second.
it can take as long as 1 second.
This changeset add a device property post-setpower-delay-ms and use it
to specify the delay after a SET_POWER command is issued for this
device.
References: https://bugzilla.kernel.org/show_bug.cgi?id=20
post-setpower-delay-ms.
References: https://bugzilla.kernel.org/show_bug.cgi?id=204991
Signed-off-by: You-Sheng Yang
---
drivers/hid/i2c-hid/i2c-hid-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/i2c-hid/i2c-hid-core.c
b/drivers/hid/i2c-hid/i2c-hid-core.c
and leaves the device in an unsupported Mouse mode.
This change adds a post-setpower-delay-ms device property that allows
specifying the delay after a SET_POWER command is issued.
References: https://bugzilla.kernel.org/show_bug.cgi?id=204991
Signed-off-by: You-Sheng Yang
---
.../bindings/input
On 2019/4/8 8:03 PM, Thomas Gleixner wrote:
> On Mon, 8 Apr 2019, You-Sheng Yang wrote:
>> +/*
>> + * On Intel CoffeeLake, tsc may be marked unstable unexpectedly after
>> + * entering PC10.
>> + */
>> +if (boot_cpu_da
On 2019/4/8 8:03 PM, Thomas Gleixner wrote:
> On Mon, 8 Apr 2019, You-Sheng Yang wrote:
>
>> From: You-Sheng Yang
>>
>> On Intel CoffeeLake it's observed tsc is always marked unstable
>> unexpectedly after entering idle state Package C10(PC10), and then clock
From: You-Sheng Yang
On Intel CoffeeLake it's observed tsc is always marked unstable
unexpectedly after entering idle state Package C10(PC10), and then clock
source is switched to hpet. This patch marks tsc as reliable when CPUID
matches CoffeeLake.
Link: https://bugzilla.kerne
On Wed, Jul 20, 2016 at 5:52 AM, Seth Forshee
wrote:
> On Tue, Jul 19, 2016 at 07:44:11PM -0700, Sheng Yang wrote:
>> On Tue, Apr 26, 2016 at 12:36 PM, Seth Forshee
>> wrote:
>> > When the userspace process servicing fuse requests is running in
>> > a pid namesp
On Tue, Apr 26, 2016 at 12:36 PM, Seth Forshee
wrote:
> When the userspace process servicing fuse requests is running in
> a pid namespace then pids passed via the fuse fd are not being
> translated into that process' namespace. Translation is necessary
> for the pid to be useful to that process.
Anyone interested in TCM loopback device?
--Sheng
On Thu, Oct 22, 2015 at 11:28 AM, Sheng Yang wrote:
> In the past, the scsi_host's number wasn't shown anywhere, user have to
> depends on vpg_83 to find the block device, which is also depends on
> backstore implementation.
;
> http://sourceforge.net/p/nbd/mailman/nbd-general/thread/20131114075827.GA13554%40quack.suse.cz/#msg31636917
>
> Maybe Markus has some thoughts on how to fix it. I think there are a couple
> options.
>
> --
> Paul
>
> On Wed, Sep 16, 2015 at 9:18 PM, Sheng Yang wrot
_sb_start_write+0xec/0x100
[ 240.366119] #1: (&sb->s_type->i_mutex_key#9){..}, at:
[] ext4_file_write_iter+0x18f/0x420
--Sheng
On Sun, Sep 20, 2015 at 11:52 PM, Wouter Verhelst wrote:
> Hi,
>
> [linux-kernel CC dropped, since this is irrelevant for them]
>
> On Wed,
Hi, Markus,
I've experienced kernel bug and system hang regarding using
nbd-client/server on the same machine. Kernel verison is v4.2.
I know http://nbd.sourceforge.net/ said:
"Please note that read-write nbd with client and server on the same
machine is a bad idea: expect deadlock within seconds
On Friday 01 June 2007 04:26, Dave Jones wrote:
> On Tue, May 29, 2007 at 09:47:53AM +0800, Yang Sheng wrote:
> > On Tuesday 29 May 2007 06:52, Randy Dunlap wrote:
> > > On Mon, 28 May 2007 15:03:10 +0800 Yang Sheng wrote:
> > > > Why we need this:
> > > >
> > > > It can speed up the calling o
18 matches
Mail list logo
