All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: javierm@redhat.com, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-fbdev@vger.kernel.org,
	Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH v2 04/11] drm/tegra: Set fbdev FBINFO_VIRTFB flag
Date: Thu, 6 Jul 2023 16:31:15 +0200	[thread overview]
Message-ID: <ZKbQM2SsPcdiWXnB@orome> (raw)
In-Reply-To: <20230706124905.15134-5-tzimmermann@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On Thu, Jul 06, 2023 at 02:46:42PM +0200, Thomas Zimmermann wrote:
> Mark the framebuffer with FBINFO_VIRTFB. The framebuffer range is
> in DMA-able memory and should be accessed with the CPU's regular
> memory ops.
> 
> v2:
> 	* drop FBINFO_DEFAULT
> 
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> Acked-by: Maxime Ripard <mripard@kernel.org>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Mikko Perttunen <mperttunen@nvidia.com>
> ---
>  drivers/gpu/drm/tegra/fbdev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/tegra/fbdev.c b/drivers/gpu/drm/tegra/fbdev.c
> index 82577b7c88da..d8460c5dc91e 100644
> --- a/drivers/gpu/drm/tegra/fbdev.c
> +++ b/drivers/gpu/drm/tegra/fbdev.c
> @@ -132,6 +132,7 @@ static int tegra_fbdev_probe(struct drm_fb_helper *helper,
>  		}
>  	}
>  
> +	info->flags |= FBINFO_VIRTFB;
>  	info->screen_base = (void __iomem *)bo->vaddr + offset;

As part of this, do we also need to set info->screen_buffer instead of
info->screen_base? The drm_fbdev_dma_helper functions do that.

Thierry

>  	info->screen_size = size;
>  	info->fix.smem_start = (unsigned long)(bo->iova + offset);
> -- 
> 2.41.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: javierm@redhat.com, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-fbdev@vger.kernel.org,
	Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH v2 04/11] drm/tegra: Set fbdev FBINFO_VIRTFB flag
Date: Thu, 6 Jul 2023 16:31:15 +0200	[thread overview]
Message-ID: <ZKbQM2SsPcdiWXnB@orome> (raw)
In-Reply-To: <20230706124905.15134-5-tzimmermann@suse.de>


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

On Thu, Jul 06, 2023 at 02:46:42PM +0200, Thomas Zimmermann wrote:
> Mark the framebuffer with FBINFO_VIRTFB. The framebuffer range is
> in DMA-able memory and should be accessed with the CPU's regular
> memory ops.
> 
> v2:
> 	* drop FBINFO_DEFAULT
> 
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> Acked-by: Maxime Ripard <mripard@kernel.org>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Mikko Perttunen <mperttunen@nvidia.com>
> ---
>  drivers/gpu/drm/tegra/fbdev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/tegra/fbdev.c b/drivers/gpu/drm/tegra/fbdev.c
> index 82577b7c88da..d8460c5dc91e 100644
> --- a/drivers/gpu/drm/tegra/fbdev.c
> +++ b/drivers/gpu/drm/tegra/fbdev.c
> @@ -132,6 +132,7 @@ static int tegra_fbdev_probe(struct drm_fb_helper *helper,
>  		}
>  	}
>  
> +	info->flags |= FBINFO_VIRTFB;
>  	info->screen_base = (void __iomem *)bo->vaddr + offset;

As part of this, do we also need to set info->screen_buffer instead of
info->screen_base? The drm_fbdev_dma_helper functions do that.

Thierry

>  	info->screen_size = size;
>  	info->fix.smem_start = (unsigned long)(bo->iova + offset);
> -- 
> 2.41.0
> 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-fbdev@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	javierm@redhat.com, dri-devel@lists.freedesktop.org,
	Mikko Perttunen <mperttunen@nvidia.com>,
	mripard@kernel.org, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 04/11] drm/tegra: Set fbdev FBINFO_VIRTFB flag
Date: Thu, 6 Jul 2023 16:31:15 +0200	[thread overview]
Message-ID: <ZKbQM2SsPcdiWXnB@orome> (raw)
In-Reply-To: <20230706124905.15134-5-tzimmermann@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On Thu, Jul 06, 2023 at 02:46:42PM +0200, Thomas Zimmermann wrote:
> Mark the framebuffer with FBINFO_VIRTFB. The framebuffer range is
> in DMA-able memory and should be accessed with the CPU's regular
> memory ops.
> 
> v2:
> 	* drop FBINFO_DEFAULT
> 
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> Acked-by: Maxime Ripard <mripard@kernel.org>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Mikko Perttunen <mperttunen@nvidia.com>
> ---
>  drivers/gpu/drm/tegra/fbdev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/tegra/fbdev.c b/drivers/gpu/drm/tegra/fbdev.c
> index 82577b7c88da..d8460c5dc91e 100644
> --- a/drivers/gpu/drm/tegra/fbdev.c
> +++ b/drivers/gpu/drm/tegra/fbdev.c
> @@ -132,6 +132,7 @@ static int tegra_fbdev_probe(struct drm_fb_helper *helper,
>  		}
>  	}
>  
> +	info->flags |= FBINFO_VIRTFB;
>  	info->screen_base = (void __iomem *)bo->vaddr + offset;

As part of this, do we also need to set info->screen_buffer instead of
info->screen_base? The drm_fbdev_dma_helper functions do that.

Thierry

>  	info->screen_size = size;
>  	info->fix.smem_start = (unsigned long)(bo->iova + offset);
> -- 
> 2.41.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-07-06 14:31 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 12:46 [PATCH v2 00/11] drm: Improve fbdev emulation for DMA-able framebuffers Thomas Zimmermann
2023-07-06 12:46 ` Thomas Zimmermann
2023-07-06 12:46 ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 01/11] fbdev: Add fb_ops init macros for framebuffers in DMA-able memory Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 02/11] drm/fbdev-dma: Use fbdev DMA helpers Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 03/11] drm/tegra: " Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 04/11] drm/tegra: Set fbdev FBINFO_VIRTFB flag Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 14:31   ` Thierry Reding [this message]
2023-07-06 14:31     ` Thierry Reding
2023-07-06 14:31     ` Thierry Reding
2023-07-06 14:47     ` Thomas Zimmermann
2023-07-06 14:47       ` Thomas Zimmermann
2023-07-06 14:47       ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 05/11] drm/exynos: Use fbdev DMA helpers Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 06/11] drm/exynos: Set fbdev FBINFO_VIRTFB flag Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-07  2:01   ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-07  2:01     ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-07  2:01     ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-06 12:46 ` [PATCH v2 07/11] drm/omapdrm: Set VM flags in GEM-object mmap function Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 08/11] drm/omapdrm: Use GEM mmap for fbdev emulation Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 09/11] drm/omapdrm: Set fbdev FBINFO_VIRTFB flag Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 10/11] fbdev: Remove FB_DEFAULT_SYS_OPS Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46 ` [PATCH v2 11/11] fbdev: Harmonize some comments in <linux/fb.h> Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 12:46   ` Thomas Zimmermann
2023-07-06 13:07   ` Javier Martinez Canillas
2023-07-06 13:07     ` Javier Martinez Canillas
2023-07-06 13:07     ` 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=ZKbQM2SsPcdiWXnB@orome \
    --to=thierry.reding@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mperttunen@nvidia.com \
    --cc=mripard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.