From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: Re: [PATCH v3] drm/tegra: Do not use ->load() and ->unload() callbacks
Date: Tue, 29 Oct 2019 16:25:36 +0300 [thread overview]
Message-ID: <28aaf3c5-2e23-c947-9dd9-31571b5d5f1b@gmail.com> (raw)
In-Reply-To: <20191028121610.3889207-1-thierry.reding@gmail.com>
28.10.2019 15:16, Thierry Reding пишет:
> From: Thierry Reding <treding@nvidia.com>
>
> The ->load() and ->unload() drivers are midlayers and should be avoided
> in modern drivers. Fix this by moving the code into the driver ->probe()
> and ->remove() implementations, respectively.
>
> v2: kick out conflicting framebuffers before initializing fbdev
> v3: rebase onto drm/tegra/for-next
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/gpu/drm/tegra/drm.c | 321 +++++++++++++++++-------------------
> 1 file changed, 154 insertions(+), 167 deletions(-)
Hello Thierry,
I tried a bit harder and managed to get simple-framebuffer working, the
bootloader's FB handover works fine for me before and after this patch.
Thanks!
Tested-by: Dmitry Osipenko <digetx@gmail.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-29 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 12:16 [PATCH v3] drm/tegra: Do not use ->load() and ->unload() callbacks Thierry Reding
2019-10-29 13:25 ` Dmitry Osipenko [this message]
2019-11-04 10:26 ` Daniel Vetter
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=28aaf3c5-2e23-c947-9dd9-31571b5d5f1b@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=thierry.reding@gmail.com \
/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