All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: Liviu Dudau <Liviu.Dudau@arm.com>,
	Ezequiel Garcia <ezequiel@collabora.com>, nd <nd@arm.com>,
	"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"arnd\@arndb.de" <arnd@arndb.de>,
	"corbet\@lwn.net" <corbet@lwn.net>,
	"airlied\@linux.ie" <airlied@linux.ie>,
	"gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"nicolas.ferre\@microchip.com" <nicolas.ferre@microchip.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel\@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"davem\@davemloft.net" <davem@davemloft.net>,
	"maxime.ripard\@bootlin.com" <maxime.ripard@bootlin.com>,
	"malidp\@foss.arm.com" <malidp@foss.arm.com>,
	"mchehab+samsung\@kernel.org" <mchehab+samsung@kernel.org>,
	"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
	Ayan Halder <Ayan.Halder@arm.com>,
	"sean\@poorly.run" <sean@poorly.run>
Subject: Re: [RFC AFBC 03/12] drm/afbc: Add AFBC modifier usage documentation
Date: Mon, 14 Jan 2019 16:24:33 +0200	[thread overview]
Message-ID: <87won748ri.fsf@intel.com> (raw)
In-Reply-To: <20190114141322.6l3th2hjbsm7fzhp@DESKTOP-E1NTVVP.localdomain>

On Mon, 14 Jan 2019, Brian Starkey <Brian.Starkey@arm.com> wrote:
> AFBC is a relatively well-established name, whereas arm-fbc is not a
> term anyone will be familiar with.

First time I ever heard of AFBC. ;)

> We could name the file "arm-afbc.rst", though I am slightly against
> namespacing it that way for the reason mentioned above - it
> does/will/should apply to more than just the gpu/drm/arm tree.

Fair enough. It's not like the name is part of the ABI, so I guess let's
go with this, and we can rename later if we come up with a better name.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: "sean@poorly.run" <sean@poorly.run>,
	Ayan Halder <Ayan.Halder@arm.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
	"malidp@foss.arm.com" <malidp@foss.arm.com>,
	"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	nd <nd@arm.com>, Ezequiel Garcia <ezequiel@collabora.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [RFC AFBC 03/12] drm/afbc: Add AFBC modifier usage documentation
Date: Mon, 14 Jan 2019 16:24:33 +0200	[thread overview]
Message-ID: <87won748ri.fsf@intel.com> (raw)
In-Reply-To: <20190114141322.6l3th2hjbsm7fzhp@DESKTOP-E1NTVVP.localdomain>

On Mon, 14 Jan 2019, Brian Starkey <Brian.Starkey@arm.com> wrote:
> AFBC is a relatively well-established name, whereas arm-fbc is not a
> term anyone will be familiar with.

First time I ever heard of AFBC. ;)

> We could name the file "arm-afbc.rst", though I am slightly against
> namespacing it that way for the reason mentioned above - it
> does/will/should apply to more than just the gpu/drm/arm tree.

Fair enough. It's not like the name is part of the ABI, so I guess let's
go with this, and we can rename later if we come up with a better name.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-01-14 14:23 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 11:31 [RFC AFBC v2 00/12] Add support for Arm Framebuffer Compression(AFBC) in mali display driver Ayan Halder
2018-12-03 11:31 ` Ayan Halder
2018-12-03 11:31 ` [RFC AFBC 01/12] drm/fourcc: Add AFBC yuv fourccs for Mali Ayan Halder
2018-12-03 11:31   ` Ayan Halder
2018-12-03 11:31 ` [RFC AFBC 02/12] drm: Added a new format DRM_FORMAT_XVYU2101010 Ayan Halder
2018-12-03 11:31   ` Ayan Halder
2018-12-04 16:31   ` Liviu Dudau
2018-12-04 16:31     ` Liviu Dudau
2018-12-03 11:31 ` [RFC AFBC 03/12] drm/afbc: Add AFBC modifier usage documentation Ayan Halder
2018-12-03 11:31   ` Ayan Halder
2019-01-03 20:44   ` Ezequiel Garcia
2019-01-03 20:44     ` Ezequiel Garcia
2019-01-11 18:07     ` Liviu Dudau
2019-01-11 18:07       ` Liviu Dudau
2019-01-14 12:23       ` Jani Nikula
2019-01-14 12:23         ` Jani Nikula
2019-01-14 14:13         ` Brian Starkey
2019-01-14 14:13           ` Brian Starkey
2019-01-14 14:24           ` Jani Nikula [this message]
2019-01-14 14:24             ` Jani Nikula
2018-12-03 11:31 ` [RFC v3 AFBC 04/12] drm/arm/malidp: Set the AFBC register bits if the framebuffer has AFBC modifier Ayan Halder
2018-12-03 11:31   ` Ayan Halder
2018-12-04 16:50   ` Liviu Dudau
2018-12-04 16:50     ` Liviu Dudau
2018-12-14 13:45     ` Ayan Halder
2018-12-14 13:45       ` Ayan Halder
2018-12-17 14:01       ` Liviu Dudau
2018-12-17 14:01         ` Liviu Dudau
2018-12-03 11:31 ` [RFC AFBC 05/12] drm/arm/malidp:- Define a common list of AFBC format modifiers supported for DP500, DP550 and DP650 Ayan Halder
2018-12-03 11:31   ` Ayan Halder
2018-12-04 16:56   ` Liviu Dudau
2018-12-04 16:56     ` Liviu Dudau
2018-12-03 11:32 ` [RFC AFBC 06/12] drm/arm/malidp:- Added support for new YUV formats " Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 16:57   ` Liviu Dudau
2018-12-04 16:57     ` Liviu Dudau
2018-12-14 14:12     ` Ayan Halder
2018-12-14 14:12       ` Ayan Halder
2018-12-17 14:04       ` Liviu Dudau
2018-12-03 11:32 ` [RFC AFBC 07/12] drm/arm/malidp: Define the constraints on each supported drm_fourcc format for the AFBC modifiers Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:49   ` Liviu Dudau
2018-12-04 17:49     ` Liviu Dudau
2018-12-14 14:23     ` Ayan Halder
2018-12-14 14:23       ` Ayan Halder
2018-12-03 11:32 ` [RFC AFBC 08/12] drm/arm/malidp: Specified the rotation memory requirements for AFBC YUV formats Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:50   ` Liviu Dudau
2018-12-04 17:50     ` Liviu Dudau
2018-12-03 11:32 ` [RFC AFBC 09/12] drm/arm/malidp:- Writeback framebuffer does not support any modifiers Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:50   ` Liviu Dudau
2018-12-04 17:50     ` Liviu Dudau
2018-12-03 11:32 ` [RFC AFBC 10/12] drm/arm/malidp:- Use the newly introduced malidp_format_get_bpp() instead of relying on cpp for calculating framebuffer size Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:51   ` Liviu Dudau
2018-12-04 17:51     ` Liviu Dudau
2018-12-03 11:32 ` [RFC AFBC 11/12] drm/arm/malidp:- Disregard the pitch alignment constraint for AFBC framebuffer Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:52   ` Liviu Dudau
2018-12-04 17:52     ` Liviu Dudau
2018-12-03 11:32 ` [RFC v3 AFBC 12/12] drm/arm/malidp: Added support for AFBC modifiers for all layers except DE_SMART Ayan Halder
2018-12-03 11:32   ` Ayan Halder
2018-12-04 17:54   ` Liviu Dudau
2018-12-04 17:54     ` Liviu Dudau

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=87won748ri.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=Ayan.Halder@arm.com \
    --cc=Brian.Starkey@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malidp@foss.arm.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=nd@arm.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=sean@poorly.run \
    /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.