All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, Chen-Yu Tsai <wens@csie.org>,
	Pawel Osciak <pawel@osciak.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Arnd Bergmann <arnd@arndb.de>,
	Alexandre Courbot <acourbot@chromium.org>,
	Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH v2 09/10] ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes
Date: Fri, 4 May 2018 11:15:55 +0200	[thread overview]
Message-ID: <20180504091555.idgtzey53lozj2uh@flea> (raw)
In-Reply-To: <e8cd340605ab4db8ebf2888a4fce645e8bc481d0.camel@bootlin.com>

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

On Fri, May 04, 2018 at 10:47:44AM +0200, Paul Kocialkowski wrote:
> > > > > +			reg = <0x01c0e000 0x1000>;
> > > > > +			memory-region = <&ve_memory>;
> > > > 
> > > > Since you made the CMA region the default one, you don't need to
> > > > tie
> > > > it to that device in particular (and you can drop it being
> > > > mandatory
> > > > from your binding as well).
> > > 
> > > What if another driver (or the system) claims memory from that zone
> > > and
> > > that the reserved memory ends up not being available for the VPU
> > > anymore?
> > > 
> > > Acccording to the reserved-memory documentation, the reusable
> > > property
> > > (that we need for dmabuf) puts a limitation that the device driver
> > > owning the region must be able to reclaim it back.
> > > 
> > > How does that work out if the CMA region is not tied to a driver in
> > > particular?
> > 
> > I'm not sure to get what you're saying. You have the property
> > linux,cma-default in your reserved region, so the behaviour you
> > described is what you explicitly asked for.
> 
> My point is that I don't see how the driver can claim back (part of) the
> reserved area if the area is not explicitly attached to it.
> 
> Or is that mechanism made in a way that all drivers wishing to use the
> reserved memory area can claim it back from the system, but there is no
> priority (other than first-come first-served) for which drivers claims
> it back in case two want to use the same reserved region (in a scenario
> where there isn't enough memory to allow both drivers)?

This is indeed what happens. Reusable is to let the system use the
reserved memory for things like caches that can easily be dropped when
a driver wants to use the memory in that reserved area. Once that
memory has been allocated, there's no claiming back, unless that
memory segment was freed of course.

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

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

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
To: Paul Kocialkowski
	<paul.kocialkowski-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
Cc: linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	Mauro Carvalho Chehab
	<mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
	Pawel Osciak <pawel-FA/gS7QP4orQT0dZR+AlfA@public.gmane.org>,
	Marek Szyprowski
	<m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	Kyungmin Park
	<kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	Hans Verkuil
	<hans.verkuil-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	Sakari Ailus
	<sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Alexandre Courbot
	<acourbot-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	Tomasz Figa <tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH v2 09/10] ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes
Date: Fri, 4 May 2018 11:15:55 +0200	[thread overview]
Message-ID: <20180504091555.idgtzey53lozj2uh@flea> (raw)
In-Reply-To: <e8cd340605ab4db8ebf2888a4fce645e8bc481d0.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>

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

On Fri, May 04, 2018 at 10:47:44AM +0200, Paul Kocialkowski wrote:
> > > > > +			reg = <0x01c0e000 0x1000>;
> > > > > +			memory-region = <&ve_memory>;
> > > > 
> > > > Since you made the CMA region the default one, you don't need to
> > > > tie
> > > > it to that device in particular (and you can drop it being
> > > > mandatory
> > > > from your binding as well).
> > > 
> > > What if another driver (or the system) claims memory from that zone
> > > and
> > > that the reserved memory ends up not being available for the VPU
> > > anymore?
> > > 
> > > Acccording to the reserved-memory documentation, the reusable
> > > property
> > > (that we need for dmabuf) puts a limitation that the device driver
> > > owning the region must be able to reclaim it back.
> > > 
> > > How does that work out if the CMA region is not tied to a driver in
> > > particular?
> > 
> > I'm not sure to get what you're saying. You have the property
> > linux,cma-default in your reserved region, so the behaviour you
> > described is what you explicitly asked for.
> 
> My point is that I don't see how the driver can claim back (part of) the
> reserved area if the area is not explicitly attached to it.
> 
> Or is that mechanism made in a way that all drivers wishing to use the
> reserved memory area can claim it back from the system, but there is no
> priority (other than first-come first-served) for which drivers claims
> it back in case two want to use the same reserved region (in a scenario
> where there isn't enough memory to allow both drivers)?

This is indeed what happens. Reusable is to let the system use the
reserved memory for things like caches that can easily be dropped when
a driver wants to use the memory in that reserved area. Once that
memory has been allocated, there's no claiming back, unless that
memory segment was freed of course.

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 09/10] ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes
Date: Fri, 4 May 2018 11:15:55 +0200	[thread overview]
Message-ID: <20180504091555.idgtzey53lozj2uh@flea> (raw)
In-Reply-To: <e8cd340605ab4db8ebf2888a4fce645e8bc481d0.camel@bootlin.com>

On Fri, May 04, 2018 at 10:47:44AM +0200, Paul Kocialkowski wrote:
> > > > > +			reg = <0x01c0e000 0x1000>;
> > > > > +			memory-region = <&ve_memory>;
> > > > 
> > > > Since you made the CMA region the default one, you don't need to
> > > > tie
> > > > it to that device in particular (and you can drop it being
> > > > mandatory
> > > > from your binding as well).
> > > 
> > > What if another driver (or the system) claims memory from that zone
> > > and
> > > that the reserved memory ends up not being available for the VPU
> > > anymore?
> > > 
> > > Acccording to the reserved-memory documentation, the reusable
> > > property
> > > (that we need for dmabuf) puts a limitation that the device driver
> > > owning the region must be able to reclaim it back.
> > > 
> > > How does that work out if the CMA region is not tied to a driver in
> > > particular?
> > 
> > I'm not sure to get what you're saying. You have the property
> > linux,cma-default in your reserved region, so the behaviour you
> > described is what you explicitly asked for.
> 
> My point is that I don't see how the driver can claim back (part of) the
> reserved area if the area is not explicitly attached to it.
> 
> Or is that mechanism made in a way that all drivers wishing to use the
> reserved memory area can claim it back from the system, but there is no
> priority (other than first-come first-served) for which drivers claims
> it back in case two want to use the same reserved region (in a scenario
> where there isn't enough memory to allow both drivers)?

This is indeed what happens. Reusable is to let the system use the
reserved memory for things like caches that can easily be dropped when
a driver wants to use the memory in that reserved area. Once that
memory has been allocated, there's no claiming back, unless that
memory segment was freed of course.

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180504/41c1fcef/attachment-0001.sig>

  parent reply	other threads:[~2018-05-04  9:15 UTC|newest]

Thread overview: 142+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 15:41 [PATCH v2 00/10] Sunxi-Cedrus driver for the Allwinner Video Engine, using media requests Paul Kocialkowski
2018-04-19 15:41 ` Paul Kocialkowski
2018-04-19 15:41 ` Paul Kocialkowski
2018-04-19 15:41 ` [PATCH v2 01/10] media: v4l2-ctrls: Add missing v4l2 ctrl unlock Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-20  7:23   ` Maxime Ripard
2018-04-20  7:23     ` Maxime Ripard
2018-04-20  7:23     ` Maxime Ripard
2018-04-20 13:38   ` Hans Verkuil
2018-04-20 13:38     ` Hans Verkuil
2018-04-20 13:38     ` Hans Verkuil
2018-04-19 15:41 ` [PATCH v2 02/10] media-request: Add a request complete operation to allow m2m scheduling Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-20  7:38   ` Alexandre Courbot
2018-04-20  7:38     ` Alexandre Courbot
2018-04-20 13:48   ` Hans Verkuil
2018-04-20 13:48     ` Hans Verkuil
2018-04-20 13:48     ` Hans Verkuil
2018-04-24  8:28   ` Sakari Ailus
2018-04-24  8:28     ` Sakari Ailus
2018-05-04  8:03   ` Paul Kocialkowski
2018-05-04  8:03     ` Paul Kocialkowski
2018-05-04  8:03     ` Paul Kocialkowski
2018-04-19 15:41 ` [PATCH v2 03/10] videobuf2-core: Add helper to get buffer private data from media request Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-20 13:43   ` Hans Verkuil
2018-04-20 13:43     ` Hans Verkuil
2018-04-20 13:43     ` Hans Verkuil
2018-04-24  8:37   ` Sakari Ailus
2018-04-24  8:37     ` Sakari Ailus
2018-05-04  8:03   ` Paul Kocialkowski
2018-05-04  8:03     ` Paul Kocialkowski
2018-05-04  8:03     ` Paul Kocialkowski
2018-04-19 15:41 ` [PATCH v2 04/10] media: vim2m: Implement media request complete op to schedule m2m run Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-19 15:41   ` Paul Kocialkowski
2018-04-19 15:45 ` [PATCH v2 05/10] media: v4l: Add definitions for MPEG2 frame format and header metadata Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-20  9:51   ` Tomasz Figa
2018-04-20  9:51     ` Tomasz Figa
2018-04-20  9:51     ` Tomasz Figa
2018-05-04  8:24     ` Paul Kocialkowski
2018-05-04  8:24       ` Paul Kocialkowski
2018-05-04  8:24       ` Paul Kocialkowski
2018-04-20 13:57   ` Hans Verkuil
2018-04-20 13:57     ` Hans Verkuil
2018-04-20 13:57     ` Hans Verkuil
2018-05-04  8:22     ` Paul Kocialkowski
2018-05-04  8:22       ` Paul Kocialkowski
2018-05-04  8:22       ` Paul Kocialkowski
2018-04-20 14:00   ` Hans Verkuil
2018-04-20 14:00     ` Hans Verkuil
2018-04-20 14:00     ` Hans Verkuil
2018-04-24  9:01   ` Sakari Ailus
2018-04-24  9:01     ` Sakari Ailus
2018-05-04  8:21     ` Paul Kocialkowski
2018-05-04  8:21       ` Paul Kocialkowski
2018-05-04  8:21       ` Paul Kocialkowski
2018-05-04  8:48   ` Paul Kocialkowski
2018-05-04  8:48     ` Paul Kocialkowski
2018-05-04  8:48     ` Paul Kocialkowski
2018-04-19 15:45 ` [PATCH v2 06/10] media: v4l: Add definition for Allwinner's MB32-tiled NV12 format Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-20 13:59   ` Hans Verkuil
2018-04-20 13:59     ` Hans Verkuil
2018-04-20 13:59     ` Hans Verkuil
2018-05-04  7:58     ` Paul Kocialkowski
2018-05-04  7:58       ` Paul Kocialkowski
2018-05-04  7:58       ` Paul Kocialkowski
2018-04-19 15:45 ` [PATCH v2 07/10] media: platform: Add Sunxi-Cedrus VPU decoder driver Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-24  9:13   ` Sakari Ailus
2018-04-24  9:13     ` Sakari Ailus
2018-05-04  7:57     ` Paul Kocialkowski
2018-05-04  7:57       ` Paul Kocialkowski
2018-05-04  7:57       ` Paul Kocialkowski
2018-04-19 15:45 ` [PATCH v2 08/10] dt-bindings: media: Document bindings for the Sunxi-Cedrus VPU driver Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 16:04   ` Philipp Zabel
2018-04-19 16:04     ` Philipp Zabel
2018-04-19 16:04     ` Philipp Zabel
2018-04-20  1:31     ` Tomasz Figa
2018-04-20  1:31       ` Tomasz Figa
2018-04-20  1:31       ` Tomasz Figa
2018-04-20  7:22       ` Paul Kocialkowski
2018-04-20  7:22         ` Paul Kocialkowski
2018-04-20  7:22         ` Paul Kocialkowski
2018-04-27  3:04         ` Rob Herring
2018-04-27  3:04           ` Rob Herring
2018-04-27  3:04           ` Rob Herring
2018-05-04  7:56           ` Paul Kocialkowski
2018-05-04  7:56             ` Paul Kocialkowski
2018-05-04  7:56             ` Paul Kocialkowski
2018-05-04  8:12             ` Maxime Ripard
2018-05-04  8:12               ` Maxime Ripard
2018-05-04  8:12               ` Maxime Ripard
2018-04-27  3:06   ` Rob Herring
2018-04-27  3:06     ` Rob Herring
2018-04-27  3:06     ` Rob Herring
2018-04-19 15:45 ` [PATCH v2 09/10] ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-20  7:39   ` Maxime Ripard
2018-04-20  7:39     ` Maxime Ripard
2018-04-20  7:39     ` Maxime Ripard
2018-05-04  7:49     ` Paul Kocialkowski
2018-05-04  7:49       ` Paul Kocialkowski
2018-05-04  7:49       ` Paul Kocialkowski
2018-05-04  8:40       ` Maxime Ripard
2018-05-04  8:40         ` Maxime Ripard
2018-05-04  8:40         ` Maxime Ripard
2018-05-04  8:47         ` Paul Kocialkowski
2018-05-04  8:47           ` Paul Kocialkowski
2018-05-04  8:47           ` Paul Kocialkowski
2018-05-04  8:54           ` Paul Kocialkowski
2018-05-04  8:54             ` Paul Kocialkowski
2018-05-04  8:54             ` Paul Kocialkowski
2018-05-04  9:15           ` Maxime Ripard [this message]
2018-05-04  9:15             ` Maxime Ripard
2018-05-04  9:15             ` Maxime Ripard
2018-05-04 12:04             ` Paul Kocialkowski
2018-05-04 12:04               ` Paul Kocialkowski
2018-05-04 12:04               ` Paul Kocialkowski
2018-05-04 13:40               ` Maxime Ripard
2018-05-04 13:40                 ` Maxime Ripard
2018-05-04 13:40                 ` Maxime Ripard
2018-05-04 13:57                 ` Paul Kocialkowski
2018-05-04 13:57                   ` Paul Kocialkowski
2018-05-04 13:57                   ` Paul Kocialkowski
2018-05-04 15:44                   ` Maxime Ripard
2018-05-04 15:44                     ` Maxime Ripard
2018-05-04 15:44                     ` Maxime Ripard
2018-04-19 15:45 ` [PATCH v2 10/10] ARM: dts: sun8i-a33: " Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski
2018-04-19 15:45   ` Paul Kocialkowski

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=20180504091555.idgtzey53lozj2uh@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=acourbot@chromium.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=hans.verkuil@cisco.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=pawel@osciak.com \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tfiga@chromium.org \
    --cc=wens@csie.org \
    /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.