linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Li <ayaka@soulik.info>
To: dri-devel@lists.freedesktop.org
Cc: mchehab+samsung@kernel.org, mikhail.v.gavrilov@gmail.com,
	laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org,
	sakari.ailus@iki.fi, daniel@fooishbar.org, mchehab@kernel.org,
	linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
	maxime.ripard@bootlin.com, sean@poorly.run, airlied@linux.ie,
	daniel@ffwll.ch, Randy Li <ayaka@soulik.info>
Subject: [PATCH v10 0/2] Add pixel format for 10 bits YUV video
Date: Thu, 10 Jan 2019 03:57:08 +0800	[thread overview]
Message-ID: <20190109195710.28501-1-ayaka@soulik.info> (raw)

As the requirement from:
P010 fourcc format support - Was: Re: Kernel error "Unknown pixelformat
0x00000000" occurs when I start capture video

I don't know which device would support the P010, P012, P016 video pixel
format, but Rockchip would support that NV12_10LE40 and a patch for that
driver is sent before.

Randy Li (2):
  drm/fourcc: Add new P010, P016 video format
  drm/fourcc: add a 10bits fully packed variant of NV12

 drivers/gpu/drm/drm_fourcc.c  | 13 +++++++++++++
 include/uapi/drm/drm_fourcc.h | 29 +++++++++++++++++++++++++++++
 2 files changed, 42 insertions(+)

-- 
2.20.1


             reply	other threads:[~2019-01-09 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 19:57 Randy Li [this message]
2019-01-09 19:57 ` [PATCH v10 1/2] drm/fourcc: Add new P010, P016 video format Randy Li
2019-01-14 16:36   ` Ayan Halder
2019-02-07  9:44     ` Neil Armstrong
2019-02-08 15:51       ` Daniel Vetter
2019-02-08 21:11         ` Neil Armstrong
2019-01-09 19:57 ` [PATCH v10 2/2] drm/fourcc: add a 10bits fully packed variant of NV12 Randy Li

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=20190109195710.28501-1-ayaka@soulik.info \
    --to=ayaka@soulik.info \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=sakari.ailus@iki.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).