All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Sui Jingfeng <15330273260@189.cn>
Cc: Maxime Ripard <maxime@cerno.tech>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	suijingfeng <suijingfeng@loongson.cn>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Randy Dunlap <rdunlap@infradead.org>,
	Roland Scheidegger <sroland@vmware.com>,
	linux-mips@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
	linux-kernel@vger.kernel.org,
	Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
	Rob Herring <robh+dt@kernel.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display controller
Date: Wed, 16 Feb 2022 14:43:34 +0000	[thread overview]
Message-ID: <CAPj87rOY0j7p5fduA+p-kT8HP7kc8f4j2Q=FkGutPPPvmV7zqQ@mail.gmail.com> (raw)
In-Reply-To: <adec818a-5c66-3b4a-6f27-bcb29b6c67d1@189.cn>

On Wed, 16 Feb 2022 at 14:13, Sui Jingfeng <15330273260@189.cn> wrote:
> On 2022/2/16 21:46, Daniel Stone wrote:
> > Other systems have this limitation, and Mesa's 'kmsro' concept makes
> > this work transparently, as long as your driver can export dmabufs
> > when running in 'VRAM' mode.
>
> When using vram helper based driver, the framebuffer  is locate at video
> ram. the backing memory fb is manage by TTM.
>
> while bo of etnaviv is locate at system ram. Currently i can't figure
> out how does the buffer going to be shared.

kmsro will allocate from the KMS device (usually using dumb buffers),
export that BO as a dmabuf, then import into etnaviv. etnaviv already
uses this for imx-drm.

Cheers,
Daniel

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Stone <daniel@fooishbar.org>
To: Sui Jingfeng <15330273260@189.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	suijingfeng <suijingfeng@loongson.cn>,
	David Airlie <airlied@linux.ie>,
	Randy Dunlap <rdunlap@infradead.org>,
	Roland Scheidegger <sroland@vmware.com>,
	linux-mips@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
	Rob Herring <robh+dt@kernel.org>,
	Maxime Ripard <maxime@cerno.tech>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display controller
Date: Wed, 16 Feb 2022 14:43:34 +0000	[thread overview]
Message-ID: <CAPj87rOY0j7p5fduA+p-kT8HP7kc8f4j2Q=FkGutPPPvmV7zqQ@mail.gmail.com> (raw)
In-Reply-To: <adec818a-5c66-3b4a-6f27-bcb29b6c67d1@189.cn>

On Wed, 16 Feb 2022 at 14:13, Sui Jingfeng <15330273260@189.cn> wrote:
> On 2022/2/16 21:46, Daniel Stone wrote:
> > Other systems have this limitation, and Mesa's 'kmsro' concept makes
> > this work transparently, as long as your driver can export dmabufs
> > when running in 'VRAM' mode.
>
> When using vram helper based driver, the framebuffer  is locate at video
> ram. the backing memory fb is manage by TTM.
>
> while bo of etnaviv is locate at system ram. Currently i can't figure
> out how does the buffer going to be shared.

kmsro will allocate from the KMS device (usually using dumb buffers),
export that BO as a dmabuf, then import into etnaviv. etnaviv already
uses this for imx-drm.

Cheers,
Daniel

  reply	other threads:[~2022-02-16 14:43 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  8:25 [PATCH v6 0/3] drm/lsdc: add drm driver for loongson display controller Sui Jingfeng
2022-02-03  8:25 ` Sui Jingfeng
2022-02-03  8:25 ` [PATCH v6 1/3] " Sui Jingfeng
2022-02-03  8:25   ` Sui Jingfeng
2022-02-03  8:53   ` Krzysztof Kozlowski
2022-02-03  8:53     ` Krzysztof Kozlowski
2022-02-03 11:07     ` Dan Carpenter
2022-02-03 11:07       ` Dan Carpenter
2022-02-03 11:29       ` Krzysztof Kozlowski
2022-02-03 11:29         ` Krzysztof Kozlowski
2022-02-03 13:34         ` Dan Carpenter
2022-02-03 13:34           ` Dan Carpenter
2022-02-03  8:58   ` Maxime Ripard
2022-02-03  8:58     ` Maxime Ripard
2022-02-03 14:14     ` Sui Jingfeng
2022-02-03 15:27     ` Sui Jingfeng
2022-02-03 15:47     ` Sui Jingfeng
2022-02-03 15:47       ` Sui Jingfeng
2022-02-09  8:52       ` Maxime Ripard
2022-02-09  8:52         ` Maxime Ripard
2022-02-09 11:56         ` Jiaxun Yang
2022-02-09 11:56           ` Jiaxun Yang
2022-02-09 14:04           ` Maxime Ripard
2022-02-09 14:04             ` Maxime Ripard
2022-02-09 14:14             ` Jiaxun Yang
2022-02-09 14:14               ` Jiaxun Yang
2023-02-03  3:25             ` suijingfeng
2022-02-03 16:04     ` Sui Jingfeng
2022-02-03 16:04       ` Sui Jingfeng
2022-02-09  8:49       ` Maxime Ripard
2022-02-09  8:49         ` Maxime Ripard
2022-02-09 14:38         ` Sui Jingfeng
2022-02-09 14:38           ` Sui Jingfeng
2022-02-09 16:16           ` Maxime Ripard
2022-02-09 16:16             ` Maxime Ripard
2022-02-12 18:11             ` Sui Jingfeng
2022-02-12 18:11               ` Sui Jingfeng
2022-02-16 14:08               ` Maxime Ripard
2022-02-16 14:08                 ` Maxime Ripard
2022-02-12 20:52             ` Ilia Mirkin
2022-02-12 20:52               ` Ilia Mirkin
2022-02-16 13:34             ` Sui Jingfeng
2022-02-16 13:34               ` Sui Jingfeng
2022-02-16 14:11               ` Maxime Ripard
2022-02-16 14:11                 ` Maxime Ripard
2022-02-03 16:29     ` Sui Jingfeng
2022-02-03 16:29       ` Sui Jingfeng
2022-02-09  8:43       ` Maxime Ripard
2022-02-09  8:43         ` Maxime Ripard
2022-02-09 15:41         ` Sui Jingfeng
2022-02-09 15:41           ` Sui Jingfeng
2022-02-09 16:19           ` Maxime Ripard
2022-02-09 16:19             ` Maxime Ripard
2022-02-16 13:46           ` Daniel Stone
2022-02-16 13:46             ` Daniel Stone
2022-02-16 14:13             ` Sui Jingfeng
2022-02-16 14:13               ` Sui Jingfeng
2022-02-16 14:43               ` Daniel Stone [this message]
2022-02-16 14:43                 ` Daniel Stone
2022-02-03 16:41     ` Sui Jingfeng
2022-02-03 16:41       ` Sui Jingfeng
2022-02-09  8:36       ` Maxime Ripard
2022-02-09  8:36         ` Maxime Ripard
2023-02-02  2:58         ` suijingfeng
2022-02-03  8:25 ` [PATCH v6 2/3] dt-bindings: ls2k1000: add the display controller device node Sui Jingfeng
2022-02-03  8:25   ` Sui Jingfeng
2022-02-03  8:50   ` Krzysztof Kozlowski
2022-02-03  8:50     ` Krzysztof Kozlowski
2022-02-16 14:01     ` Sui Jingfeng
2022-02-16 14:01       ` Sui Jingfeng
2022-02-17  8:38       ` Krzysztof Kozlowski
2022-02-17  8:38         ` Krzysztof Kozlowski
2022-02-03  8:25 ` [PATCH v6 3/3] dt-bindings: mips: loongson: introduce board specific dts Sui Jingfeng
2022-02-03  8:25   ` Sui Jingfeng
2022-02-03  8:49   ` Krzysztof Kozlowski
2022-02-03  8:49     ` Krzysztof Kozlowski
2022-02-09 12:00 ` [PATCH v6 0/3] drm/lsdc: add drm driver for loongson display controller Jiaxun Yang
2022-02-09 12:00   ` Jiaxun Yang
2022-02-10  4:04   ` Sui Jingfeng
2022-02-10  4:04     ` Sui Jingfeng
2022-02-06 19:38 [PATCH v6 1/3] " kernel test robot
2022-02-10 23:10 kernel test robot
2022-02-12  5:04 kernel test robot

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='CAPj87rOY0j7p5fduA+p-kT8HP7kc8f4j2Q=FkGutPPPvmV7zqQ@mail.gmail.com' \
    --to=daniel@fooishbar.org \
    --cc=15330273260@189.cn \
    --cc=airlied@linux.ie \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sroland@vmware.com \
    --cc=suijingfeng@loongson.cn \
    --cc=tsbogend@alpha.franken.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.