Mario Limonciello
d2ef2fac35
thunderbolt: Fix a logic error in wake on connect
...
[ Upstream commit 1a760d10de ]
commit a5cfc9d658 ("thunderbolt: Add wake on connect/disconnect
on USB4 ports") introduced a sysfs file to control wake up policy
for a given USB4 port that defaulted to disabled.
However when testing commit 4bfeea6ec1 ("thunderbolt: Use wake
on connect and disconnect over suspend") I found that it was working
even without making changes to the power/wakeup file (which defaults
to disabled). This is because of a logic error doing a bitwise or
of the wake-on-connect flag with device_may_wakeup() which should
have been a logical AND.
Adjust the logic so that policy is only applied when wakeup is
actually enabled.
Fixes: a5cfc9d658 ("thunderbolt: Add wake on connect/disconnect on USB4 ports")
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com >
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com >
Signed-off-by: Sasha Levin <sashal@kernel.org >
2025-06-19 15:40:29 +02:00
..
2025-06-19 15:39:30 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:39:34 +02:00
2025-03-11 14:05:43 +01:00
2025-06-10 07:17:10 -04:00
2025-04-22 16:06:05 +09:00
2025-04-05 10:30:12 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:39:25 +02:00
2025-06-19 15:39:20 +02:00
2025-06-19 15:39:59 +02:00
2025-06-19 15:40:12 +02:00
2025-03-20 09:11:09 +01:00
2025-05-15 04:49:15 +03:00
2025-06-19 15:39:53 +02:00
2025-05-05 15:34:49 +02:00
2025-04-15 15:18:55 +02:00
2025-04-02 18:03:34 -07:00
2025-06-10 07:17:08 -04:00
2025-03-25 20:40:51 -07:00
2025-06-19 15:39:22 +02:00
2025-04-21 08:30:13 -07:00
2025-03-17 22:06:41 -07:00
2025-06-19 15:40:28 +02:00
2025-05-14 15:31:23 +02:00
2025-03-20 21:38:01 +01:00
2025-06-19 15:39:27 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:08 +02:00
2025-04-11 17:32:38 -07:00
2025-04-11 20:47:45 -03:00
2025-05-22 09:08:54 -07:00
2025-06-19 15:39:38 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:17 +02:00
2025-04-05 10:30:12 +02:00
2025-04-05 10:30:12 +02:00
2025-05-15 10:40:49 -07:00
2025-06-19 15:40:18 +02:00
2025-03-21 17:12:04 -05:00
2025-04-15 13:29:03 +02:00
2025-05-14 17:28:24 +02:00
2025-03-31 11:44:00 +02:00
2025-03-25 15:00:18 -07:00
2025-05-01 17:47:49 +02:00
2025-06-19 15:40:01 +02:00
2025-05-24 18:54:18 -07:00
2025-06-19 15:39:54 +02:00
2025-05-15 16:01:50 +02:00
2025-04-05 10:30:12 +02:00
2025-04-05 10:30:12 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:22 +02:00
2025-04-15 18:21:39 +02:00
2025-06-19 15:40:19 +02:00
2025-06-19 15:39:37 +02:00
2025-04-05 10:30:12 +02:00
2025-04-05 10:30:12 +02:00
2025-03-26 19:57:34 -07:00
2025-06-19 15:40:21 +02:00
2025-04-26 13:02:36 -07:00
2025-05-19 14:26:12 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:18 +02:00
2025-06-19 15:40:03 +02:00
2025-04-05 10:30:12 +02:00
2025-04-04 14:23:07 -07:00
2025-04-02 20:27:18 -07:00
2025-05-22 13:08:21 -07:00
2025-06-10 07:17:10 -04:00
2025-06-19 15:39:52 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:29 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:39:35 +02:00
2025-06-19 15:40:28 +02:00
2025-06-19 15:39:55 +02:00
2025-06-19 15:39:24 +02:00
2025-05-08 13:29:30 +02:00
2025-04-02 18:09:17 -07:00
2025-06-19 15:39:24 +02:00
2025-03-25 15:00:18 -07:00
2025-04-15 18:22:32 +02:00
2025-05-16 15:43:44 -07:00
2025-04-12 08:11:19 -07:00
2025-03-10 17:37:25 +01:00
2025-04-08 19:30:58 +02:00
2025-05-14 11:16:52 +02:00
2025-06-19 15:40:20 +02:00
2025-03-29 17:18:50 -07:00
2025-06-19 15:40:20 +02:00
2025-06-19 15:40:29 +02:00
2025-05-05 15:46:34 +02:00
2025-06-19 15:39:55 +02:00
2025-03-11 10:41:18 +01:00
2025-06-19 15:40:15 +02:00
2025-06-19 15:40:28 +02:00
2025-06-19 15:39:26 +02:00
2025-06-19 15:39:29 +02:00
2025-04-11 22:13:00 -04:00
2025-06-19 15:39:26 +02:00
2025-06-19 15:40:29 +02:00
2025-06-19 15:40:29 +02:00
2025-06-19 15:39:55 +02:00
2025-05-02 13:59:02 +02:00
2025-06-19 15:40:29 +02:00
2025-06-19 15:39:59 +02:00
2025-04-18 10:08:11 -04:00
2025-06-19 15:40:17 +02:00
2025-04-05 10:30:12 +02:00
2025-06-19 15:40:01 +02:00
2025-06-19 15:40:15 +02:00
2025-06-19 15:39:37 +02:00