From: Danilo Krummrich <dakr@redhat.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
tzimmermann@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-misc-next v2 2/4] drm/vc4: plane: protect device resources after removal
Date: Wed, 24 Aug 2022 17:58:40 +0200 [thread overview]
Message-ID: <bd89a246-ee32-7b54-9c9c-7090cc7d51a2@redhat.com> (raw)
In-Reply-To: <20220824154823.qu3tdwypg5o3ci4z@houat>
Hi Maxime,
On 8/24/22 17:48, Maxime Ripard wrote:
>> @@ -1252,12 +1261,17 @@ void vc4_plane_async_set_fb(struct drm_plane *plane, struct drm_framebuffer *fb)
>> WARN_ON_ONCE(plane->state->crtc_x < 0 || plane->state->crtc_y < 0);
>> addr = bo->dma_addr + fb->offsets[0];
>>
>> + if (!drm_dev_enter(plane->dev, &idx))
>> + return;
>> +
>> /* Write the new address into the hardware immediately. The
>> * scanout will start from this address as soon as the FIFO
>> * needs to refill with pixels.
>> */
>> writel(addr, &vc4_state->hw_dlist[vc4_state->ptr0_offset]);
>>
>> + drm_dev_exit(idx);
>> +
>
> You did change the CRTC patch, but the comment to protect the entire
> function also applies to this one.
Yes, I changed this one too, but missed this particular function - gonna
send a v3.
- Danilo
>
> Maxime
next prev parent reply other threads:[~2022-08-24 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 11:08 [PATCH drm-misc-next v2 0/4] Fixes for vc4 hotplug rework Danilo Krummrich
2022-08-19 11:08 ` [PATCH drm-misc-next v2 1/4] drm/vc4: hdmi: unlock mutex when device is unplugged Danilo Krummrich
2022-08-19 11:08 ` [PATCH drm-misc-next v2 2/4] drm/vc4: plane: protect device resources after removal Danilo Krummrich
2022-08-24 15:48 ` Maxime Ripard
2022-08-24 15:58 ` Danilo Krummrich [this message]
2022-08-19 11:08 ` [PATCH drm-misc-next v2 3/4] drm/vc4: crtc: " Danilo Krummrich
2022-08-19 11:08 ` [PATCH drm-misc-next v2 4/4] drm/vc4: hvs: protect drm_print_regset32() Danilo Krummrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd89a246-ee32-7b54-9c9c-7090cc7d51a2@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®