Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Mikko Perttunen <cyndis@kapsi.fi>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH] drm/tegra: Remove existing framebuffer only if we support display
Date: Thu, 31 Aug 2023 09:33:19 +0300	[thread overview]
Message-ID: <5f1bca1b-8deb-e677-521d-87d3848e22df@kapsi.fi> (raw)
In-Reply-To: <f5ce7a77-ee3e-5186-dd8a-76c0bd794de0@suse.de>

On 8/30/23 13:19, Thomas Zimmermann wrote:
> Hi
> 
> Am 25.08.23 um 15:22 schrieb Thierry Reding:
>> From: Thierry Reding <treding@nvidia.com>
>>
>> Tegra DRM doesn't support display on Tegra234 and later, so make sure
>> not to remove any existing framebuffers in that case.
>>
>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>> ---
>>   drivers/gpu/drm/tegra/drm.c | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tegra/drm.c b/drivers/gpu/drm/tegra/drm.c
>> index b1e1a78e30c6..7a38dadbc264 100644
>> --- a/drivers/gpu/drm/tegra/drm.c
>> +++ b/drivers/gpu/drm/tegra/drm.c
>> @@ -1220,9 +1220,11 @@ static int host1x_drm_probe(struct 
>> host1x_device *dev)
>>       drm_mode_config_reset(drm);
>> -    err = drm_aperture_remove_framebuffers(&tegra_drm_driver);
>> -    if (err < 0)
>> -        goto hub;
>> +    if (drm->mode_config.num_crtc > 0) {
> 
> If you don't support the hardware, wouldn't it be better to return 
> -ENODEV if !num_crtc?

While display is not supported through TegraDRM on Tegra234+, certain 
multimedia accelerators are supported, so we need to finish probe for those.

Cheers,
Mikko

> 
> Best regards
> Thomas
> 
>> +        err = drm_aperture_remove_framebuffers(&tegra_drm_driver);
>> +        if (err < 0)
>> +            goto hub;
>> +    }
>>       err = drm_dev_register(drm, 0);
>>       if (err < 0)
> 


  reply	other threads:[~2023-08-31  6:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 13:22 [PATCH] drm/tegra: Remove existing framebuffer only if we support display Thierry Reding
2023-08-30  6:13 ` Javier Martinez Canillas
2023-09-07  7:57   ` Thierry Reding
2023-09-07  8:11     ` Javier Martinez Canillas
2023-08-30 10:19 ` Thomas Zimmermann
2023-08-31  6:33   ` Mikko Perttunen [this message]
2023-08-31  8:04     ` Daniel Vetter
2023-09-07  8:03       ` Thierry Reding
2023-09-07  8:35         ` Thomas Zimmermann
2023-09-07  8:47           ` Javier Martinez Canillas

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=5f1bca1b-8deb-e677-521d-87d3848e22df@kapsi.fi \
    --to=cyndis@kapsi.fi \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --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