Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kamil Debski <k.debski@samsung.com>
To: 'Mauro Carvalho Chehab' <mchehab@redhat.com>, jtp.park@samsung.com
Cc: linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	pawel@osciak.com, kyungmin.park@samsung.com,
	jaeryul.oh@samsung.com
Subject: RE: [RFC/PATCH v4 1/4] Changes in include/linux/videodev2.h for MFC 5.1
Date: Fri, 10 Dec 2010 11:10:37 +0100	[thread overview]
Message-ID: <001201cb9852$820d48c0$8627da40$%debski@samsung.com> (raw)
In-Reply-To: <4D01F0B6.8090800@redhat.com>

Hi,

From: Mauro Carvalho Chehab [mailto:mchehab@redhat.com]
> Em 10-12-2010 01:32, 박정태 escreveu:
> > Hi, Kamil
> >
> > What do you think modification of codec class control ID for MFC as
> > following.
> > 1. Define the CID base for MFC
> > 2. Separate decode & encode controls
> > 3. Separate common & codec-specific controls
> >
> >> Add fourcc values for compressed video stream formats and
> >> V4L2_CTRL_CLASS_CODEC. Also adds controls used by MFC 5.1 driver.
> 
> This is a very bad idea. As much as possible, controls should be
> generic enough
> to avoid us to have the same control provided  by two different
> hardware.
> 
> The only case were a control should be per-driver, is when the control
> is for some
> very specific implementation detail on that hardware, that it is
> unlikely that other
> chipsets will implement it at the same way.
> 

I agree with Mauro. The point of having a general class for codecs
(V4L2_CID_CODEC_CLASS) is reusing same controls for different hardware.
I think that most controls, maybe all, could be used by other hw codecs.

> (snip)

Best regards,
-- 
Kamil Debski
Linux Platform Group
Samsung Poland R&D Center

  parent reply	other threads:[~2010-12-10 10:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 13:35 [RFC/PATCH v4 0/4] Multi Format Codec 5.0 driver for S5PC110 SoC Kamil Debski
2010-12-09 13:35 ` [RFC/PATCH v4 1/4] Changes in include/linux/videodev2.h for MFC 5.1 Kamil Debski
2010-12-10  3:32   ` 박정태
     [not found]     ` <4D01F0B6.8090800@redhat.com>
2010-12-10 10:10       ` Kamil Debski [this message]
2010-12-09 13:35 ` [RFC/PATCH v4 2/4] MFC: Add MFC 5.1 driver to plat-s5p Kamil Debski
2010-12-10  2:44   ` Kukjin Kim
2010-12-10 10:10     ` Kamil Debski
2010-12-10  3:41   ` Kukjin Kim
2010-12-09 13:35 ` [RFC/PATCH v4 3/4] MFC: Added MFC 5.1 V4L2 driver Kamil Debski
2010-12-09 13:35 ` [RFC/PATCH v4 4/4] s5pv210: Enable MFC on Goni Kamil Debski
2010-12-10  2:32 ` [RFC/PATCH v4 0/4] Multi Format Codec 5.0 driver for S5PC110 SoC Kukjin Kim
2010-12-10  2:40   ` Kyungmin Park
2010-12-10  3:40     ` Kukjin Kim
2010-12-10  4:02       ` Kyungmin Park
2010-12-10  5:23         ` Kukjin Kim

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='001201cb9852$820d48c0$8627da40$%debski@samsung.com' \
    --to=k.debski@samsung.com \
    --cc=jaeryul.oh@samsung.com \
    --cc=jtp.park@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@redhat.com \
    --cc=pawel@osciak.com \
    /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