On Fri, 25 Oct 2024, Jani Nikula wrote:
> On Fri, 25 Oct 2024, Raag Jadav wrote:
>> @@ -70,6 +73,16 @@ static struct dentry *drm_debugfs_root;
>>
>> DEFINE_STATIC_SRCU(drm_unplug_srcu);
>>
>> +/*
>> + * Available recovery methods for wedged device. To be sent along with
>> device
>> + * wed
On Fri, Oct 25, 2024 at 12:08:50PM +0300, Jani Nikula wrote:
> On Fri, 25 Oct 2024, Raag Jadav wrote:
...
> > +/*
> > + * Available recovery methods for wedged device. To be sent along with
> > device
> > + * wedged uevent.
> > + */
> > +static const char *const drm_wedge_recovery_opts[] = {
>
On Fri, Oct 25, 2024 at 05:45:59PM +0300, Andy Shevchenko wrote:
> On Fri, Oct 25, 2024 at 12:08:50PM +0300, Jani Nikula wrote:
> > On Fri, 25 Oct 2024, Raag Jadav wrote:
>
> ...
>
> > > +/*
> > > + * Available recovery methods for wedged device. To be sent along with
> > > device
> > > + * wed
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.12-rc4
next-20241025]
[If your patch is applied to the wrong git tree, k
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.12-rc4
next-20241025]
[If your patch is applied to the wrong git tree, k
On Fri, 25 Oct 2024, Raag Jadav wrote:
> Introduce device wedged event, which will notify userspace of wedged
> (hanged/unusable) state of the DRM device through a uevent. This is
> useful especially in cases where the device is no longer operating as
> expected even after a reset and has become u
