[PATCH v2] drm/radeon: Retry DDC probing on DVI on failure if we got an HPD interrupt

From: Lyude HPD signals on DVI ports can be fired off before the pins required for DDC probing actually make contact, due to the pins for HPD making contact first. This results in a HPD signal being asserted but DDC probing failing, resulting in hotplugging occasionally failing. This is

[PATCH v2] drm/radeon: Retry DDC probing on DVI on failure if we got an HPD interrupt

From: Lyude HPD signals on DVI ports can be fired off before the pins required for DDC probing actually make contact, due to the pins for HPD making contact first. This results in a HPD signal being asserted but DDC probing failing, resulting in hotplugging occasionally

[PATCH] drm/radeon: Retry DDC probing on DVI on failure if we got an HPD interrupt

From: Stephen Chandler Paul HPD signals on DVI ports can be fired off before the pins required for DDC probing actually make contact, due to the pins for HPD making contact first. This results in a HPD signal being asserted but DDC probing failing, resulting in hotplugging occasionally failing.

[PATCH] drm/radeon: Retry DDC probing on DVI on failure if we got an HPD interrupt

From: Stephen Chandler Paul HPD signals on DVI ports can be fired off before the pins required for DDC probing actually make contact, due to the pins for HPD making contact first. This results in a HPD signal being asserted but DDC probing failing, resulting in hotplugging

[PATCH v6.2 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v6.2 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH v8] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v8] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH v7] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v7] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH v6.1 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v6 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v6 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH v6.1 1/1] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH v5] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and emulate any serio

[PATCH v5] Input: Add userio module

From: Stephen Chandler Paul Debugging input devices, specifically laptop touchpads, can be tricky without having the physical device handy. Here we try to remedy that with userio. This module allows an application to connect to a character device provided by the kernel, and

[PATCH] DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd

From: Stephen Chandler Paul Most of the time this isn't an issue since hotplugging an adaptor will trigger a crtc mode change which in turn, causes the driver to probe every DisplayPort for a dpcd. However, in cases where hotplugging doesn't cause a mode change (specifically when one unplugs a

[PATCH] DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd

From: Stephen Chandler Paul cp...@redhat.com Most of the time this isn't an issue since hotplugging an adaptor will trigger a crtc mode change which in turn, causes the driver to probe every DisplayPort for a dpcd. However, in cases where hotplugging doesn't cause a mode change (specifically when

[PATCH v5] i8042: Add unmask_kbd_data option

From: Stephen Chandler Paul A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such it's probably a

[PATCH v5] i8042: Add unmask_kbd_data option

From: Stephen Chandler Paul cp...@redhat.com A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such

[PATCH v4] i8042: Add debug_kbd option

From: Stephen Chandler Paul A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such it's probably a

[PATCH v3] i8042: Add debug_kbd option

From: Stephen Chandler Paul A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such it's probably a

[PATCH v2] i8042: Add debug_kbd option

From: Stephen Chandler Paul A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such it's probably a

[PATCH v2] i8042: Add debug_kbd option

From: Stephen Chandler Paul cp...@redhat.com A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such

[PATCH v4] i8042: Add debug_kbd option

From: Stephen Chandler Paul cp...@redhat.com A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such

[PATCH v3] i8042: Add debug_kbd option

From: Stephen Chandler Paul cp...@redhat.com A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such

[PATCH] i8042: Add debug_kbd option

From: Stephen Chandler Paul A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such it's probably a

[PATCH] i8042: Add debug_kbd option

From: Stephen Chandler Paul cp...@redhat.com A big problem with the current i8042 debugging option is that it outputs data going to and from the keyboard by default. As a result, many dmesg logs uploaded by users will unintentionally contain sensitive information such as their password, as such