From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Ayaka <ayaka@soulik.info>, Sakari Ailus <sakari.ailus@iki.fi>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: P010 fourcc format support - Was: Re: Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video
Date: Wed, 09 Jan 2019 13:20:00 -0500 [thread overview]
Message-ID: <e5ee7e611ff861b4e8dbc4fbf48dd2bf48e074a4.camel@ndufresne.ca> (raw)
In-Reply-To: <20190109152808.5ce020ca@coco.lan>
Le mercredi 09 janvier 2019 à 15:28 -0200, Mauro Carvalho Chehab a
écrit :
> Em Wed, 09 Jan 2019 11:52:45 -0500
> Nicolas Dufresne <nicolas@ndufresne.ca> escreveu:
>
> > Le jeudi 10 janvier 2019 à 00:42 +0800, Ayaka a écrit :
> > > > There is a UVC media device that supports P010 device. We're discussing
> > > > about adding support for it on media. The full thread is at:
> > > >
> > > > https://lore.kernel.org/linux-media/20190109121900.hbrpttmxz3gaotwx@valkosipuli.retiisi.org.uk/T/#m8c395156ca0e898e4c8b1e2c6309d912bc414804
> > > >
> > > > We've seen that you tried to submit a patch series for DRM adding
> > > > support for it at the rockship driver. What's the status of such
> > > > series?
> > > Rockchip would use another 10bit variant of NV12, which is merged as NV12LE40 at Gstreamer and I sent another patch for it, but I didn’t receive any feedback from that.
>
> Hmm... We have already NV12 format at media subsystem side:
> Documentation/media/uapi/v4l/pixfmt-nv12.rst
>
> Did we miss some patch from you?
NV12 is by definition 8bit per pixel. Rockchip uses a 10bit variant,
for which each pixels is packed over 40 bits so that it's bandwidth
efficient. It's probably quite complex to handle HW wise. Xilinx also
got a variant they are upstream, which is packed over 32 bits, with 2
bits padding.
>
> > For extra detail, the Rockchip variant is fully packed, with no padding
> > bits, while the Microsoft variant uses 16bits per pixels, with 6bits
> > padding. It was a mistake to use P010 initially for the Rockchip
> > format.
>
> Yeah, P010 format seems to be a waste of bandwidth. Yet, as we're
> now having devices using it (via uvcdriver), it would make sense to
> merge the single plane format for it. I would merge the P016 too, as
> P010 seems to be just a degradation of it.
It's meant for fast CPU indexing, which makes it odd as a streaming
format.
>
> Ayaka,
>
> Would it be possible for you to re-send the P010/P016 documentation
> for single plane, fixing the typo (simliar -> similar)?
>
> Let's not merge the dual plane formats, as we don't need them
> yet at the Kernel.
>
> Thanks,
> Mauro
prev parent reply other threads:[~2019-01-09 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 20:05 Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video Mikhail Gavrilov
2019-01-08 14:45 ` Mauro Carvalho Chehab
2019-01-08 14:54 ` Laurent Pinchart
2019-01-08 15:16 ` Mauro Carvalho Chehab
2019-01-08 15:55 ` Laurent Pinchart
2019-01-08 15:18 ` Mikhail Gavrilov
2019-01-08 15:58 ` Laurent Pinchart
2019-01-08 16:11 ` Mikhail Gavrilov
2019-01-08 18:49 ` Mauro Carvalho Chehab
2019-01-08 19:00 ` Mauro Carvalho Chehab
2019-01-09 3:51 ` Mikhail Gavrilov
2019-01-09 12:03 ` Mauro Carvalho Chehab
2019-01-08 21:29 ` Laurent Pinchart
2019-01-09 12:19 ` Sakari Ailus
2019-01-09 13:01 ` P010 fourcc format support - Was: " Mauro Carvalho Chehab
2019-01-09 16:42 ` Ayaka
2019-01-09 16:52 ` Nicolas Dufresne
2019-01-09 17:28 ` Mauro Carvalho Chehab
2019-01-09 18:20 ` Nicolas Dufresne [this message]
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=e5ee7e611ff861b4e8dbc4fbf48dd2bf48e074a4.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=ayaka@soulik.info \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=sakari.ailus@iki.fi \
/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).