Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-16 Thread Maxime Ripard
Hi, On Thu, Dec 12, 2024 at 12:37:59PM +0200, Raag Jadav wrote: > On Wed, Dec 11, 2024 at 06:14:12PM +0100, Maxime Ripard wrote: > > On Wed, Dec 04, 2024 at 01:17:17PM +0200, Raag Jadav wrote: > > > + misc maintainers > > > > > > On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote: >

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-13 Thread André Almeida
Hi Raag, Thank you for your patch. Em 28/11/2024 12:37, Raag Jadav escreveu: [...] +int drm_dev_wedged_event(struct drm_device *dev, unsigned long method) +{ + const char *recovery = NULL; + unsigned int len, opt; + /* Event string length up to 28+ characters with available

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-13 Thread Raag Jadav
On Thu, Dec 12, 2024 at 03:31:01PM -0300, André Almeida wrote: > Hi Raag, > > Thank you for your patch. > > Em 28/11/2024 12:37, Raag Jadav escreveu: > > [...] > > > +int drm_dev_wedged_event(struct drm_device *dev, unsigned long method) > > +{ > > + const char *recovery = NULL; > > + unsig

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-12 Thread Raag Jadav
On Wed, Dec 11, 2024 at 06:14:12PM +0100, Maxime Ripard wrote: > On Wed, Dec 04, 2024 at 01:17:17PM +0200, Raag Jadav wrote: > > + misc maintainers > > > > On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote: > > > Am 03.12.24 um 06:00 schrieb Raag Jadav: > > > > On Mon, Dec 02, 2024 a

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-11 Thread Maxime Ripard
On Wed, Dec 04, 2024 at 01:17:17PM +0200, Raag Jadav wrote: > + misc maintainers > > On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote: > > Am 03.12.24 um 06:00 schrieb Raag Jadav: > > > On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote: > > > > On Fri, Nov 29, 2024 at 10:40

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-04 Thread Raag Jadav
+ misc maintainers On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote: > Am 03.12.24 um 06:00 schrieb Raag Jadav: > > On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote: > > > On Fri, Nov 29, 2024 at 10:40:14AM -0300, André Almeida wrote: > > > > Hi Raag, > > > > > > > > Em 2

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-03 Thread Christian König
Am 03.12.24 um 06:00 schrieb Raag Jadav: On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote: On Fri, Nov 29, 2024 at 10:40:14AM -0300, André Almeida wrote: Hi Raag, Em 28/11/2024 12:37, Raag Jadav escreveu: Introduce device wedged event, which notifies userspace of 'wedged' (hanged/un

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-02 Thread Raag Jadav
On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote: > On Fri, Nov 29, 2024 at 10:40:14AM -0300, André Almeida wrote: > > Hi Raag, > > > > Em 28/11/2024 12:37, Raag Jadav escreveu: > > > Introduce device wedged event, which notifies userspace of 'wedged' > > > (hanged/unusable) state of the

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-12-02 Thread Raag Jadav
On Fri, Nov 29, 2024 at 10:40:14AM -0300, André Almeida wrote: > Hi Raag, > > Em 28/11/2024 12:37, Raag Jadav escreveu: > > Introduce device wedged event, which notifies userspace of 'wedged' > > (hanged/unusable) state of the DRM device through a uevent. This is > > useful especially in cases whe

Re: [PATCH v10 1/4] drm: Introduce device wedged event

2024-11-30 Thread André Almeida
Hi Raag, Em 28/11/2024 12:37, Raag Jadav escreveu: Introduce device wedged event, which notifies 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 and has become unrecoverable f

[PATCH v10 1/4] drm: Introduce device wedged event

2024-11-28 Thread Raag Jadav
Introduce device wedged event, which notifies 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 and has become unrecoverable from driver context. Purpose of this implementation is