From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] drm/ssd130x: Fix an oops when attempting to update a disabled plane
Date: Mon, 17 Jul 2023 11:00:13 +0200 [thread overview]
Message-ID: <87r0p6kj4y.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <bbbb18e0-5de1-5155-c6b2-52a2b1d75898@suse.de>
Thomas Zimmermann <tzimmermann@suse.de> writes:
Hello Thomas,
> Hi
>
> Am 13.07.23 um 18:32 schrieb Javier Martinez Canillas:
[...]
>>
>> +static const struct drm_mode_config_helper_funcs ssd130x_mode_config_helpers = {
>> + .atomic_commit_tail = drm_atomic_helper_commit_tail_rpm,
>> +};
>> +
>
> After some discussion on IRC, I'd suggest to allocate the buffer
> somewhere within probe. So it will always be there when the plane code runs.
>
Yes, that's also what Geert suggested so I'll just do that. And also make
it a dev managed resource.
> A full fix would be to allocate the buffer memory as part of the plane
> state and/or the plane's atomic_check. That's a bit more complicated if
> you want to shared the buffer memory across plane updates.
>
I don't think is worth the complexity, allocating it on probe and released
when the device is unbound from the driver should be enough as Geert said.
> Best regards
> Thomas
>
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-07-17 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 16:32 Javier Martinez Canillas
2023-07-14 7:18 ` Geert Uytterhoeven
2023-07-14 7:53 ` Javier Martinez Canillas
2023-07-17 8:48 ` Thomas Zimmermann
2023-07-17 9:00 ` Javier Martinez Canillas [this message]
2023-07-17 9:04 ` Geert Uytterhoeven
2023-07-17 9:42 ` Javier Martinez Canillas
2023-07-17 10:37 ` Javier Martinez Canillas
2023-07-17 11:28 ` Geert Uytterhoeven
2023-07-17 13:26 ` Javier Martinez Canillas
2023-07-17 11:08 ` Thomas Zimmermann
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=87r0p6kj4y.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--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®