public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: javierm@redhat.com, dri-devel@lists.freedesktop.org,
	jonathanh@nvidia.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/7] drm/tegra: Convert fbdev to DRM client
Date: Wed, 5 Apr 2023 17:06:29 +0200	[thread overview]
Message-ID: <791521e1-1d2b-c0ff-7fe3-57d81af2bf2c@suse.de> (raw)
In-Reply-To: <ZC2L69yI6l_2zPuG@orome>


[-- Attachment #1.1: Type: text/plain, Size: 1996 bytes --]



Am 05.04.23 um 16:55 schrieb Thierry Reding:
> On Thu, Mar 30, 2023 at 10:36:00AM +0200, Thomas Zimmermann wrote:
>> Convert tegra's fbdev code to struct drm_client. Replaces the current
>> ad-hoc integration. The conversion includes a number of cleanups. As
>> with most other drivers' fbdev emulation, fbdev in tegra is now just
>> another DRM client that runs after the DRM device has been registered.
>>
>> Once all drivers' fbdev emulation has been converted to struct drm_client,
>> we can attempt to add additional in-kernel clients. A DRM-based dmesg
>> log or a bootsplash are commonly mentioned. DRM can then switch easily
>> among the existing clients if/when required.
>>
>> I did the conversion from similar experience with other drivers. But I
>> don't have the hardware to test this. Any testing is welcome.
>>
>> Thomas Zimmermann (7):
>>    drm/tegra: Include <linux/of.h>
>>    drm/tegra: Include <linux/i2c.h>
>>    drm/tegra: Removed fb from struct tegra_fbdev
>>    drm/tegra: Remove struct tegra_fbdev
>>    drm/tegra: Hide fbdev support behind config option
>>    drm/tegra: Initialize fbdev DRM client
>>    drm/tegra: Implement fbdev emulation as in-kernel client
>>
>>   drivers/gpu/drm/tegra/Makefile |   2 +
>>   drivers/gpu/drm/tegra/drm.c    |  23 +---
>>   drivers/gpu/drm/tegra/drm.h    |  27 ++--
>>   drivers/gpu/drm/tegra/fb.c     | 242 +--------------------------------
>>   drivers/gpu/drm/tegra/fbdev.c  | 240 ++++++++++++++++++++++++++++++++
>>   drivers/gpu/drm/tegra/output.c |   3 +
>>   drivers/gpu/drm/tegra/rgb.c    |   1 +
>>   7 files changed, 265 insertions(+), 273 deletions(-)
>>   create mode 100644 drivers/gpu/drm/tegra/fbdev.c
> 
> Seems to be working just fine. Applied, thanks.

Thanks a lot!

> 
> Thierry

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-04-05 15:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  8:36 [PATCH 0/7] drm/tegra: Convert fbdev to DRM client Thomas Zimmermann
2023-03-30  8:36 ` [PATCH 1/7] drm/tegra: Include <linux/of.h> Thomas Zimmermann
2023-03-30 12:51   ` [1/7] " Sui Jingfeng
2023-04-03 10:42     ` Thomas Zimmermann
2023-04-03 13:46       ` Sui Jingfeng
2023-03-30  8:36 ` [PATCH 2/7] drm/tegra: Include <linux/i2c.h> Thomas Zimmermann
2023-03-30 12:52   ` [2/7] " Sui Jingfeng
2023-03-30  8:36 ` [PATCH 3/7] drm/tegra: Removed fb from struct tegra_fbdev Thomas Zimmermann
2023-03-30  8:36 ` [PATCH 4/7] drm/tegra: Remove " Thomas Zimmermann
2023-03-30  8:36 ` [PATCH 5/7] drm/tegra: Hide fbdev support behind config option Thomas Zimmermann
2023-03-30  8:36 ` [PATCH 6/7] drm/tegra: Initialize fbdev DRM client Thomas Zimmermann
2023-03-30  8:36 ` [PATCH 7/7] drm/tegra: Implement fbdev emulation as in-kernel client Thomas Zimmermann
2023-04-05 14:55 ` [PATCH 0/7] drm/tegra: Convert fbdev to DRM client Thierry Reding
2023-04-05 15:06   ` Thomas Zimmermann [this message]
2023-04-05 15:04 ` Thierry Reding

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=791521e1-1d2b-c0ff-7fe3-57d81af2bf2c@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --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